Here's a small diagnostic you can run on your own company in under fifteen minutes, by yourself, without involving consultants or scheduling a workshop. It is brutal, and it is fair, and the result tells you almost everything you need to know about whether your strategy is real or performative.
The test
Pick any key result on your current quarter's plan. Not the easy one — any one. From there, identify the work items that are supposed to move it. Pick one work item. Find the person responsible for it. Open their calendar for this week and find the slot where they are doing it.
That's the whole test. Five steps, one chain. Bet → objective → key result → work item → owner → calendar.
If the five steps take you more than fifteen minutes total, your strategy is not connected to your execution. It is connected to your slide template. The chain exists in narration only. Somebody, somewhere, can tell you a story about how the work ladders up to the bet. Nobody can show you.
What the test actually measures
The test 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 is a beautiful artifact when it's well told. It also breaks the moment the storyteller is unavailable, the audience grows past a single room, or the underlying work shifts faster than the next telling.
Data doesn't break in those ways. Data is queryable. The difference between a strategy you can query and a strategy you have to retell is the difference between a system and a performance.
A strategy that cannot be traced in a Tuesday afternoon does not survive the Wednesday escalation. When something blows up — a customer churns, a competitor moves, the CEO needs an answer for the board — the question is always some variant of "show me what we're doing about this." A traceable strategy resolves that question in two clicks. An untraceable one resolves it in two weeks of frantic Slack threads and screenshot collation, during which the underlying problem gets worse.
The four failure modes you'll discover
Run the test on your own org and you'll land in one of four places. Most companies live in a mix of the first three.
The first mode is no key result has any work attached. The strategy is wish-listed; the teams are doing whatever they were already doing; nobody ever actually wired the deck to the backlog. This is more common than you'd think, especially in companies that "did OKRs once" and then quietly drifted.
The second mode is KRs have work attached, but the work shipped last quarter. Plans drift faster than the document gets updated. Whoever made the strategy deck did the linking once at the offsite and stopped maintaining it after week three. The chain technically exists. It's just pointing at corpses.
The third mode is work is attached, but nobody owns the link. Someone made the deck. Someone else owns the work. Neither of them owns the connection between the two. So when the work changes or the strategy clarifies, the link rots in place. Everybody assumes the other person updates it.
The fourth mode is everything traces cleanly. You're in the top decile and you already know it. You're probably also not the audience for this essay.
The point isn't to feel bad about which mode you're in. The point is to make the mode visible. The mix of failure modes, surfaced honestly, is the actual roadmap to a working operating system — far more useful than another planning offsite that produces another deck that produces the same four failures next quarter.
What a passing test looks like
A passing test takes under two minutes, end to end. You open the strategy view. You pick a bet. You see the objectives that ladder to it, with named owners. You see the key results for each objective, with current state and trend. You click into a key result and see the work tagged to it — actual tickets in the team's tool of record, whether that's Jira, Linear, Asana, or Monday. You click into a ticket and see the person assigned and the slot on their calendar this week. The chain is unbroken. Nothing requires reconstruction.
Critically, a passing test is reversible. Pick a ticket. Click upward. End at a strategic bet. That round trip — bet to ticket and ticket to bet, both navigable — is the actual definition of a coherent execution layer. If only one direction works, you have a report. If both directions work, you have a system.
The Vindaris view
Traceability is not a documentation problem. You will not solve it by writing better strategy memos or hiring a chief of staff to maintain a spreadsheet. It is the substrate of an execution layer — the data model that holds bets, objectives, work, owners, and capacity as connected objects rather than as separately authored documents.
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. Until that thread exists as data, every QBR is a séance — leadership trying to summon the spirit of the January offsite through interpretive performance — and every team is quietly doing the work they were already going to do anyway.