The gap between strategy and delivery isn't a process problem

There is a meeting that happens in almost every organisation I have ever worked in. It goes something like this. The leadership team spends two days offsite. They produce a strategy. It has a vision, some strategic pillars, maybe a set of priorities for the year. Someone designs a good slide. Everyone leaves feeling aligned.

Six weeks later, I sit with the delivery teams. I ask them what they are working on and why. And I listen very carefully to whether what they say connects to what I heard in that leadership meeting.

It almost never does.

Not because the teams are not working hard. Not because the strategy was wrong. But because somewhere between the offsite and the sprint board, the intent got lost. Diluted, translated, filtered, or simply never arrived. The leadership team believes the organisation is moving in one direction. The teams are moving in whatever direction makes sense given the work in front of them. And nobody has noticed, because there is no mechanism that would make the gap visible.

This is one of the most expensive problems in organisational life and it is almost never treated as a priority. Because it does not look like a crisis. The work continues. The reports come in. The dashboards show progress. It is only when you look at what was actually delivered against what the strategy required that the gap becomes undeniable, and by then it is usually too late to close it without significant cost.

Why the gap exists

In my experience the gap almost always has multiple causes operating simultaneously. Fixing one without addressing the others is why so many well-intentioned interventions fail to stick.

The first cause is that leaders assume communication equals alignment. The strategy gets announced. It goes in the all-hands presentation. It appears on the intranet. A town hall is held. And leadership genuinely believes that because the information has been shared, it has been understood, internalised, and translated into action.

It has not. Hearing something once in a large meeting is not the same as understanding what it means for your specific team's priorities next quarter. I have sat in rooms where a leadership team was genuinely puzzled that the organisation was not moving in the direction they had clearly communicated six months earlier. When I asked the teams what the strategic priorities were, I got six different answers. None of them were wrong exactly. None of them were quite right either.

The second cause is middle management. This is the layer that receives the strategy from above and is supposed to translate it into direction for the teams below. In most organisations this is where the intent breaks down most severely.

Middle managers are often the most time-pressured people in the building. They are managing upward, managing downward, and managing sideways simultaneously. They receive a strategy written in outcome language. Be the most trusted partner in our sector. Accelerate time to value. Build a high-performing organisation. Then they have to turn it into something their teams can actually do on Monday morning. Most of the time they do their best. But their best involves interpretation, prioritisation, and compromise. By the time the strategy has passed through three layers of management it frequently bears little resemblance to the original intent.

The third cause is the language mismatch between strategy and delivery. Strategy is written in outcomes. Delivery operates in tasks. The two rarely speak the same language and there is usually no bridge between them.

I have seen organisations with genuinely good strategies fail to execute not because the teams were incapable but because nobody had done the work of connecting "increase customer satisfaction by 20%" to "here is what your team specifically needs to do differently this quarter." OKRs are supposed to solve this. They often do not, because organisations implement the ceremony of OKRs without doing the hard thinking about how the objectives cascade and connect.

The fourth cause is the absence of a feedback loop. Nobody knows the gap exists because there is no mechanism designed to surface it. Reporting flows upward. Strategy flows downward. There is no structured way for delivery reality to reach leadership, and no structured way for strategic intent to reach teams in a form that either side can actually use.

I have worked with leadership teams who were genuinely shocked to learn what their teams were spending most of their time on. Not because the teams were hiding it. But because the information was never captured, never surfaced, and never reached anyone who might have cared.

What actually closes the gap

The honest answer is that no single intervention closes this gap. I have watched organisations implement OKRs and achieve nothing because the planning did not change. I have watched organisations implement quarterly planning and achieve nothing because the teams still had no visibility of what leadership actually needed. And I have watched organisations build beautiful delivery dashboards that leadership never looked at because the data did not connect to their strategic questions.

What works is all three, working together, in the right sequence.

OKRs done properly create the bridge between strategic intent and team-level action. Not OKRs as a performance management tool. Not OKRs as a way of measuring individuals. OKRs as a shared language connecting what the organisation is trying to achieve to what each team is actually doing. When an engineer can look at their sprint and trace a line from their work to a key result to an objective to a strategic priority, that is when the gap starts to close. It takes discipline to build that cascade. Most organisations stop halfway.

Quarterly planning creates the rhythm that keeps the connection live. A strategy agreed in January that is never revisited until December is not a strategy. It is a document. Quarterly planning, done as a genuine whole-system exercise rather than a calendar exercise, forces the organisation to ask every ninety days: are we still pointed in the right direction? Has anything changed that should change our priorities? Are the teams working on what actually matters most right now?

Big Room Planning, done well, is one of the most powerful tools I have seen for closing the strategy-delivery gap at scale. Getting leadership, engineering, and delivery in the same room, working on the same problems, is not just a planning exercise. It is an alignment exercise. You cannot leave a well-run Big Room Planning event without knowing exactly what the next quarter requires from your team, and why.

Real-time delivery visualisation closes the feedback loop. When leadership can see what teams are actually working on, and teams can see how their work connects to organisational priorities, the gap becomes visible before it becomes expensive. The point of a well-built delivery ecosystem, whether that is Jira, Confluence, or another tool your organisation already uses, is not to generate reports. It is to make reality visible in real time so decisions can be made on the basis of what is actually happening rather than what people assume is happening.

The leadership behaviour that makes all of this work

All three of these depend on something no tool or methodology can supply. Leaders who are genuinely curious about the gap.

I have worked with leaders who, when shown that the organisation was not executing the strategy they thought it was, got defensive. The data was questioned. The methodology was challenged. The people who surfaced the gap were quietly sidelined. And the gap continued.

I have worked with other leaders who, shown the same information, got curious. They asked questions. They went and sat with the teams. They changed how they communicated priorities. They made the connection between strategy and delivery a standing agenda item rather than an annual review. And the gap closed.

The difference was not the tools. It was not the framework. It was the willingness to be uncomfortable with the truth for long enough to do something about it.

A final thought

When I work with organisations, connecting strategy to delivery is one of the first things I address. Not by implementing a framework. By asking a simple question: if I sat with your teams tomorrow and asked them what your organisation's top three strategic priorities are, what would they say?

Most leadership teams cannot answer that question with confidence.

That is the gap. That is where we start.

From there we build the cascade. From vision to strategic goals to OKRs to quarterly initiatives to team-level delivery. Then we build the rhythm that keeps it live and the visibility that surfaces when it breaks down.

It is not complicated. But it requires honesty about where the organisation actually is, and commitment to staying in the work until the connection holds.

That is the difference between a strategy that exists and a strategy that executes.