Playing to Win

Strategy, in Playing to Win, is an integrated set of choices that positions an organization to win in a chosen arena. A.G. Lafley and Roger L. Martin argue that many organizations avoid strategy while believing they are doing it: they write mission statements, set financial targets, build annual plans, and approve long lists of initiatives. Those activities may be useful, but they do not answer the strategic question unless they specify where the organization will compete, how it will create a superior value equation there, and what must be built to sustain that advantage.

The book’s practical mechanism is the strategy choice cascade: winning aspiration, where to play, how to win, required capabilities, and management systems. The value of the cascade is not that it makes strategy easy. It makes avoidance visible. A strategy that does not rule anything out, expose any tradeoff, or depend on any contested belief about customers and competitors is probably a plan, a hope, or a portfolio of activity rather than a strategy.

Real strategy makes exclusion unavoidable

The first discipline in the book is choice. A statement that says an organization will grow, innovate, delight customers, improve efficiency, and pursue attractive opportunities may be agreeable to everyone, but that is often the problem. If it does not tell managers which customers not to chase, which markets not to enter, which capabilities not to fund, or which initiatives to stop, it cannot concentrate effort.

Lafley and Martin use “winning” to force that concentration, though the word is easy to misread. It does not mean winning at all costs or disregarding stakeholders. In this framework, winning means defining success competitively and serving chosen customers better than alternatives in a chosen arena. Without that standard, almost any beneficial activity can be called strategic. With it, every proposed action has to face a harder question: does this help us win where we have chosen to play?

This is also why the book distinguishes strategy from planning. Planning concerns activities and resources that managers can largely control. Strategy concerns an outcome that depends on customers, competitors, channels, costs, capabilities, and uncertainty. A plan can say what the organization will do next quarter. A strategy has to explain why those actions should produce advantage in a contested environment.

The book’s evidence base is practice-heavy rather than a controlled empirical proof. Lafley and Martin ground the framework in Procter & Gamble, including Lafley’s first tenure as CEO, during which the book reports that P&G doubled sales, quadrupled profits, and increased market value by more than $100 billion. Those results do not establish a universal law. They show the managerial setting the framework was designed for: a large organization with many brands, geographies, categories, channels, and possible investments needed a way to convert ambition into coherent choice.

Aspiration is useful only when it disciplines later choices

The first question, winning aspiration, asks what winning means. It is not decorative purpose language placed above the real strategy. It defines the objective function for the rest of the cascade. If leaders cannot say what counts as winning, they cannot judge whether a proposed customer segment, market boundary, price tier, channel, or capability is worth choosing.

A useful aspiration is therefore constraining. “Be the best” is too vague because it does not identify the game being played or the basis on which success will be judged. A purely financial target is also incomplete in this framework. It may state a desired result, but it does not explain whom the organization will serve, why those customers will choose it, or what advantage will produce the financial outcome. Financial performance matters, but it is not a substitute for the strategic logic that creates it.

The aspiration is not sacred wording fixed before all other decisions. Lafley and Martin’s cascade is often drawn from top to bottom, but the choices are interdependent. A team may begin with an aspiration and then discover that no credible where-to-play or how-to-win choice supports it. In that case, the aspiration should be revised. The cascade is a system of fit, not a lockstep form in which each box is completed once and protected from later evidence.

Where to play and how to win form the strategic core

The central pair of choices is where to play and how to win. Where to play defines the arena in which the organization will compete. That arena can be described by customer segments, product categories, geographies, channels, vertical stages, price tiers, or other relevant boundaries. The question is not where the organization could theoretically participate. It is where it will place its bets.

How to win explains why the organization can create superior value in that arena. The source of advantage may involve differentiation, cost position, brand, scale, channel control, customer insight, system design, or another coherent basis of superiority. But a broad answer such as “win through innovation” or “win through customer focus” is not enough. It becomes strategic only when attached to a specific field of play where that advantage matters and can be defended.

The two questions must be answered together because each changes the meaning of the other. An attractive market is not a strategy if the organization has no credible way to win there. A powerful capability is not a strategy if it is aimed at no particular arena. This is one of the book’s sharpest corrections to conventional planning: “What markets are growing?” and “What are we good at?” are incomplete questions when asked separately. The strategic question is whether a chosen arena and a chosen advantage reinforce each other.

The book uses P&G brand examples, including Olay, Bounty, Gillette, Swiffer, and Febreze, to show that the cascade applies below the corporate level. Strategy is not only a headquarters-level portfolio exercise. A brand, category, or product system also has to define its playing field and winning logic. The examples matter because they keep the framework close to customers, occasions, channels, and positioning rather than leaving it as an abstract corporate diagram.

Capabilities and systems make the choice real

The fourth and fifth questions prevent the cascade from stopping at attractive positioning. Required capabilities are the few organizational abilities that must exist for the chosen how-to-win to work. They are not a generic inventory of strengths or a long list of competencies. They are strategy-specific. If the way to win depends on brand building, consumer insight, retail execution, product innovation, cost structure, or some other ability, then those capabilities must be built and protected because the strategy fails without them.

This distinction is important because organizations often confuse existing strengths with required capabilities. A company may be proud of what it already does well, but the cascade asks a narrower question: what must this organization be able to do unusually well for this particular winning logic to be credible? Sometimes existing strengths support the strategy. Sometimes they are irrelevant. Sometimes the desired strategy reveals a capability gap so large that the proposed choice is unrealistic unless leaders are willing to invest.

Management systems are the routines, measures, incentives, decision processes, reviews, and structures that build and maintain those capabilities. Lafley and Martin treat them as part of strategy, not as post-strategy execution. That is a useful correction. If a company chooses a strategy requiring certain capabilities but funds projects through old priorities, measures managers against unrelated targets, and reviews performance through generic operating metrics, the declared strategy will not shape behavior for long.

The dependency is simple:

Winning aspiration → Where to play → How to win → Required capabilities → Management systems

The arrow should not be read as a rigid one-way sequence. It shows fit. The aspiration gives direction; the where-to-play and how-to-win choices define the theory of advantage; the capabilities make that theory possible; the systems make the capabilities durable. If a later element cannot support an earlier choice, the earlier choice has to be reconsidered.

Testing strategy means asking what would have to be true

The book’s most practical discipline is reverse engineering strategic options. Instead of asking a team to defend its favorite answer, the process asks what would have to be true for each possible strategy to be a good choice. That shift changes the character of the discussion. A disputed option becomes a hypothesis about customers, competitors, costs, channels, capabilities, or behavior rather than a referendum on the executive who proposed it.

The decision rule follows the book’s logic:

1. Frame the issue as a real choice among different strategic possibilities.
2. For each possibility, specify what would have to be true for it to succeed.
3. Identify the conditions that are most uncertain, important, or contested.
4. Test those conditions with the best available evidence.
5. Choose the strategy whose required conditions are most credible and worth committing to.

This is not a demand for perfect data. Lafley and Martin’s approach sits between two weak defaults: formal planning that creates the appearance of rigor by listing controllable activity, and undisciplined creativity that produces appealing ideas without testing the assumptions underneath them. Reverse engineering adds rigor without pretending that strategy can become a laboratory science. It makes the logic visible enough for disagreement to become productive.

The method also reduces the advocacy trap. In many strategy processes, executives argue for preferred plans and evidence becomes ammunition. In a “what would have to be true” discussion, the team can temporarily treat multiple options as plausible. The work is to discover which option depends on the most believable set of conditions. That does not remove politics or uncertainty, but it gives the group a better object of debate than confidence.

Planning earns its place after the strategic choice

Planning becomes powerful once the strategic choice is clear. Budgets can fund the required capabilities. Reviews can track whether the strategy is working. Incentives can support the behaviors the strategy needs. Operating plans can coordinate action across functions. But when planning comes first, the organization can optimize activity without ever deciding where it intends to win or why it deserves to win there.

The framework is strongest when the problem really involves competitive choice: which customers to serve, which arenas to enter or exit, which advantage to build, and which capabilities to privilege. It is weaker when treated as a universal template for every organizational question or as a mechanical form to complete. The cascade works because the answers fit together. Its practical demand is severe but clarifying: make the choices explicit, test the assumptions behind them, and align the organization so the chosen way to win can actually be built.