A strategy set in January isn't guaranteed right in August. This is the quarterly self-audit that forces a team to test whether its strategy still holds — before the market tests it for them.
▸ Try the interactive toolA strategy set at the start of the year is not guaranteed to be right months later. Competitors launch, markets shift, your best customers reveal problems you didn't anticipate, and OKR cycles surface where your assumptions were wrong. The Strategy Review Checklist is a quarterly self-audit — a structured set of questions across several domains — that forces a team to test whether its strategy still holds.
The checklist isn't about rewriting strategy every quarter — that would be the opposite failure. It's about deliberately re-examining the assumptions the strategy rests on, so that when one breaks, you notice on your own schedule rather than being surprised by the market. A strategy that's never re-tested isn't stable; it's just unexamined.
Strategies don't usually fail loudly. They quietly stop being true as their underlying assumptions expire, and the team keeps executing a plan that no longer fits.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| Never reviewing | The strategy silently goes stale; you find out when results miss. | A scheduled audit catches expired assumptions before they cost a quarter. |
| Reviewing too often | Constant rewrites create whiplash and signal instability. | A quarterly cadence balances stability with responsiveness. |
| Reviewing only results | Hitting OKRs can mask a strategy that's drifting from the market. | The checklist tests assumptions and context, not just the scoreboard. |
| Confirmation bias | Teams review to reassure themselves, not to find problems. | Structured questions force you to look where you'd rather not. |
Is the core challenge you identified still the most important one? Markets move — the obstacle that defined your strategy may have shifted or been solved.
What's changed since last review? New entrants, competitor moves, shifts in substitutes. A strategy built against last quarter's competitors may be aimed at the wrong target.
Are the segments, needs, and willingness-to-pay you assumed still holding? New customer learnings often quietly invalidate a founding assumption.
What did the last OKR cycle teach you about where you were wrong? Treat misses as evidence about the strategy, not just execution.
Most reviews end in “hold” — and that's fine. The point is that holding is now a decision, not a default.
A team's strategy assumed their main competition was a set of named rivals and built positioning around beating them. A quarterly review asked the simple question “what's changed?” — and surfaced that the real threat had become a free, good-enough alternative users were adopting instead of any paid tool.
Their entire positioning had been aimed at the wrong competitor for a quarter. The review didn't force a panic pivot; it adjusted the diagnosis and re-pointed the strategy at the actual threat. Without the scheduled audit, they'd have learned the same thing from a bad results quarter instead.
The deliverable is a short written record per quarter: what was tested, what changed, and the hold/adjust/pivot decision — so drift is visible over time.
| Domain | The question | Watch for |
|---|---|---|
| Diagnosis | Is the core challenge still the right one? | Solving yesterday's problem |
| Competition | What's changed in the landscape? | Aiming at the wrong rival |
| Customers | Do the segment & need assumptions hold? | A quietly expired assumption |
| Internal | What did OKRs teach us? | Blaming execution for a strategy miss |
A strategy that's never re-examined isn't stable — it's just unquestioned. The checklist turns “we're sticking with the plan” from a default into a deliberate, defensible decision.
The subtle skill is reviewing at the right altitude. Reviewing results tells you whether you're executing; reviewing assumptions tells you whether you're executing the right thing. A team can hit every OKR while its strategy slowly detaches from reality. The checklist's discipline is to look past the scoreboard at the assumptions underneath — and to do it on a calendar, before a bad quarter forces the look.
An audit that depends on someone remembering never happens. Put it on the calendar.
Constant pivots are as harmful as never reviewing. Most reviews should end in “hold.”
Good results can hide strategic drift. Test assumptions, not just outcomes.
If the review only ever confirms you're right, it's theatre. Look for the breaking assumption.
The checklist tests whether the stack still holds top-to-bottom as conditions change.
Each review re-runs Rumelt's kernel — is the diagnosis still accurate, the policy still right?
Five Forces, PESTLE, and competitive analysis supply the “what's changed?” evidence.
The OKR cycle's results and misses are primary input — they reveal where assumptions were wrong.
Take a strategy you're close to. Answer: is the core challenge still right? what's changed competitively? do the customer assumptions hold? what have results taught us?
For each, decide honestly: does this support holding the strategy, adjusting it, or pivoting?
If you can't answer “what's changed?” with anything specific, that's a sign the strategy hasn't been examined closely enough — not that nothing has changed.