Cadence of Strategy Refresh
Strategy refresh cadence is the formal interval at which leadership re-tests strategic assumptions, kills bets that aren't working, and reallocates resources. Most companies confuse 'annual planning' with 'strategy refresh' โ annual planning is budgeting; strategy refresh is asking 'do our bets still make sense given what we've learned?' High-performing organizations run strategy refresh on three nested clocks: annual (re-baseline the 3-year horizon and capital plan), quarterly (rescore initiatives against current evidence, kill/double-down), and event-triggered (a competitor move, a regulatory shock, a tech inflection forces an unscheduled refresh). The cadence question is not 'how often do we plan' โ it is 'how often do we have license to change the plan.'
The Trap
The trap is calling the annual budget cycle a 'strategy review.' The annual cycle's center of gravity is allocating money against last year's strategy plus 5%, not testing whether the strategy is still right. By the time you discover a strategic bet is wrong in month 9, you've already burned 75% of the year's resources. The other trap is the opposite โ refreshing strategy every quarter so aggressively that the organization can't execute. Strategy that changes faster than the team can adapt becomes performative; teams stop investing in execution because they expect another pivot.
What to Do
Implement the three-clock model: (1) Annual: re-baseline the 3-year strategy at the offsite โ what bets are still right, what's no longer relevant, what new bets does the world require? Output is the next-year operating plan AND the multi-year capital plan. (2) Quarterly: at the QBR, rescore each strategic initiative on a 3x3 matrix (evidence-of-traction ร strategic-importance), kill bottom-left, fund top-right. Aim to kill ~10-20% of initiatives per QBR. (3) Event-triggered: define explicit triggers that force an unscheduled refresh โ a major competitor acquisition, a >20% miss to plan for two consecutive quarters, a regulatory or technology inflection. Pre-define them so the call to convene isn't political.
Formula
In Practice
Stripe's published 'Operating Principles' (and the broader practice described by Patrick Collison in interviews) emphasize a quarterly strategic review where the executive team explicitly revisits the assumptions underneath each major bet โ payments expansion, lending, climate, etc. โ and either kills or doubles down. The discipline of forced quarterly resource reallocation is credited with Stripe's ability to enter (and sometimes exit) adjacent markets faster than peers. A parallel discipline at Spotify, described in the Henrik Kniberg 'Spotify Engineering Culture' papers (2014), is the quarterly squad re-prioritization where every squad re-justifies its mission against current strategic priorities โ squads that no longer fit the strategy are disbanded or redirected. Both cases share the same insight: without a forcing function, organizations carry strategic baggage indefinitely. (Sources: Patrick Collison's published interviews on Stripe operating model; Kniberg, 'Spotify Engineering Culture,' 2014.)
Pro Tips
- 01
Pre-write your kill criteria. The hardest part of strategy refresh is killing bets you've championed. Pre-defining the metric thresholds at which a bet should be killed (BEFORE you have the data) removes the ego from the decision. 'If we don't have 50 paying customers in this segment by Q3, we kill the segment' is a written contract with your future self.
- 02
Time the refresh to resource decisions, not the calendar. The QBR should happen 4-6 weeks BEFORE the next quarter's hiring decisions and budget commits, not after. If your refresh happens after the org has already committed Q+1 resources, the refresh is theater because nothing can actually move.
- 03
Distinguish strategy refresh from execution review. The QBR can be ONE forum that does both, but the agenda must explicitly separate them. Mixing them makes the strategic questions ('should we still be in this market?') get drowned out by the execution questions ('why are we behind on the launch?').
Myth vs Reality
Myth
โFrequent strategy refresh signals strategic indecisionโ
Reality
The opposite is true: organizations that refuse to refresh strategy at evidence-driven intervals are signaling sunk-cost commitment, not conviction. Real strategic conviction means staking ground based on evidence and CHANGING ground when evidence changes. The companies that refresh quarterly with discipline outperform those that hold annual strategy as scripture.
Myth
โAnnual planning is sufficient for strategy refreshโ
Reality
Annual planning operates on a 12-month feedback loop, but markets, competitors, and customer behavior change on much shorter cycles. McKinsey's research on dynamic resource reallocation (Hall/Lovallo/Musters, 2012) found that companies in the top quintile of resource reallocation had 30% higher TSR than those in the bottom quintile โ and the differentiator was reallocation FREQUENCY, not strategy quality.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge โ answer the challenge or try the live scenario.
Knowledge Check
Your company runs a thorough annual strategy planning process every November and treats the resulting plan as the year's roadmap. After 3 years you notice a pattern: ~40% of initiatives launched in January are still being funded in November despite missing every milestone, while genuine new opportunities emerging mid-year don't get resourced until the NEXT January. What's the structural fix?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets โ not absolutes.
Annual Initiative Kill Rate (% of portfolio killed/redirected)
Mid-to-large enterprises with 15+ strategic initiatives in portfolioHigh-Performing
20-30%
Healthy
10-20%
Marginal
5-10%
Sunk-Cost Carrying
1-5%
No Real Refresh
<1%
Source: McKinsey research on dynamic resource reallocation (Hall/Lovallo/Musters, 2012)
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Stripe
2018-present
Stripe operates an explicit quarterly strategic review where the executive team rescores each major bet โ payments expansion, Stripe Capital, Stripe Climate, Atlas, Sigma, etc. โ against current evidence. Patrick Collison has discussed this rhythm publicly: bets that lack traction don't get carried indefinitely on inertia, and bets with strong signal get resource doubling. The discipline allowed Stripe to scale its product surface area dramatically without losing focus, because every quarter is an explicit decision point on portfolio composition. The 2022 cost-cut and 2023 Bridge acquisition both demonstrated the same operating muscle: clear-eyed quarterly reassessment leading to decisive moves.
Strategic Refresh Cadence
Quarterly (formal) + Event-Triggered
Product Surface Area
Payments โ 30+ products in 8 years
Portfolio Decision Discipline
Public examples of scaling back AND doubling down per quarter
Quarterly strategy refresh is not strategic indecision โ it is the only mechanism that lets a fast-moving company carry a broad portfolio without losing focus. Annual-only refresh would force Stripe to either narrow the portfolio or accept slow reallocation.
Spotify
2012-2018
Spotify's squad model (described by Henrik Kniberg in 2014) included an explicit quarterly squad mission review. Every squad re-justified its mission against current company priorities. Squads whose missions had become misaligned were either redirected, merged, or dissolved. The cadence โ quarterly, structured, public โ meant teams expected mission changes and built their backlogs to be redirectable. Without this cadence, the squad model would have created hundreds of independently-optimizing teams pursuing increasingly disconnected goals.
Squad Mission Refresh
Quarterly
Squad Count at Peak
~150+
Team Discipline
Backlogs designed to be redirectable
Squad-style autonomy without quarterly mission refresh creates strategic chaos. The cadence is what makes autonomy compatible with strategic coherence โ it's not a contradiction, it's a coupling.
Related concepts
Keep connecting.
The concepts that orbit this one โ each one sharpens the others.
Beyond the concept
Turn Cadence of Strategy Refresh into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h ยท No retainer required
Turn Cadence of Strategy Refresh into a live operating decision.
Use Cadence of Strategy Refresh as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.