Playing To Win

Playing to Win

Concept of the skill

Playing to Win treats strategy as five mutually reinforcing choices, not as a plan, goal list, or analysis deck.

Concept Card

What it is: Playing to Win is A.G. Lafley and Roger L. Martin's strategy-cascade method. It frames strategy as an integrated set of five choices: winning aspiration, where to play, how to win, must-have capabilities, and management systems.

Mental model: Strategy is not a document that collects goals and initiatives. It is a coherent choice system. Each answer narrows and constrains the next answer, then the later answers pressure-test the earlier ones.

Why it exists: Agents often produce generic strategy prose: "grow revenue," "serve customers," "differentiate," "execute well." The cascade forces the missing choices into the open: which customers, markets, channels, offers, advantage, activities, capabilities, measures, and routines.

What it is not: It is not an industry attractiveness analysis, a moat taxonomy, an OKR tree, a roadmap, a backlog-prioritization table, or a financial model. Those can support the cascade, but the cascade owns the integrated strategy choice.

Adjacent concepts: Strategic choice cascade, strategy choice, where-to-play/how-to-win, activity systems, capability systems, reverse testing, competitive advantage, trade-offs.

One-line analogy: Playing to Win is a set of interlocking gears: if one gear turns, the others must still mesh.

Common misconception: The five questions are not five independent brainstorm prompts. They must fit together and reinforce each other.

Coverage

This skill teaches agents to:

1. Convert strategy prose into the five cascade choices.
2. Separate strategy from planning, goals, initiatives, and analysis.
3. Make the where to play choice concrete across customer, geography, channel, product/service, value-chain stage, and occasion.
4. Make the how to win choice a real advantage, not a slogan.
5. Identify capabilities that are necessary because of the how-to-win choice.
6. Define management systems that build, measure, and sustain the capabilities.
7. Pressure-test fit across all five choices.
8. Surface trade-offs, no-go choices, and assumptions that must be true.

Philosophy of the skill

Playing to Win is useful because it makes strategy expensive in the right place: choice. A vague strategy feels easy because it refuses trade-offs. A real strategy creates tension. It chooses one arena over another, one advantage logic over another, one capability system over another, and one management rhythm over another.

The cascade is not a guarantee that the strategy is correct. It is a forcing function that makes the strategy inspectable. Once the choices are explicit, an agent can ask whether they fit, whether they are feasible, whether competitors can copy them, and what evidence would change the decision.

The Five Choices

Workflow

1. Extract the current implied strategy

Read the existing plan and identify what it already implies.

Current aspiration:
Current where-to-play:
Current how-to-win:
Current capabilities:
Current management systems:
Unstated assumptions:
No-go choices:

If the source material only contains initiatives, infer the missing choices and label them as inferred. Do not present inferred choices as confirmed.

2. Make where-to-play concrete

Specify the arena with at least three dimensions when possible.

The test: a competitor should be able to tell what you are choosing not to pursue.

3. Make how-to-win falsifiable

Describe why the chosen customers will prefer this offer against the relevant alternative.

Strong how-to-win statements name:

• the target customer's job or pain,
• the alternative they would otherwise use,
• the specific value equation you improve,
• the hard-to-copy system that makes the improvement durable enough,
• the evidence that would show the advantage is working.

Weak how-to-win statements use adjectives without mechanism: better, easier, smarter, delightful, AI-powered, premium, trusted.

4. Tie capabilities to the advantage

Capabilities are not departments. They are things the organization must do unusually well because the how-to-win demands them.

Use this check:

If our how-to-win is true, we must be excellent at:
1.
2.
3.

If we are not excellent at those, the strategy fails because:

Keep the list short. A long list means the advantage is vague or the strategy is actually multiple strategies.

5. Define management systems

Management systems make the strategy persistent. They decide what gets measured, funded, reviewed, escalated, rewarded, and learned.

At minimum, define:

• decision cadence,
• owner for each capability,
• leading indicators,
• lagging indicators,
• review ritual,
• resource-allocation rule,
• kill or pivot trigger.

If the cascade has no management systems, it is a workshop artifact, not an operating strategy.

Fit Checks

Run these checks before presenting the strategy as coherent.

Output Template

Use this compact shape for strategy work.

Playing to Win cascade

Winning aspiration:

Where to play:
- Customer/segment:
- Need/occasion:
- Product/category:
- Geography/channel/value-chain scope:
- Explicit no-go:

How to win:
- Advantage:
- Relevant alternative:
- Why the target chooses us:
- Evidence that this is working:

Must-have capabilities:
1.
2.
3.

Management systems:
- Metrics:
- Cadence:
- Decision rights:
- Resource allocation:
- Kill/pivot trigger:

Fit risks:
- Choice mismatch:
- Assumption to test:
- Capability gap:

Boundaries

Use Playing to Win when the task is to define or repair the strategy choice system.

Use another tool when the task is narrower:

Verification

Before finishing, verify:

• The answer contains all five choices.
• Where to play is narrow enough to exclude real alternatives.
• How to win names a mechanism of advantage, not just an adjective.
• Capabilities follow from the how-to-win choice.
• Management systems include owners, metrics, cadence, and decision rights.
• The choices reinforce each other.
• At least one no-go trade-off is explicit.
• Unverified assumptions are labeled as assumptions.
• The response does not present a plan, roadmap, OKR tree, or market analysis as a strategy cascade.

References

• references/playing-to-win-sources.md
• references/upstream-displacement-2026-05-26.md

Do NOT Use When

Use another skill when the task falls outside the declared scope, matches an anti_examples prompt, or is owned by a more specific related skill.