Every Transformation Looks Infinite Until Someone Deconstructs It.

Everyone treated this as a technology integration problem: get the vendors coordinated and build the integration.

One of the most complex multi-vendor transformations in the portfolio: an integration platform provider, a systems integrator, the customer's own global business and IT functions, and multiple specialized vendors, all operating without a shared model of what success looked like or who owned what.

Built the governance and decision architecture from zero, but the real work was earning the trust to make it stick. I translated competing priorities across every stakeholder group into a single decision framework, then orchestrated the alignment needed for a genuinely global organization to move on it together, not just comply with it.

What had been the hardest, least-trusted program in the portfolio became the model the customer adopted for how complex transformation should be orchestrated across their enterprise, and the confidence to expand into a seven-figure, multi-year commitment across dozens of additional global sites.

A regulatory finding meant this was a compliance exercise: write the SOPs, close the audit, move on.

A capability that didn't exist anywhere in the client's organization: not a checklist item, but an entirely new function that had to be imagined into existence, with no playbook, no precedent, and no one at the company who had done this before.

I was in the room for the first conversation where that gap became undeniable, before there was a team, a process, or even a name for what needed to be built. I wrote the governing document that started it, then spent several years building the structure underneath: training, escalation pathways, quality systems, and eventually a leadership bench that could run it without me. A small founding team became a global capability spanning hundreds of people, across regions and regulatory classes nobody had planned for at the outset.

Some transformations don't have an existing model to diagnose against: the diagnosis is deciding what needs to exist in the first place. Of every program I've led, this is the one I'd still tell the same way twenty-five years from now: proof that decomposing “nothing exists yet” into something that scales for a decade is the hardest, and most durable, version of the work.

The client wanted a transition: move a body of work from one vendor to another without disruption.

The client wasn't buying a transition. They were buying proof that a repeatable capability existed: evidence the organization could take on complexity it had never demonstrated before, and be trusted with more of it.

Hired with an explicit three-year mandate, I built that capability from nothing, starting as a manual, prototype-stage framework and evolving it toward a scalable operating model the enterprise could reuse. I then used it to lead a large-scale, multi-country transition spanning language and regulatory requirements the organization had never supported before, managing the stakeholder complexity that came with it.

Winning new scope rarely comes down to the transition itself; it comes down to whether the client believes you've built something repeatable. That capability became exactly the kind of proof clients bet expansion on.