Between strategy and delivery

Your strategic goals live in a document. Your projects live in your project tool. Between them is a gap no one owns, and where the data graveyards grow. An article about what happens in the gap.

Picture a leadership meeting in January. The year's strategy is set, written up in a presentation everyone is happy with. Twenty initiatives are to be prioritised across five strategic themes. It all looks coherent.

Six months later, another leadership meeting. On the table is a simple question. "How is the strategy actually doing?"

Then comes the silence. Not because no one knows anything, everyone knows something. The CFO goes by budget and outcome, the CIO by Jira, the strategy lead by what the unit managers reported. Three versions of the same question, none complete.

This is the gap. No one is doing anything wrong. It's that no one stands where the answer would be.

Where the gap sits

The strategy lives in a document. It says what you want to achieve.

Delivery lives in a project tool, Jira or a large Excel. It says exactly what the developers do next week.

But no one translates between them. No one says that of the twenty initiatives, six have delivered, eight are delayed but on track, four are paused and two were cancelled without anyone noticing. No one says that of the five themes, three are well-supplied, one thinly staffed and one starving entirely.

The information isn't missing. It's there, spread across people, systems and quarterly reports. But the aggregation is manual, half-finished and always retroactive.

Three common symptoms

The gap usually takes three forms.

1. Report wars at quarter-end

A week before the quarterly report, the project office kicks off a frantic collection. Emails to unit managers, Excel templates back and forth, different readings of "on track". By the time the PowerPoint is on the table, half the room knows it is already out of date.

2. Reprioritisations that surprise

Mid-quarter someone discovers a critical initiative is blocked. It turns out two others were waiting on the same thing, but no one saw it until now. Panic calls, reprioritisation, other initiatives take a back seat. The plan was never wrong. It was just never validated against reality.

3. "What did we actually do last year?"

At year-end everything is to be evaluated. Then you discover that no one can answer. There are completed projects, there are costs, there are changed KPIs. But the link between them you have to reconstruct from memory, email and scattered documents.

You don't have a strategy problem. You don't have a delivery problem. You have a translation problem between the two, and it's no one's job to solve it.

The data graveyards

Valuable data is created all the time, cost outcomes, status updates, dependencies, goal attainment. But it is never aggregated into a usable picture of the portfolio.

It ends up in data graveyards. Excel files on unit managers' OneDrive, colour-coded reports no one reads, status fields in Jira no one correlates against strategic goals. The data is there, but it's fragmented and only readable by whoever happens to know where it sits.

Why no one solves it

This is the crux. The gap exists because it isn't anyone's job to stand there.

The CFO owns the finances, the CIO delivery, the strategy lead the direction, the unit managers their own areas. Each does their part, but no one is tasked to continuously translate between strategy and delivery.

When someone finally does, at the quarterly report or year-end, it becomes a heroic one-off by a PMO or a borrowed analyst. Because it's no one's ongoing responsibility, it becomes an event, not a process. And events are always retrospective.

What solving it means

Solving the gap is not about replacing the strategy process.

What we're talking about has a name, strategy visualisation. No dashboard, no PowerPoint with arrows. A shared picture of the journey between strategy and delivery, where both sides can stand in front of the same surface and point at the same thing. Then the translation stops being a heroic effort four times a year and becomes an ongoing reality.

It's not about switching project tools either. The strategy is still yours, delivery still the project office's. But the aggregation between them becomes continuous, so the question "how is the strategy doing?" has an answer every day.

It's an operational shift, not a strategic one.

When this isn't your problem

Not every organisation has the gap. Or not in a form where it's worth solving.

If you have under ten active initiatives and sit in the same room every day, there's no translation that needs to happen. The information flows informally, and that's enough. Don't introduce systems where loose conversation already solves the problem.

But somewhere between ten and thirty initiatives the informal stops being enough. Then the data graveyards grow faster than anyone notices, because the gap is invisible until someone actually tries to cross it.

A review gives you a way to cross the gap regularly. It's a workshop and two steps. In the workshop you set the organisation's goals, each manager's business goals and the assessment criteria together, and the criteria are set before the initiatives are known. Then the initiatives are assessed. Finally leadership goes through the whole picture with the simulator in front of them and locks the decision as a timestamped decision point. We facilitate and document, the content and the decisions are yours.

It leaves no binder behind, but something living in the platform. The goal map shows which goals are well-supplied, thin or starving, so the question "how is the strategy doing?" has an answer without a quarterly close. And the decision history lets you set then against now, what applied at the last decision point and what applies today. The translation becomes a surface you can return to, not an event four times a year. We walk through how it works step by step in the review.