Your shipped work is your real strategy. The deck is fiction.
Every organization has two strategies. The one in the doc — the one that gets presented at the offsite, cited in the all-hands, printed on the conference room wall. And the one revealed by what actually shipped last quarter. Those two strategies are almost never the same. The gap between them is where execution credibility goes to die.
What an organization actually believes shows up in the roadmap, not the strategy doc. The shipped work is the audit.
This is the lie that hides everything else. As long as the deck exists, leadership feels strategic. As long as the team is shipping, they feel productive. Neither side is checking whether the shipping matches the deck. So the gap grows quietly, sprint by sprint, until somebody — usually a board member, usually at the worst possible time — asks the question nobody on your team can answer: "What strategic outcome did this past quarter advance?"
If you can't answer that in one sentence, you don't have a strategy. You have a delivery rhythm with a strategy-shaped hole at its center.
The Strategy Drift Mechanism
Strategy doesn't get killed in a meeting. It gets killed in the cracks between meetings.
A sales call generates an urgent escalation. A customer support ticket reveals a bug that needs a fix. The CEO sees a competitor announcement and asks for a feature comparison. Each one is a small, defensible reprioritization. Each one nudges the sprint plan a few degrees off the strategy. None of them are wrong in isolation. All of them together are the strategy being silently rewritten by whoever yelled loudest that week.
By the end of the quarter, the team has shipped a coherent body of work — but it's coherent to the escalations, not to the strategy. The roadmap is the residue of the loudest voices, not the most important problems.
This is not a discipline failure. It's a visibility failure. Nobody is making the gap visible in real time, so nobody can defend against the drift. The deck and the demo never get put in the same room.
The Demo Is the Audit
Every team that ships software has, baked into its process, a built-in strategy audit. Most of them don't use it. It's the demo.
When someone presents what shipped this sprint, you have a free chance to ask: "Which line on the strategy doc did this advance, and by how much?" That's it. That single question, asked every demo, will surface the drift in real time. Not in a heroic quarterly review. Not in an offsite postmortem. In the room, in the moment, while the work is still warm and the decisions are still defensible.
Almost nobody asks it. Demos turn into status theater — "here's what we built, here's the next thing." The strategic linkage is assumed, never tested. By the time you check, the answer to "what did we ship for the strategy this quarter" is "I'm not sure, let me get back to you," which is a leader's polite way of saying the strategy is dead and the roadmap doesn't know yet.
I've watched this in every kind of org — startup, scale-up, enterprise. The shape of the failure is identical. The cure is identical too. It is a single repeated question at every demo, asked by someone who is willing to accept "this didn't advance the strategy" as a real answer instead of a personal attack.
Three Measurable Gaps
You don't need a consultancy to find the drift. You need three numbers:
1. Strategy-to-roadmap mapping rate. Take last quarter's shipped work — every meaningful release. For each item, can you trace it to a specific line on the strategy doc? Healthy orgs land at 70%+. Most orgs I run this with come in below 40%. The other 60% is escalations, fire-fighting, and "we always did it this way" work nobody can connect to anything strategic.
2. Interrupt-to-planned ratio. Pull two quarters of sprint data. What percentage of shipped work came from items planned at sprint start vs. items injected mid-sprint by escalation? If interrupts exceed 30%, your team is no longer executing strategy — they're executing customer support with a Jira board. The strategy doc is decorative at that point.
3. Demo-to-strategy linkage rate. Sit in your next four demos. Count how many shipped items were explicitly mapped to a strategic outcome by the presenter — without prompting. The number is almost always zero. Zero is the diagnostic. It means nobody on the delivery floor has internalized the strategy enough to articulate it spontaneously.
The roadmap is the truth. The deck is the wish. The gap between them is your real operating model.
Stop Defending the Deck. Audit the Shipped Work.
Stop presenting the strategy. Start auditing it against the demos.
The mistake most leaders make is doubling down on the doc — making it clearer, prettier, more thorough. The doc was never the problem. The visibility loop between the doc and the work was the problem. A perfect strategy doc with a broken audit loop is still a dead strategy.
Add the question to your demo cadence. "Which strategic line did this advance?" Make it routine. Make it boring. Make it the price of admission to the demo. Within a quarter, your team will start pre-answering the question because nobody wants to demo work they can't connect to a strategy line. The audit changes the work.
If you're a PM, not a VP: Run the same test on your own backlog this week. Pull your last sprint. For every shipped item, write the strategy line it advanced. The ones you can't write are the ones to bring up with your manager — not as a complaint, as a data point. "Forty percent of last sprint didn't ladder to anything in the strategy. What does that mean?" That's a conversation you can lead.
The Prompt
This week, do one thing.
Open your last demo. List every shipped item. Next to each one, write the specific line in your strategy doc it advanced. Be honest — don't backfill the connection.
Count how many you couldn't write.
Reply and tell me the percentage. I am collecting these. The pattern across orgs is uglier than most leaders are ready to admit.
Next week we put all three lies together — the diagnostic, the scoring, what to do when you discover all three are true at once.