Between strategy and delivery

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

Picture a leadership meeting in January. The strategy for the year is set. It's framed in a deck everyone is happy with, approved, communicated. Twenty initiatives are to be prioritized over the year, distributed across five strategic themes. Everything looks coherent.

Six months later, a different leadership meeting. The question on the table: "How is the strategy actually going?"

That's when the silence comes. Not because no one knows anything — everyone knows something. The CFO has their view based on budget and actuals. The CIO has theirs based on Jira data. The chief of strategy has theirs based on what unit heads have reported in. Three different versions of the same question, none of them complete.

This is the gap. It's not that anyone's doing something wrong. It's that no one is standing in the place where the answer would be.

Where the gap sits

Strategy lives in a document. Or a presentation. Or on an internal communications page. It's clear in its own way — it states what you want to achieve.

Delivery lives in a project tool. Jira, Azure DevOps, or a large Excel file. It's detailed in its own way — it states exactly what the developers are doing next week.

But no one translates between them automatically. No one says "of the twenty initiatives in the strategy, six have delivered fully, eight are delayed but on track, four were paused, two were cancelled without anyone noticing." No one says "of the five strategic themes, we'll likely meet three, one will land around 60 percent, and one won't come close."

It's not that the information is missing. It exists. Spread across people, systems, and quarterly reports. But the aggregation is manual, half-finished, and always retrospective.

Three common symptoms

How do you notice you have the gap? It usually shows up in three ways.

1. Reporting battles at quarter-end

A week before each quarterly report, executive assistants and the project office run a frenetic data collection. Emails to unit heads. Excel templates back and forth. Different definitions of "on track." Two weeks later, a slide deck lands on the table — and already by the time it's presented, half the room knows it's outdated.

2. Re-prioritizations that surprise

Mid-quarter, someone discovers that a critical initiative is blocked. It turns out two other initiatives were also waiting on the same thing — but no one had seen it until now. The result: emergency meetings, re-prioritization, other initiatives have to step aside. The original plan was never wrong — it was just never validated against reality.

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

At year-end, it's time to evaluate. That's when you discover that no one can answer the question. There are completed projects. There are costs. There are changes in KPIs. But the connection between them? You have to reconstruct that from memory, email history, 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 no one has the job of solving it.

The data graveyards

This is what happens in the gap, in concrete terms. Valuable data is being created continuously — cost actuals, status updates, dependencies, goal progress — but it isn't being aggregated into a usable view of the portfolio.

It ends up in data graveyards. Excel files in unit heads' personal storage. Color-coded quarterly reports no one reads. Status fields in Jira that no one extracts and correlates against strategic goals. The data is there. But it's fragmented, inconsistently coded, and only readable by whoever happens to know where it lives.

Why no one solves it

This is what's actually decisive. The gap exists because it's no one's job to stand there.

The CFO owns the finances. The CIO owns delivery. The chief of strategy owns direction. Unit heads own their own areas. Each does their job — but no one has the mandate to continuously translate between strategy and delivery.

When someone finally does — at quarterly reports, at year-end — it becomes a heroic effort by the PMO, a consultant, or an analyst brought in. And because it isn't anyone's ongoing responsibility, it doesn't become a continuous process either. It becomes an event. And events are always retrospective.

What it means to solve it

Solving the gap doesn't mean replacing the strategy process.

What we're talking about has a name: strategy visualization. It's not a dashboard, not a PowerPoint full of arrows. It's 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. Once it exists, the translation stops being a heroic effort someone performs four times a year. It becomes an ongoing reality.

It doesn't mean changing project tools either. The strategy is still yours. Delivery is still the project office's. But the aggregation between them becomes continuous instead of quarterly, so the question "how is the strategy going?" has an answer every day, not just four times a year.

It's an operational shift rather than a strategic one.

When this isn't your problem

Worth saying: not all organizations have the gap. Or at least not in a form where it's worth solving.

If you have fewer than ten active initiatives and leadership sits in the same room every day — there's no translation that needs to happen. The information flows informally. That's okay. Don't try to install systems where casual conversations already solve the problem.

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