Why strategy fails at the execution layer — and what to do about it

There is a familiar pattern in the firms we work with: a strategy review produces a compelling presentation, leadership aligns around it, and then — six months later — almost nothing has changed. The strategy hasn't failed. Execution has.

The failure is rarely cultural or motivational. It is almost always structural. Strategies are written at altitude. They describe ambitions and priorities. They do not describe decisions — who makes them, under what criteria, by when. And without that specificity, each layer of the organisation defaults to what it already knows how to do.

The question that most strategy processes skip is deceptively simple: what would have to be true of the organisation's operating model for this strategy to actually work? Answering it forces a very different conversation. Not 'where do we want to go?' but 'what would we have to stop doing, start doing, and do differently to get there?'

In our experience, three gaps account for most strategy-to-execution failures. The first is a resource gap: the new priorities are not resourced, because existing commitments have a constituency and new ones do not. The second is a decision rights gap: the people closest to the work don't have authority to make the calls that would move things, so they escalate, and things slow down. The third is a measurement gap: the strategy has outcome metrics (revenue, margin, market share) but no leading indicators — so the team can't tell whether it's on track until it's too late to course-correct.

The fix is not more planning. It is translating the strategy into a small number of explicit choices about resource allocation, decision authority, and early-warning metrics — and then building the cadence to manage against them. Strategy becomes executable when it is specific enough to be contested. If everyone agrees, it probably isn't saying anything.

The leadership teams that execute well share one habit: they treat the first ninety days after a strategy review as an operating design problem, not a communications problem. They ask: what has to change structurally for this to happen? And they're willing to answer honestly, even when the answer is uncomfortable.