Strategy
Why strategy doesn't reach delivery
Senior leaders often know what they want to achieve. The problem is the system beneath them. Here's the pattern — and what to do about it.
Every leadership team I've worked with has a strategy. Most have a good one.
The problem isn't the strategy. It's the gap between where the strategy lives — in documents, decks, and leadership conversations — and where the work actually gets done.
The pattern
Here's what it usually looks like.
The leadership team agrees a set of priorities. Those priorities get communicated. They land differently at each layer of the organisation. By the time they reach the teams doing the work, they've been filtered through multiple interpretations, competing pressures, and the weight of existing commitments.
Six months later, a review reveals that the organisation has been busy — but not necessarily on the right things.
Why it happens
Three causes appear more than any others.
Priorities are not choices. A strategy with ten equally weighted priorities is not a strategy — it's a list. When everything is important, nothing is. Teams fill the ambiguity with their own judgement, which often means reverting to what they already know.
Measurement lags too far behind. Many organisations measure success by activity — projects launched, features delivered, milestones hit. These measure effort, not outcomes. By the time the data shows that the strategy isn't landing, months have passed.
The connective tissue is missing. Strategy, portfolio, delivery, and performance management are often run as separate processes. Each has its own rhythm, language, and ownership. The places where they should connect — where a strategic goal becomes an initiative, where an initiative becomes work, where that work generates evidence — are unclear or absent.
What to do about it
The fix isn't a better strategy document. It's building the operating system that connects strategic intent to execution.
That means:
- Making choices explicit — not just about what to do, but what not to do
- Defining outcomes, not just outputs, so teams know what success looks like
- Connecting portfolio decisions to strategic priorities, not just budget cycles
- Building review rhythms that surface evidence and drive adaptation
None of this is complicated. But it requires deliberate design — and a willingness to look at the system, not just the symptoms.
If this pattern sounds familiar, book a 30-minute call to talk through your situation.
Want to explore this further?
Book a 30-minute call to discuss how this applies to your organisation.