A strategy review exists to re-decide three things: where capital goes, where headcount goes, and which bets are still live. Anything else is decoration. The design that actually produces those decisions is a tight three-block agenda, a real pre-read, decision-grade evidence, and a written commitment memo published within 48 hours.
Why most strategy reviews are broken
The default quarterly is a sequence of functional read-outs. Sales presents pipeline. Product presents the roadmap. Finance presents the budget. By the time the team gets to the strategic questions, the room is exhausted and the answer is "let's take this offline".
The structural problem is that functional read-outs are a horizontal cut of the business, and strategy is a vertical cut. Strategy is about what changes, what stays the same, and what gets killed. A read-out is about what is happening. They live on different time horizons and produce different decisions.
The one thing a strategy review is for
A strategy review has exactly one purpose: to produce a small number of binding decisions that change how the next quarter is resourced. If the meeting ends without a change to capital, headcount, or priority, it was a workshop.
That framing is unpopular because it forces the team to make commitments in the room instead of deferring them. It is also the only framing that produces a strategy review that survives more than two cycles before quietly turning back into a status update.
The three-block agenda
The agenda is the same every quarter. Repetition is the feature; the team learns the shape and stops debating logistics.
- Block one: the read. Ninety minutes. A grounded read of the last quarter against the bets that were committed to. Driven by the navigation layer, not by opinion. The output is a shared understanding of what is true.
- Block two: the kill list. Sixty minutes. Every active bet is on the table. Three categories: keep, kill, double. Defaulting to "keep" is not allowed; the owner has to defend it.
- Block three: the commit. Ninety minutes. The next quarter outcomes, the resources behind them, the decision owners, and the kill criteria. Recorded live.
This sits inside the broader cadence stack covered in the operating cadence stack. It is not the only meeting that matters; it is the only one that re-allocates resources.
The pre-read is the meeting
Most of the work happens before the room opens. A pre-read distributed 48 to 72 hours ahead of the session, read by every attendee, is the difference between a strategy review and a series of presentations.
The pre-read is short, written, and structured the same way every quarter:
- One page on the last quarter against commitments. Numbers, not narrative.
- One page per active bet. Status, leading indicators, owner recommendation.
- One page on the navigation layer: where the forecast moved and why.
- One page of proposed kills, doubles, and new bets, with the case for each.
The rule is simple. If you did not read the pre-read, you do not get to speak in the room. Two cycles of holding that line and the team adapts.
Evidence that earns a seat at the table
Not every input deserves equal weight in a strategy review. We use a three-tier standard:
- Tier one. Auditable data from the navigation layer. Outcomes, leading indicators, forecast. See how to build that layer.
- Tier two. Customer evidence. Named accounts, named conversations, churn diagnoses, win-loss themes. Not vibes.
- Tier three. Operator judgment, explicitly labeled as such. Useful for framing, never sufficient on its own.
A claim made in the room without at least tier two backing is routed to the issues list, not debated. This sounds harsh; it is the single biggest improvement we see when teams adopt it.
Making commitments that survive the quarter
The output of the meeting is a one to two page commitment memo, published within 48 hours, structured as:
- The three to five bets that are live next quarter, each with one owner.
- The capital and headcount allocated to each bet, explicitly.
- The leading indicators that will tell the team it is on or off track by mid-quarter.
- The kill criteria: the conditions under which the bet ends early.
- The bets that were killed this quarter and the rationale.
The kill section is the most important and the most often skipped. A strategy review that only adds bets, never removes them, will sprawl until execution is meaningless.
Six mistakes that kill the review
- Letting it become a quarterly board prep. Boards consume strategy, they do not set it. Run the internal review first.
- Functional read-outs as the spine. Read-outs go in the pre-read. They do not consume room time.
- No pre-read, or an unread pre-read. Without it you are running an improv session.
- "Let's table that". The phrase that ends strategy reviews. Force a decision or an explicit defer to the next layer.
- No kill criteria on bets. Bets without kill criteria become budget line items forever.
- No written commitment memo. If it is not written down within 48 hours, it did not happen.
A 90 day rebuild
- Quarter 1. Run one full review with the three-block agenda. Expect the first block to overflow. Hold the structure anyway.
- Quarter 2. Add the pre-read. Tighten the evidence standard. The quality of the room jumps noticeably.
- Quarter 3. Add the kill list discipline. This is the quarter where the team learns to remove bets, not just add them.
- Quarter 4. Review the design itself. Tune the time blocks, the pre-read sections, and the cadence with the rest of the operating stack. See the strategy pillar on the framework page.
Score your strategy review against a working design.
The ASCEND assessment grades how your team allocates capital and attention each quarter. Ten minutes, no signup, and a clear read on which block is the weakest.