Selected work
The request is where discovery starts—not where it ends.
These are not software showcases. Each case begins where the operating environment became difficult: confidentiality crossing departments, brands multiplying faster than governance, customer access colliding with regulation, or technical cases surviving months of handoffs across borders.
How to read the work
Look for the decision underneath the configuration.
The identities are generalized, but the tensions are not. Each case explains what was becoming difficult to control, why a conventional implementation would have been insufficient, what I owned, how the response was structured, and what existed when the work was delivered.
Where quantitative outcomes have not been independently verified, I do not invent them. The proof is in scope, decisions, architecture, delivery, and the operating state created.
Four environments. Four different kinds of pressure.
Internal service transformation
One Service Front Door for HR, Payroll, and IT
One employee experience had to conceal several very different kinds of work—without sacrificing ownership, coordination, or trust.
Design one employee experience without pretending every department performs the same work.
An implementation-ready employee-service architecture involving 33 identified users, IT, HR, and payroll scope, restricted-ticket requirements, employee and manager intake, onboarding and offboarding, and cross-department coordination.
Business systems leadership · Internal service transformation · Confidential workflow architecture
Examine the evidence →Multibrand customer experience
Scaling Support Across Multiple Brands Without Losing Control
The first implementation solved fragmentation. The harder work was ensuring every new brand, channel, and exception did not recreate it.
Centralize the operation without flattening the brands or hard-coding the organization’s current size.
A progression from fragmented communication toward a centralized multichannel and multibrand environment, followed by expansion work involving optimization, additional channels, self-service, integrations, and broader systems needs.
CX systems leadership · Multibrand architecture · Long-horizon client ownership
Examine the evidence →Regulated service architecture
Designing Omnichannel Service Inside Regulatory Constraints
Customers needed several ways to engage. The operation needed every important communication path to remain deliberate, traceable, and defensible.
Treat regulatory and policy requirements as architecture inputs—not a compliance review performed after configuration.
Verified discovery and architecture spanning omnichannel intake, telephony, IVR planning, callback evidence, call recording, payment workflows, reporting, time-based restrictions, and risk controls.
Regulated systems · Solutions consulting · Risk-aware CX architecture
Examine the evidence →Cross-border technical operations
Coordinating Long-Running Technical Support Across Borders
When a technical case can last for months, continuity becomes an operating capability—not a note field.
Design around the life of the technical case—not the team currently holding it.
A verified cross-border support design involving domestic field operations, overseas engineering, machine-specific diagnosis, parts coordination, service scheduling, multiple channels, time-zone constraints, and long-lived cases.
Technical service operations · Cross-border coordination · Long-running case architecture
Examine the evidence →Solutions consulting · Zendesk
Keeping the Solution Intact From Sales Through Implementation
When internal solution-consulting capacity was constrained, active opportunities still needed credible discovery, honest scope, and a delivery path customers could trust.
Make the sales conversation the first responsible stage of implementation—not a separate performance.
A repeatable co-selling and implementation-continuity motion supporting active Zendesk opportunities when internal capacity was constrained, with documented sales credit on supported wins.
Solutions Consultant · Professional Services · Zendesk implementation
Examine the evidence →Implementation leadership · Incident response
Protecting Five Brands During a Live Telephony Launch Incident
A platform-side porting error redirected live calls for five brands into the wrong environment. The response had to become operational before the fault could be fully resolved.
Treat every misrouted call as a customer obligation while the technical escalation proceeds in parallel.
Approximately 24 hours of coordinated incident containment for five brands, including temporary telephony workflows, brand-aware intake, customer continuity, and platform escalation.
Implementation Manager · Professional Services · CX and Support Systems
Examine the evidence →