The strategy execution gap: why strategy dies between the mandate and the money

The number on the slide is 62%. Someone at the far end of the table asks where it came from.

What follows is familiar. The analyst looks at the director. The director looks at the deck. Somebody offers to confirm it after the meeting. The true answer, which nobody gives because nobody in the room has it, is that 62% came from a cell in a consolidation workbook, filled from a status template, filled three weeks ago from a delivery tracker by a project manager who is not in the building today.

Nobody did anything wrong. The strategy is still going to fail on that pillar, and this meeting is where it will fail, quietly, by not deciding anything.

What is the strategy execution gap?

The strategy execution gap is the distance between what an organisation has formally committed to and what its money and its people are actually doing. It opens not because anyone disagrees with the strategy, but because the strategy is held in one set of documents and the delivery is held in another, and nothing structurally forces the two to agree.

Be precise about this, because the phrase usually describes a failure of will. It rarely is one. The objectives are clear, the leadership is committed, and delivery teams are working hard on things they believe matter. The gap opens in the mechanics: wherever a number has to be carried from one system to another by a person, and nothing checks that it arrived intact or on time.

Strategy does not die when it is written. It dies over the following twelve to eighteen months, in three specific places.

Where does the gap actually open?

The retyping problem

Between the delivery team and the committee, every number gets retyped.

An analyst requests status from twenty initiative owners. Each fills a template from their own tracker. The analyst consolidates twenty templates into one deck. A director softens the wording on three items. The deck goes up.

Two things happen in that chain and neither is dishonest. Information is lost at every hop, because a template has fewer fields than the tracker it was filled from. And each number is rounded gently toward the answer its author would prefer to give, because the person writing the status is the person who will be asked about it in the room. Twenty small roundings in the same direction produce a portfolio view that is systematically more comfortable than the portfolio.

Retyping also destroys the trail. Once a number has been copied by hand it cannot be traced back. That is what the 62% moment is.

The month-end lag

The portfolio view exists only as often as somebody assembles it. That is monthly, and it describes a period that closed before assembly started.

A committee meeting on the 20th is looking at the last day of the previous month, filtered through two weeks of consolidation. It is making funding decisions on a picture between three and seven weeks old. Everyone knows the picture is stale. Everyone treats it as current, because it is the only picture there is.

The cost is not inaccuracy. It is that intervention arrives after intervention was possible. A dependency that slipped in week one reaches the committee in week seven, by which point the downstream team has re-planned around it or lost the time.

Ownerless numbers

The quietest of the three. A KPI owned by “Corporate Services”. A benefit owned by “the programme”. A milestone owned by a job title that has been vacant since March.

A number owned by a department is owned by nobody. There is no one who is uncomfortable when it stops moving, no one who can explain what changed, no one to ask a second question. When it goes red the response is to schedule a workshop, because the first task is finding out who knows anything about it.

Such numbers also outlive their own relevance. A measure nobody owns is never retired, because retiring it requires someone to argue it stopped mattering. So measures accumulate, and each one lowers the attention available to the rest.

Why does more reporting not close the gap?

Because the instinctive fix makes each of the three mechanisms worse.

More reporting means more retyping, which means more loss and more rounding. It consumes the time of exactly the people who would otherwise be delivering. And it adds surface for the committee to read, pushing the meeting further toward reading and further from deciding.

Most struggling portfolios already produce more reporting than anyone can absorb. The numbers exist; they are simply not attached to the objectives they are supposed to explain, and by the time they are assembled they describe a past state.

What does closing the gap require?

Three things, in this order.

Traceability. Every initiative attached to the objective that funded it. Every objective attached to the measure that shows it moving. Not in a mapping slide, which goes stale within a quarter, but as a link in the record, so a change on one side is visible on the other without anyone maintaining the map. The test: can you rescope an initiative and see, without asking anyone, which objectives are now less well served?

Named ownership. Every objective, KPI, initiative, milestone and benefit carries an individual rather than a department. The individual can change; the field cannot be empty. This sounds administrative. It is the highest-yield change available to most offices, because a named owner turns a red status from a topic into a conversation with a specific person who already knows the answer.

It also makes decisions durable. A decision to accept a six-week slip, carrying a name and a date, is still legible two years later.

Live actuals. Delivery data arriving from where the work happens, on its own schedule, rather than being requested. This is the part most often deferred, because it looks like an integration project. It is also the part that removes the lag. Once actuals arrive continuously the monthly pack stops being assembled, not because someone automated the assembly but because it was never disassembled.

Order matters. Live actuals in a record with no traceability give you a fast view of disconnected activity, and traceability without named ownership gives you a map nobody can be asked about.

Which parts of the gap should stay open?

Here is where the argument needs qualifying, because taken to its conclusion it produces something worse than the problem.

A portfolio wired so tightly that every scope change escalates to the strategy office does not execute. It seizes. Delivery teams need room to re-sequence and absorb small slips without a governance event, and an office that can see everything is under constant temptation to respond to everything it sees. The difference between visibility and control is a discipline, not a feature.

The second risk is what traceability does to the people supplying the data. Trace a number to an individual and you have made that individual accountable, which was the point. Use the trace punitively two or three times and you have also taught everyone that early warning is dangerous. Data quality then degrades in a particular direction: statuses stay green longer, forecasts get revised later, bad news arrives pre-negotiated. No software fixes that. A committee that visibly rewards the owner who flagged a slip in week one might.

And there is a question nobody has answered well. The balanced scorecard and OKRs both assume what matters can be cascaded downward into measures. Some of what a government entity does resists that: policy work whose value shows up a decade later, capability held in reserve, coordination between entities that has no output of its own. Those things still have to be funded, and a record built around traceable measurement will quietly disadvantage them every cycle.

How would you know the gap is closing?

The signs are behavioural and they show up in the room.

The meeting stops opening with a page-by-page read of everything green. Questions get directed at a person by name rather than at the PMO. “We will come back to you on that” becomes rare, because the answer is in the record and can be produced while the question is still being asked. Committees move money between initiatives mid-year instead of only at budget time.

And the reporting cycle stops being an event. Nobody discusses the pack, because there is no pack.

Common questions

Is the strategy execution gap a leadership problem or a systems problem?

Usually a systems problem misdiagnosed as a leadership one. Leadership attention gets spent on whatever the record puts in front of it, and a record showing only a monthly summary of activity will absorb that attention into activity. Fix what the record connects before running another alignment exercise.

Do we need to replace our project tools?

No, and trying to usually stalls the work. Delivery teams should keep the tools they deliver in. What changes is that the governance layer above them holds the objectives, the measures and the links, and receives delivery data instead of requesting it.

What is the smallest useful first step?

Take the objective your leadership is asked about most often. Attach every initiative claiming to serve it, name an individual owner for each, and record a baseline for its KPI with the date it was taken. That usually surfaces more about the portfolio than a year of monthly packs did.

Where this comes from

We build TruMandate, a portfolio governance platform for government entities and large enterprises in the UAE and Saudi Arabia. This is the problem we were shown repeatedly before we built anything, in offices doing the work well and unable to prove it.