There is a five-minute test that tells you whether your strategy is operational or decorative. Try it on yours.
The test
- Pick any key result on your current quarter's plan.
- Identify the work items meant to move it.
- Pick one work item.
- Find the person doing it.
- Open their calendar for this week.
If steps 1 through 5 take more than fifteen minutes total, your strategy is not connected to your execution. It is connected to your slide template.
What the test actually measures
It measures whether the strategy graph exists as data or as narrative. Most companies have it as narrative — a story leadership tells in QBRs and town halls, reconstructed each time from memory and screenshots. Narrative breaks when the storyteller is unavailable, when the audience grows past the room, and when the work shifts faster than the next telling.
Data doesn't break. Data is queryable.
A strategy that cannot be traced in a Tuesday afternoon does not survive the Wednesday escalation.
The four failure modes you'll discover
Running the test on your own org will reveal one of four things:
- No KR has any work attached. The strategy is wish-listed; the teams are doing whatever they were doing.
- KRs have work attached, but the work shipped last quarter. Plans drifted; nobody updated the links.
- Work is attached, but nobody owns the link. Someone "made the deck" and stopped maintaining it after week two.
- Everything traces cleanly. You're in the top decile and you already know it.
Most teams find a mix of the first three. That mix, made visible, is the actual roadmap to a working operating system.
What a passing test looks like
A passing test takes under two minutes. Strategic bets show their objectives. Objectives show the work tagged to them, with owners and current state. The work tagged to them resolves to actual tickets in the team's tool of record — Jira, Linear, Asana, Monday — and those tickets sit on a person's plan for this week. The chain is unbroken.
The Vindaris view
Traceability is not a documentation problem. It is the substrate of an execution layer. If you can't follow a thread from bet to calendar, no amount of additional reporting will make the strategy real. The thread is the system.