Strategic Choice Cascade: Roger Martin's 5-Question Framework
The strategic choice cascade is a five-question framework for building a strategy that hangs together. SWOT, Porter's, and VRIO each answer a specific analytical question. The cascade sits above them as the integrative top of the stack, where situational analysis turns into a small set of explicit, connected choices the organization commits to.
This guide covers the five questions, how they connect, a worked example for an agency, when the cascade fits (and when it does not), and where it sits alongside the other frameworks. Build your own cascade with the interactive widget below, copy it, take it into your next strategy session.
Build Your Strategic Choice Cascade
The cascade reads top to bottom. Each choice constrains the next, and the connections are the strategy. Type your answer to each question; the widget seeds an example so you can see the shape, then reset to clear.
Build your strategic choice cascade
Answer each question in one or two sentences. The cascade reads top to bottom: each choice constrains the next. Iterate, copy, share with the team.
Need a sharper situational picture before you pick where to play? Run a SWOT analysis → first, then come back to fill in the cascade.
Quick answer. The strategic choice cascade is a strategy framework introduced by Roger Martin and A.G. Lafley in their 2013 book Playing to Win: How Strategy Really Works. It frames strategy as five connected choices. A winning aspiration. A deliberate choice of where to play. A clear way to win in that field. The capabilities required. And the management systems that build and sustain those capabilities.
"Hope is not a strategy." - A.G. Lafley, former CEO of Procter & Gamble
The 5 Questions of the Cascade
Each question sits at a specific level of the strategy. Skip any of them and the cascade breaks. The order matters because each later choice is constrained by the earlier ones; you cannot pick capabilities until you know how you intend to win.
| Question | What it answers | Common failure |
|---|---|---|
| 1Winning aspiration | The purpose. What does winning actually look like for this organization? | Treating it as a vision statement (vague platitudes) instead of a measurable outcome. |
| 2Where to play | The deliberate slice of the world: geographies, segments, channels, products. | "Everywhere" or "everyone" answers. Cascade fails without explicit choice of NOT playing in some segments. |
| 3How to win | The unique value or cost position that lets us win in the chosen field. | Vague differentiation (better service, higher quality) instead of a specific, defensible position. |
| 4Capabilities | The 3 to 5 organizational strengths required for the chosen way of winning. | Listing every capability the firm has, instead of identifying which ones are non-negotiable for THIS strategy. |
| 5Management systems | The structures, metrics, processes, and incentives that build and sustain those capabilities. | Skipping this question entirely. The cascade is most often abandoned at the systems step. |
Martin emphasizes that the cascade is iterative, not linear. You toggle back and forth between the boxes as later questions reveal that earlier ones need refinement. Where to play often shifts after the team realizes the capabilities required would take three years to build. That is the cascade working as intended.
Worked Example: SaaS Agency Defining Its Strategy
Same scenario as our other strategic-frameworks worked examples: a 15-person B2B SaaS marketing agency. The team has run a SWOT, sized the industry with Porter's, and audited resources with VRIO. The cascade pulls those analyses into one connected set of choices.
Winning aspiration. "Be the SEO partner of choice for B2B SaaS marketing teams in the 50-500 employee range, in North America by 2027." Specific, measurable, contains a deliberate market boundary. Not "be a great agency" or "grow to $10M ARR"; those are not aspirations, they are vague targets.
Where to play. B2B SaaS only (not e-commerce, not enterprise services). North America first, EU second. Mid-market (Series B to public), not pre-PMF startups or Fortune 500 buyers. Direct to in-house marketing leaders, not procurement-led RFPs. Notice what is excluded: that is where most cascades fail.
How to win. Deepest niche expertise (publish more useful B2B SaaS SEO content than any direct competitor) plus a productized starter offer that proves results in 90 days. Not "differentiated by quality and service" (every agency claims that). A specific position no one else owns in this niche.
Capabilities required. Three: an editorial team that ships 4 expert pieces per month, a productized SEO delivery process that works for 5+ clients in parallel, and a hiring engine for SaaS-trained SEO specialists. Anything else is nice to have, not non-negotiable.
Management systems. Editorial calendar with a named owner. 90-day ROI scorecard per client. Quarterly hire review pegged to the growth plan. Monthly partner referral close-rate review. Each system enforces one of the capabilities.
Five connected answers. Read them in sequence and the strategy hangs together. Change any one and the others have to adjust.
When to Use the Cascade (vs Other Frameworks)
The cascade is a top-of-stack framework. Reach for it when the analytical work is already done and the team needs to commit to a connected set of choices.
After analysis, before commitment. If you have run a SWOT, sized the industry with Porter's Five Forces, and audited resources with VRIO, the team is now staring at a wall of insights. The cascade is the conversation that turns those insights into strategy.
When the team disagrees on direction. Forcing answers to the five questions surfaces disagreements that vague strategy talk hides. If two leaders disagree on Question 2 (where to play), Question 3 (how to win) cannot be answered until that disagreement is resolved.
When the strategy is too long. If your strategy document runs 40 slides, the cascade collapses it to one page. That single page reveals which choices are weak, contradictory, or missing.
Skip the cascade when the team has not done the analytical work. The cascade is a synthesis tool. Without inputs from SWOT, Porter's, customer research, or competitive intelligence, the answers will be confident-sounding guesses. Run the analysis first.
Cascade vs Other Frameworks
The cascade does not replace the analytical frameworks. It sits above them as the place where their findings get integrated into commitment.
| Framework | Job it does | Where it fits with cascade |
|---|---|---|
| Strategic Choice Cascade | Integrative top: 5 connected choices that define the strategy. | The strategy itself. Other frameworks feed individual cascade questions. |
| Porter's Five Forces | Industry attractiveness analysis. | Feeds Question 2 (Where to Play): tells you which industries are worth playing in. |
| SWOT | Firm-level diagnosis (internal strengths/weaknesses + external opportunities/threats). | Feeds Question 2 and 3: situational input for choice of field and way to win. |
| VRIO | Internal resource audit for sustained advantage. | Feeds Question 4 (Capabilities): tests which capabilities are actually durable. |
| TOWS | Strategic option generation from SWOT findings. | Feeds Question 3 (How to Win): generates candidate strategies to choose from. |
| OKRs | Quarterly objectives with measurable outcomes. | Operationalizes Question 5 (Management Systems): the cadence that runs the strategy. |
The full strategy stack: PEST and Porter's for the macro and industry environment, SWOT for the firm-level situation, VRIO on the strengths to verify which are durable, TOWS to generate strategic options, the strategic choice cascade to commit to a connected set of choices, and OKRs to operationalize them. The KPI framework covers the standards layer underneath, and the OKR vs KPI bridge covers how those two measurement systems hand off. Each tool answers one question. The cascade is the question of how it all fits together.
Common Mistakes
Five patterns that produce a cascade that looks complete but is not actually a strategy.
- Vision instead of aspiration "Be the most innovative agency in the world" is a vision statement, not a winning aspiration. The aspiration must be measurable enough that you would know if you achieved it.
- "Everywhere" answers to Where to Play A choice of field requires explicit non-choices. If your Where to Play does not list segments and channels you are NOT pursuing, you have not answered the question.
- Generic How to Win "Differentiated through service and quality" is what every competitor's strategy doc says. The cascade demands a specific, defensible position no one else can credibly claim in your chosen field.
- Listing every capability Question 4 asks for the 3 to 5 capabilities required for THIS strategy, not the firm's full inventory. If your list runs to 15 items, the strategy has no focus.
- Skipping management systems Most cascades collapse at Question 5. Without explicit systems, the chosen capabilities never get built. The strategy becomes a document, not a thing the organization actually does.
Limitations
Two honest constraints worth naming.
Built for corporate scale. Lafley and Martin developed the cascade at P&G. For a 15-person agency, the management systems question can feel like overkill. You do not need a "system," you need the founder to commit to one weekly review. Adapt the rigor to the scale; do not abandon the question.
Iteration, not one-pass. The cascade looks like a top-down sequence on the page. In practice, answering Question 5 reveals that Question 2 was wrong, and you cycle back. Teams that treat the cascade as one-pass produce a tidy document that does not survive contact with execution.
"Strategy is an exercise of picking the choice that is most attractive from the universe of choices that are possible." - Roger Martin, former Dean, Rotman School of Management
What We Recommend
Run the cascade as the closing move of any strategy session, not the opening one. The five questions only produce useful answers when the team has shared analytical inputs to draw from. In practice: open the session with whichever analytical framework fits the question (Porter's for industry, SWOT for situation, VRIO for resources). Spend the second half answering the cascade as a team, with one person typing the answers in real time so disagreements surface immediately. Save the cascade as a living note in the shared planning space and reread it at the start of every quarterly review. The cascades that compound across years do so because each quarter the team revisits which answers still hold and which have shifted.
The comparison table above links to each analytical framework that feeds the cascade. For the growth-direction choice that often anchors Question 2 (Where to Play), see our Ansoff matrix guide. For Roger Martin's own deeper writing on the framework, his Medium essays are the canonical source.
A cascade is only as useful as the work it triggers. Rock combines chat, tasks, notes, and files in one workspace so the cascade, the analytical inputs, and the work to deliver the strategy all live together. One flat price, unlimited users. Get started for free.
