You have built the strategy. You have built the team.
And the work is still not landing the way you know it can.
You already know how to solve operational problems. More resources, better tools, tighter process. Those are bounded and fixable. The stall is not that kind of problem.
The stall lives in the human dimension: how people see the situation, what they are protecting, what they are unwilling to name. Every standard response skips this entirely.
The Build does not. It works on the human side while the operational work keeps moving.
Day to day, you might find yourself...
Managing fires that keep reigniting.
The cost fix that broke query performance. The query fix that broke the cost model. One problem managed, another surfacing, and the same loop with a different label on the ticket.
Watching adoption fall short.
The migration lands on time. The teams it was built for are still running workarounds from the old system. Nobody is using it the way it was designed.
Losing ground you already gained.
The executive who championed your work goes quiet. The meeting invitations stop arriving. Your calendar fills with escalation calls instead of the conversations that actually move things.
Reaching the limit of what you know.
You have made the case. With data, with decks, with deliverables. You have done everything you know how to do. And the quiet thought you will not say out loud: what if the problem is not the organisation?
So you are wondering what actually has to change?
Not another framework applied from outside. Not another restructure.
The stall is not a knowledge problem. It is a naming problem, a seeing problem, a language problem, a commitment problem, and none of them resolves in isolation.
The Build works on all of them.
The entry point is the stall itself. Something is live and not moving.
Name It.
The first thing we do is sit with the question most skip entirely: what part of this requires people to change, not their tools, but how they see the situation? Every stalled initiative has operational problems. Those get attention. The human dimension gets skipped, not because leaders are careless, but because the operational answer is always more immediately available and more comfortable to act on. Getting that distinction wrong guarantees the wrong solution. We get it right before anything else moves.
Most common roadblock: We already know what the problem is. Or think we do. The diagnosis has been made before the question has been asked, and the rest of the work follows from a conclusion that was never examined.
See It.
We map the system before making a single move. Who is in this, and what are they dealing with? Where does power actually sit, and how does it move? What are the prevailing winds that will either keep the initiative on course or blow it quietly onto the rocks? When resistance appears, we do not ask how to overcome it. We ask: is there gold here? Resistance is almost always protecting something. When you learn to mine it rather than manage it, you find information nobody else in the organisation has access to.
Most common roadblock: The pull toward action is strong. Most of us move before we have read the room, the players, or the prevailing winds. Execution without that intelligence is just motion.
Play It.
This is where we get honest about what it actually takes. The role gets you authority. Language and relationships build the power that actually moves things. Political capital does not build itself. We build it deliberately, just as you build anything else worth having. Who has the most to lose, and are they being heard? Who needs to be in the room before the decision, not after it? What language reaches this person, this team, that the current vocabulary is completely missing?
Most common roadblock: We believe the work should speak for itself. Engaging deliberately with power and language feels like politics, and politics feels like a betrayal of the work. So the political terrain goes unmapped, and the initiative pays the price.
Own It.
We surface the self-protective patterns that keep the organisation doing the opposite of what it says it wants. Then we surface yours. Underneath every stalled commitment there is almost always a competing one. Something you are genuinely protecting that directly undermines the thing you say you want to achieve. It is not sabotage. It is human. If you look honestly, you find that the stall has had an inside accomplice the entire time.
Most common roadblock: We do the work on everyone around us and never once turn the lens on ourselves.
Lead It.
By this stage the framework has become internal. You are not applying an approach. You are operating from a fundamentally different place, able to hold the operational and adaptive dimensions simultaneously, read the system, speak the right language, and work with your own patterns rather than being run by them. The conversations that were previously unavailable have now become possible. The one with the resistant business unit. The one with the executive sponsor. The ones that require naming what the initiative is actually asking people to give up. None of them are available at the start. They require everything the previous four stages have built.
Most common roadblock: We treat this stage as the destination. The integration happens once and is not maintained. The old operating system quietly reinstalls itself.
If these roadblocks feel familiar, the skills that built your career are not the ones that will break the stall.
The Build does not replace what you have built. It runs alongside it. And it addresses the dimension that operational excellence and outside expertise, on their own, cannot.
What we build together
Everything below is built together across the sixteen weeks. Every deliverable is yours to keep, and each one changes what becomes possible.
1. Name what you are really dealing with.
A written diagnostic statement that names the stall accurately and identifies why previous attempts missed. One page you keep on your desktop and point to when the next pressure to fix something arises.
2. Read the room before you enter it.
A stakeholder map that plots every key player by influence and interest, mapping their stakes, desired outcomes, loyalties, potential losses, and hidden alliances. A living document you update as new intelligence comes in. Every move from this point forward is made with that map in hand.
3. Be heard by the people who matter.
A power map and language map. A structured audit of your political capital across every key stakeholder: the quality of each relationship, what has been invested versus assumed, and where rebuilding is needed. Paired with redescriptions of the initiative written in the language of the person you need to reach.
4. Find your own role in the stall.
An immunity-to-change map and experiment log. The organisational self-protective structures surfaced and named. Then yours. The improvement goal, the behaviours working against it, the hidden competing commitments, and the assumption holding the whole structure in place. Paired with experiments designed to test whether that assumption is as accurate as it feels.
5. Lead from a different place.
A 90-day leadership plan and personal operating statement. The plan maps the conversations still ahead, the stakeholder moves that need sequencing, and the adaptive challenges that will resurface under pressure. The operating statement captures how you lead from this point forward. You share it with your team. You return to it when the pressure comes back.
6. Measure what shifted.
A seven-dimension 360 leadership assessment goes out before we begin and again at twelve months, to the same respondents. How you adapt under pressure, make sense of complexity, build relationships, communicate vision, approach execution, build credibility, and your overall effectiveness. Documented evidence of change across the full year. Not just how it felt, but how you are being experienced by the people around you.
How it works
It starts with a conversation.
Forty-five minutes. Not a sales call. I want to understand your situation before making any recommendations. If it is not the right fit, I will tell you.
We measure before we move.
You complete a structured diagnostic covering the initiative's history, the attempts made, and your own assessment of your role in the stall. The opening 360 goes out at the same time. Both are synthesised into a single baseline. Everything that follows is measured against it.
Sixteen weeks together.
Five stages, from the diagnostic in week one through the leadership plan in week sixteen. Each stage builds on the last. The deliverables are not exercises. They are working documents you use in real time, in your real situation, with the real people involved.
The work continues after the sixteen weeks.
A 30-day check-in. A three-month review. A six-month leadership assessment. And at twelve months, the closing 360.
The Build is sixteen weeks of focused work together, followed by a year of support.
The time commitment is two to three hours per week. We start with one stall, but what you carry forward applies to everything.
The 360 assessment provides documented evidence of change across the full year, measured by the people around you.
If you are exploring whether this is the right fit, the best next step is an honest conversation. We will review your situation together. If The Build is what you need, we will know. If it is not, I will tell you that too.
Questions
How is this different from executive coaching?
Executive coaching develops the leader. The Build develops the leader while the initiative is live. The operational and adaptive dimensions run in parallel. The delivery work keeps moving. And the deeper work happens at the same time. Most approaches separate these. The Build does not.
What kind of organisations do you work with?
Data-led organisations where the technology is in place but the results have not followed. The sweet spot is after the technical work is done and something is clearly stuck. But if you are mid-rollout and already seeing the human side breaking down, or years into a stall and unsure where to start, that is worth a conversation too.
How long does it take to see results?
The diagnostic delivers a named analysis in the first two weeks. After the first stage, you will have a clearer picture of what you are actually dealing with than you have had in months.
What if the challenge is really just a technology problem?
The Build starts with a diagnostic. If the problem is operational, we name it as operational. The Build is not the right response for a purely operational problem, and I will tell you that. The distinction is the whole point. You do not apply an adaptive solution to an operational problem any more than you apply an operational solution to an adaptive one.
Book a conversation
Forty-five minutes. No commitment.