How the work actually goes
Six stages. No shortcuts.
Strategy that can't survive contact with budgets, politics, and the people who have to carry it out isn't a strategy yet. This is the sequence that gets it there.
Listen beneath the complaint
Start with stakeholder interviews, document review, and direct observation. Separate what leadership believes is wrong from what the evidence and the data actually show. Find where work stops moving, who benefits from the current structure, and what the organization has trained itself not to say.
Interrogate the myth
Every organization has a story about why things are the way they are — about its history, its competence, its market position, its culture. The story usually has real truth in it. The task is naming the belief that makes the current structure feel necessary, and testing whether it still holds.
Define the consequential why
Not a slogan. Who has to benefit. What has to materially change. What it costs to do nothing. What evidence would actually prove the organization had moved.
Architect the break
Design the smallest structural intervention that can interrupt the pattern — in authority, incentives, workflow, information, staffing, governance, or resources. Small and real beats sweeping and theoretical.
Embed, execute, and measure
Work inside the implementation. Set ownership, milestones, and a cadence for decisions. Treat resistance and unintended consequences as information, not failure.
Transfer agency
Document the model. Train the people who own it. Hand over decision rights and operating knowledge. Confirm the organization can sustain and improve the system without continued dependence on The Why Inc.
Running underneath every stage
The people doing the work get developed too.
A system only stays fixed if the people running it are capable of running it. Alongside the six stages, staff leadership development, partnership-building, and individual opportunity coaching happen wherever the engagement touches people directly — not as an add-on, but as part of how agency actually gets transferred.
Before any of it starts
Every engagement has to answer these first.
What is the real problem?
Not the one leadership opened with — the one underneath it.
Why hasn't the existing system solved it already?
Usually something besides the stated problem is in the way. Find out what it is.
What authority and access does this need?
Strategy without access to the real system is a guess.
What can the client do alone when this ends?
If the answer is “nothing,” the engagement was designed wrong.