Framework · 8 min read
Playing to Win (Strategic Choice Cascade)
A connected set of strategic choices and required capabilities.
A.G. Lafley and Roger L. Martin · View sources ↓At a glance
- Use this when
- You need to make explicit choices about where to play and how to win.
- What you will work towards
- A connected set of strategic choices and required capabilities.
- Bring to the reading
- A specific decision from your work and the customer evidence you have so far.
What it is
A five-question cascade of explicit, mutually reinforcing strategic choices, developed by A.G. Lafley, former CEO of Procter & Gamble, and strategist Roger L. Martin in Playing to Win: How Strategy Really Works (Harvard Business Review Press, 2013). The five questions run in order: what is our winning aspiration (a specific, falsifiable definition of what winning looks like, not a mission statement); where will we play (which markets, segments, and channels, and just as importantly, which we will not); how will we win there (the specific, defensible mechanism by which we beat the alternatives in that chosen field); what capabilities must we have to win the way just chosen; and what management systems support and reinforce those choices (the metrics, hiring criteria, and compensation structures that make the strategy stick day to day rather than decay back to old habits). The cascade's core discipline is that each answer must both follow logically from the one above it and demonstrably deliver it; a list of five answers that do not reinforce each other is not yet a strategy, just five separate opinions. This sits a level above the two operational frameworks already in this category. The Quarterly PMM Planning Framework translates business goals into a quarter's initiatives, and the Pragmatic Institute Framework scores whether specific operating boxes (enablement, business health) are functioning; neither one answers the prior question of what the underlying strategy actually is. This cascade is the missing layer: the strategic-choice architecture a quarterly plan should operationalise and a Pragmatic Institute-style scorecard should be checked against, not a competing planning ritual.
When to use it
- Quarterly planning keeps producing a list of initiatives with no clear strategic thread connecting them, because the underlying strategy, not just the quarter's priorities, has never actually been made explicit.
- A product line or segment's "strategy" is really a list of everything the team could plausibly do, rather than a chosen bet that also names what is being deliberately left out.
- Leadership disagreement over focus keeps resurfacing as a tactical argument when the real disagreement is an unstated difference over where to play or how to win, arguing about channels or messaging when the actual gap is upstream.
- A new segment, product line, or go-to-market motion is under consideration and needs a strategy behind it, not just a launch plan; running the 3-/7-/10-Step PMM frameworks or Complete GTM Workflow Stages on an unset strategic foundation just executes the wrong plan efficiently.
- Strategy has visibly drifted from what leadership assumes it is, evidenced by budget and headcount allocation that no longer matches any explicit statement of where the company is choosing to play.
Ownership
At a scaled company, the CEO or a business-unit or product-line leader owns the final cascade and its sign-off, since the "where to play" and "how to win" choices commit resources and organisational focus well beyond PMM's remit alone. PMM typically leads or co-leads the exercise for a specific product line or segment, supplying the market-sizing, segmentation, and competitive evidence that ground choices two and three in fact rather than opinion, and owns translating the finished cascade into positioning and messaging once it is set. At a solo or founding-PMM stage, that person runs the cascade directly with the founder or CEO, since there is no separate business-unit layer to negotiate the choices through; the aspiration and playing-field choices still ultimately rest with the founder, but the founding PMM is usually the one drafting and pressure-testing them.
How to apply it
- Define the winning aspiration. Write a specific, falsifiable statement of what winning looks like and for whom, by when, not an inspirational mission statement. Force an explicit trade-off: name at least one plausible aspiration the team is deliberately not pursuing, since an aspiration with no ruled-out alternative is not yet a choice.
- Choose where to play. List the specific markets, segments, geographies, and channels you will compete in, sourced from validated STP segmentation and market-sizing work, and name, just as explicitly, which segments or channels you are choosing not to pursue for now. A "where to play" answer with no excluded option attached is a wish list, not a choice.
- Choose how to win. Within the chosen playing field, name the specific, defensible mechanism by which you beat the available alternatives there, not a generic claim like "quality" or "great service" that any competitor could equally assert. Tie the mechanism to something a competitor cannot easily replicate within a year or two.
- Identify the capabilities required. List the specific organisational capabilities, not generic ones like "great execution", the chosen way of winning actually demands, and honestly assess which of them the organisation already has versus which represent a real, named gap.
- Identify the management systems needed. Name the specific metrics, hiring criteria, and compensation or incentive structures that reinforce the choices above in day-to-day operation. A cascade with no management system behind it reliably decays back into whatever behaviour the old metrics and incentives already reward, usually within a single quarter.
- Test the cascade for mutual reinforcement, both directions. Walk it top-down (does each choice logically require the one below it?) and bottom-up (does each choice actually deliver the one above it?). Any broken link in either direction means the cascade is not yet internally consistent, and needs revision before it is treated as final.
- Stress-test against a competitor's most plausible response. Ask what would have to be true for the "how to win" choice to fail, and what a capable competitor's best counter-move would look like. If the chosen mechanism collapses easily against a foreseeable response, revise it before committing resources.
- Publish the five choices as a single briefing document, and use it as the explicit north star that the Quarterly PMM Planning Framework's business goals, and any Pragmatic Institute-style operating scorecard, should trace back to rather than restate from scratch each quarter.
Example
Northlane, a fictional B2B expense-management SaaS company, had grown opportunistically across SMB self-serve, mid-market services firms, and early enterprise accounts, with one blended roadmap and one generic sales motion trying to serve all three. Win rate sat at 19% company-wide, and the roadmap was a running list of every feature any one segment had asked for, with no clear sense of which segment the company was actually building for. Leadership ran the Strategic Choice Cascade over three working sessions. The winning aspiration: become the default expense platform for mid-market professional-services firms of 100 to 1,000 employees within three years, explicitly ruling out enterprise as a primary near-term aspiration. Where to play: mid-market services firms in North America, explicitly not enterprise (a market where two entrenched competitors already ran 9-to-12-month implementation cycles Northlane could not resource) and not SMB self-serve (a segment where the company's own churn data showed 40% annual attrition, too price-sensitive to sustain the sales motion being built). How to win: configurability without enterprise complexity, evidenced by a two-week implementation playbook versus the category's typical three-month enterprise rollout, combined with a library of vertical-specific expense-policy templates for professional-services firms that a general-purpose competitor would need real time to replicate. Capabilities required: a dedicated rapid-implementation team, the policy-template library itself (which did not yet exist), and a mid-market-trained sales team, since the existing reps had been hired and trained for enterprise-style long-cycle selling. Management systems: implementation time became a tracked, reported KPI for the first time; sales compensation shifted from blended pipeline value to mid-market logo growth specifically; and hiring criteria for new sales reps changed to favour mid-market experience over enterprise pedigree. Within two quarters of restructuring the roadmap and go-to-market motion around these five choices, average implementation time fell from an unmeasured, informally "a few months" to a tracked 17 days, win rate in the mid-market segment specifically rose from 19% to 34%, and the company formally sunset its SMB self-serve tier, redirecting that engineering capacity into the policy-template library the "how to win" choice depended on.
Pitfalls
- Writing an aspiration and calling it a strategy. "Grow revenue 30% this year" is a goal, not a cascade; without the four choices that follow it, an aspiration alone gives no guidance on where to focus or how to actually win, and teams under it default back to trying to do everything. Recovery: refuse to treat any single answer as the finished exercise; require all five questions answered and cross-checked for mutual reinforcement before the cascade is considered strategy rather than ambition.
- Choosing a "how to win" that any competitor could equally claim. Answers like "great customer service" or "we care more" sound like a choice but commit the organisation to nothing specific and defend nothing against a determined competitor. Recovery: test every "how to win" candidate by asking whether a named competitor could credibly claim the exact same thing about themselves; if they could, the answer is not yet specific or defensible enough.
- Skipping the management systems step because it feels like an HR or operations problem, not a strategy problem. A well-reasoned cascade with no comp plan, hiring criteria, or tracked metric behind it reliably decays back into whatever behaviour the old incentives already reward, often within a single quarter, because nothing in day-to-day operation actually reinforces the new choices. Recovery: treat step 5 as mandatory, not optional; name at least one concrete metric, one hiring criterion, and one incentive change before considering the cascade complete.
How the ideas connect
Choose where to go next
Make it useful
Bring it back to your work.
Name one decision this guide could help you make. Write down the evidence you need, the output you would produce, and how you would know it was useful.
Check your understanding
Practise applying Playing to Win (Strategic Choice Cascade) in five short scenarios.
5 practical scenarios. Choose an answer, explore the reasoning, and revisit the guide whenever you need.
Sources
- A.G. Lafley and Roger L. Martin, "Playing to Win: How Strategy Really Works", Harvard Business Review Press (2013)
- Roger Martin, "Decoding the Strategy Choice Cascade", Medium (2023)
← All entries in Strategy & Planning · Try the category quiz