Your strategy might be lying to you. There are three places to check.
For three weeks I've been pulling apart the lies most product organizations tell themselves about strategy. We're aligned. We have priorities. We have a strategy. Each one feels true in the room. Each one quietly fails the moment work hits the calendar. Each one has a measurable test most leaders refuse to run.
This week I'm putting all three together into one diagnostic you can run on your org in under two hours. Score it. Sit with the result. Then act.
The Three-Lie Diagnostic: alignment test, priority test, shipped-work test. Three numbers. One uncomfortable conversation. The clearest picture of your strategy you've had in a year.
How the Three Lies Compound
The three lies are not independent. They cascade.
When alignment is fake (Lie #1), people leave the room with three different versions of the strategy. Without a shared version, leaders can't make real cuts — every "no" feels like favoring one interpretation over another. So priorities inflate to accommodate everyone (Lie #2). When priorities are fake, the team makes its own decisions about what to ship — because the official priorities can't constrain anything. So the shipped work drifts away from the strategy doc (Lie #3). By the time the board asks what got accomplished, nobody can map it back to anything.
Each lie protects the lie below it. Each lie makes the lie above it possible to ignore. Together they become a closed loop nobody inside the org can break, because every leader has incentive to maintain the appearance that all three are working.
The diagnostic breaks the loop by making the gap visible — fast, cheap, and undeniable.
Run the Diagnostic
Set aside two hours this week. Block the calendar. Do not delegate.
Test 1 — The Three-Person Alignment Test (30 minutes)
Pick three people from three different functions on your team. Ask each, separately:
"What is the single most important thing this team is working on this quarter, and what are we explicitly not doing in order to protect it?"
No doc reference. No group setting. Note answers verbatim.
Score: Pass = three answers within 80% (same priority, same tradeoff). Fail = anything less.
Test 2 — The Casualty Audit (30 minutes)
Pull your stated priority list. For each item, ask: "What did we kill to put this on the list?" Then count the items where the answer is "we just added it."
Score: Pass = at least one visible casualty per priority. Fail = casualty list shorter than priority list.
Test 3 — The Demo Mapping Audit (60 minutes)
Take your last sprint or release. List every shipped item. Beside each, write the specific line on the strategy doc that item advanced. Be honest — do not backfill connections.
Score: Pass = 70%+ items map to a strategy line. Fail = below 70%.
That's the whole instrument. Three tests. One scorecard. Two hours.
What the Score Means
All three pass: Rare. If this is you, you've earned it — go apply the same discipline to the next quarter's strategy. Do not assume the score holds. Run it again next quarter.
One fails: Leverage point. The failed test tells you exactly where to focus the next 90 days. If alignment fails, you have an authoring problem — the strategy isn't legible enough to align around. If priorities fail, you have a leadership problem — somebody needs to make the cuts publicly. If the shipped-work map fails, you have a visibility problem — the demo audit fixes most of it.
Two fail: Strategic drift. The org is operating partially on inertia and partially on the loudest voices. Do not start a "new strategy." Fix the failed tests first — adding more strategy on top of broken plumbing makes it worse.
All three fail: Strategic crisis. This is more common than it sounds. The org has been functional but not strategic for some period of time, and nobody has named it. Do not panic. Do not hold an offsite. Sit with the score. Pick the test you can fix fastest — usually the demo audit, because it's a process change, not a politics change. Run the cycle again in 90 days.
A failed test is not a failure of leadership. A refusal to run the test is.
What This Is Not
This is not a strategy generator. The diagnostic does not tell you what your strategy should be. It tells you whether the strategy you already have is alive or dead. If the strategy itself is bad, the diagnostic will surface that — but fixing it is a different exercise entirely.
This is not a one-time exercise. The lies grow back. Run the diagnostic quarterly. The score is a vital sign, not a diploma.
This is not a replacement for the harder work of authoring a real strategy. It's the audit that tells you whether the authoring work is paying off. Most leaders skip the audit because it might tell them the work isn't paying off. That's exactly why it's worth running.
For PMs Who Don't Run the Org
Run all three tests on your own scope.
Ask three teammates what they think the team's #1 priority is. Pull your last sprint and try to map every shipped item to a strategy line. Look at your own priority list and find the items you added without killing anything.
You probably don't have authority to fix all of it. You do have authority to bring the data to your manager — not as a complaint, as a diagnostic. "I ran the three-lie audit on our team. Here's what I found. What do we want to do about it?"
That conversation either changes things or tells you something about the org you needed to know.
What I Do With This in Workshops
The Three-Lie Diagnostic is the first exercise I run with most product leadership teams I work with. It surfaces in two hours what most teams have been avoiding for two quarters. The conversation that follows — about why the lies grew, which one to fix first, who has authority to act — is the actual workshop.
If you ran the diagnostic this week and the score scared you, that's useful information. If you'd rather have someone facilitate the conversation that comes after, that's what I do.
The Prompt
This week:
Block two hours. Run the three tests. Score honestly. Reply with one of the four results — all pass, one fail, two fail, all three fail.
I read every reply. The pattern across orgs is data I use to keep this work sharp.
Next week: a new arc. But this diagnostic doesn't expire — keep it. Run it next quarter. The score will tell you whether anything you tried in between actually worked.