Playing to Win

Strategy Is Choice

Choosing something that could be wrong

A plan lists activities and dates. A budget allocates money. A mission statement declares intent. None of these require picking a side, which is exactly why organizations reach for them instead of a real strategy.

Strategy exists only where a company commits to a specific way of competing that forecloses other options, a choice specific enough that it could genuinely turn out wrong.

"Playing to win" versus "playing not to lose"

Most companies default to a posture worth naming: "playing not to lose." Targets rise a little above last year's, market share gets defended, and no bet gets made that could actually fail.

That posture feels safer, but it never forces anyone to say what the company will stop doing. "Playing to win" is the opposite instinct: committing to a specific aspiration and backing it with resources, accepting the bet might not pay off.

The five choices that have to move together

Every chapter in this book fills in one link of a single framework: the Strategic Choice Cascade. It treats strategy as five questions, answered together rather than in isolation.

• Winning aspiration: what winning actually means for this business, tied to customers and competitors.
• Where to play: the specific arenas, geography, category, segment, channel, value-chain stage, chosen to compete in, and just as deliberately, the ones skipped.
• How to win: the source of advantage, lower cost or real differentiation, chosen for that arena.
• Capabilities: the reinforcing set of activities the company has to be genuinely good at to win that way.
• Management systems: the processes, metrics, and incentives that keep the organization actually living out the first four choices.

Each level constrains the one beneath it. An aspiration vague enough to fit any market cannot narrow where to play; a where-to-play answer with no how-to-win attached just describes a market the company happens to sell into.

P&G's own turnaround, roughly doubling sales and quadrupling profits over a decade, is the case the rest of the book returns to as proof that running this chain deliberately changes outcomes, not just paperwork.

Where this bites in product work

A roadmap padded with safe, incremental line items is "playing not to lose" wearing a ticket-tracker label. The test worth applying to any roadmap slide is whether it states a choice that could fail, a specific segment bet, a specific way of winning against a named competitor.

If cutting any single line would not change what the team is betting on, the roadmap is not a strategy yet.

What Is Winning

What a winning aspiration actually has to do

The cascade's first link, the "winning aspiration," sets the frame for every choice under it. It fails the moment it could sit unedited on any company's website: "be a great place to work" or "delight every customer" does not say what winning in the market looks like.

The test: would it change a decision?

A useful check is whether the stated aspiration is compatible with literally every strategic option the company could pick. If it is, it is not doing strategic work, it is decoration.

A real winning aspiration has to be specific enough that some choices clearly fail it and others clearly serve it.

P&G's aspiration, and why the combination mattered

The book's anchor case is the aspiration Lafley set at P&G: touch and improve the lives of more consumers, in more parts of the world, more completely, paired with a hard financial marker, delivering total shareholder returns in the top third of the consumer-products industry.

The customer-facing half gave the company a purpose; the competitive half gave it a bar to measure against, so nobody could claim victory just because revenue grew.

That pairing matters because the two failure modes run in opposite directions. An aspiration that is purely financial, grow X percent, tells nobody why customers should choose the company over a rival.

An aspiration that is purely inspirational, change the world, never gets checked against a scoreboard, so it can survive years of mediocre results untouched. Combining a customer purpose with a measurable competitive standard closes both gaps at once.

The PM-learning moment: north-star metrics that do not disqualify anything

Product teams write north-star metrics the same way companies write mission statements, and the same test applies. A metric like "grow weekly active users" says nothing about which users, doing what, versus which competitor.

Before adopting one, check whether it would actually rule out a real initiative currently on the roadmap. If every current project passes the metric, the metric is not defining winning, it is just tracking activity.

Where to Play

"Where to play" is the choice of which specific arenas a company will compete in, and, with equal weight, which it will deliberately skip.

Five dimensions, chosen together

The book breaks the decision into five dimensions that combine into one answer: geography, product category, consumer or customer segment, distribution channel, and stage of the value chain.

Claiming "everywhere" across all five is not a where-to-play choice, it is the absence of one, because it spreads resources thin without building an edge anywhere specific.

Olay's repositioning, chosen field by field

The clearest illustration is Olay's turnaround from a declining, roughly eight-hundred-million-dollar mass-market skin cream into a multibillion-dollar growth brand. The where-to-play move was precise on every dimension.

The target consumer shifted from women over fifty to an "aspirational" thirty-five-to-fifty segment; the category moved from basic moisturizer to anti-aging skincare; the channel stayed mass retail, drugstores and big-box shelves, rather than jumping to department-store counters.

What made the arena work was a deliberate positioning gap: pricing and packaging borrowed the cues of prestige beauty brands while distribution stayed in the mass channel, a combination retailers call "masstige," mass plus prestige.

Olay competed for shoppers who wanted department-store-quality skincare without paying department-store prices, a segment the existing mass players and the existing prestige players were both leaving unclaimed.

Why narrowing is what creates the win

None of this required Olay to become a bigger brand overnight. It required giving something up: the older core customer got less marketing attention, and the low-price commodity positioning that had defined the brand for years was abandoned on purpose.

The where-to-play choice only did strategic work because it excluded options as clearly as it included one.

The PM-learning moment: naming who you are not building for

Product teams usually can describe their target user; far fewer can name, out loud, the adjacent segment they have decided not to serve this cycle.

Write that exclusion down explicitly, the enterprise tier you are not chasing yet, the geography you are not localizing for. A where-to-play choice that never says no to anyone has not actually chosen a playing field.

How to Win

Once an arena is chosen, "how to win" asks what makes this company the winner in it specifically.

Two durable paths, not a blend

Drawing on Michael Porter's competitive-strategy logic, the book argues there are only two durable answers: cost leadership, matching competitors' value at a meaningfully lower cost, or differentiation, delivering superior value that justifies a premium.

A company chasing "a little cheaper and a little better" than everyone else usually ends up neither.

Why the two paths cannot be run at once

The reason is not preference, it is structural. The internal activities that support low cost, standardization, scale, tight efficiency, actively undercut the activities that support differentiation, customization, premium experience, faster innovation cycles.

A single business unit built to excel at one path will, almost mechanically, be mediocre at the other if it tries to run both at the same time.

Olay's differentiation, priced to win

Olay's Total Effects launch shows the differentiation path in practice. Rather than competing on price against other mass-market moisturizers, P&G built the product around addressing seven specific, named signs of aging in a single formula.

That was an offer no mass competitor matched and few prestige competitors bundled as clearly. The premium price over ordinary moisturizer was justified by a specific, differentiated benefit, not by brand prestige alone.

That is what let the masstige positioning from the where-to-play choice actually convert into revenue.

The cost path, for contrast

A cost-leadership example looks structurally different: a private-label or value competitor wins the same shelf by matching baseline moisturizing performance at the lowest price the category will bear.

It strips out the extra formulation, packaging, and marketing spend a differentiated product carries. Both paths can win in the same category at the same time, because they are not actually fighting for the same customer.

The PM-learning moment: forcing the either/or into feature calls

Feature prioritization debates often hide an unresolved how-to-win choice. A pricing tier or feature set that tries to be the cheapest option and the most full-featured option at once usually satisfies neither buyer.

Before greenlighting a feature, ask which of the two paths it serves; a feature that only makes sense under "we are the premium option" should not ship alongside a pitch built on being the cheapest.

Play to Your Strengths

Capabilities are the activities a company must actually be excellent at to execute its chosen how-to-win.

Three tests for a real capability

The book insists capabilities only count if they pass three tests: they have to be feasible to build with resources the company can plausibly marshal, distinctive relative to competitors, and defensible once built, hard for a rival to copy quickly.

Generic strengths like "talented people" or "strong culture" fail all three, because they do not explain why this company can win this specific way and a rival cannot.

Capabilities as a reinforcing system, not a list

The book frames real capabilities as an activity system: individual strengths that reinforce each other so the whole becomes harder to copy than any single piece.

A competitor might replicate one capability in isolation, a research method, a distribution deal, but copying an entire interlocking system built around one how-to-win choice takes far longer, which is what makes a capabilities-based edge durable instead of temporary.

P&G's five, and how they connect to the choices above

For P&G, the recurring five are deep consumer understanding, methods for surfacing needs consumers cannot yet articulate themselves, a reliable innovation pipeline, brand-building skill, strong execution with retail partners, and global scale that lets a proven innovation roll out across markets quickly.

Each one exists specifically to support a differentiation-led how-to-win; none of them would matter much to a company that had chosen the cost-leadership path instead.

The quiet way strategies fail here

The chapter's real warning targets a common, invisible failure mode: a company picks a sound where-to-play and how-to-win, then never funds the capability gap that choice actually requires, defaulting instead to whatever the organization already happens to do well.

The strategy does not fail because the top-level choice was wrong; it fails because nothing underneath it changed.

The PM-learning moment: auditing capabilities against the choice, not the backlog

Run your team's actual capabilities, data infrastructure, support model, integrations, onboarding motion, against the feasible, distinctive, defensible test for your chosen how-to-win specifically, not against a generic "are we good at this" survey.

A capability gap that blocks the chosen way of winning belongs on the roadmap as a first-class item, not as tech debt to get to eventually.

Manage What Matters

Management systems are the cascade's last link: the planning cadence, performance metrics, resource-allocation routines, and people processes that keep an organization living out its strategic choices day to day, instead of leaving them stranded in a slide deck.

A company can nail the first four choices and still lose here, if its budgeting or incentives quietly reward something the chosen strategy does not need.

The generic-template trap

A frequent failure is a planning process that hands every business unit the same fill-in-the-blank template, producing documents that look like strategy but are really financial projections with a market slide attached.

The fix is not a better template; it is rebuilding the planning conversation around the cascade's actual questions, so a unit leader has to state a winning aspiration, a where-to-play, and a how-to-win in plain language rather than submit a spreadsheet.

Rebuilding the review at P&G

At P&G, this meant replacing a heavy, calendar-driven planning ritual with a leaner process organized explicitly around the five cascade questions.

Leaders had to defend the logic connecting their choices to peers in the room, not just present growth projections, and units that shared underlying capabilities were expected to reinforce each other.

Shared consumer-insight methods and shared retail relationships acted like structural rods holding multiple business units' strategies to the same standard.

What actually gets rewarded

Incentives, resource allocation, hiring, and promotion all have to visibly reinforce the same choices, or employees correctly conclude the stated strategy is not the real one and default to optimizing whatever comp and review criteria actually measure.

A strategy document that says "differentiation" while bonuses are still paid on unit cost reduction is telling the organization two contradictory things at once, and the metric usually wins.

The PM-learning moment: auditing what your team's systems actually reward

List the systems that shape your team's daily behavior, sprint review format, promotion criteria, the metric featured on the team dashboard, and check each against the product strategy you would claim to be running.

A team whose dashboard only tracks shipped-feature count will optimize for shipping, regardless of what the roadmap deck says about differentiation or focus.

Think Through Strategy

The Strategy Logic Flow

Before committing to a finished cascade, the book proposes stress-testing it with the "Strategy Logic Flow," a structured way of laying the five choices out as one connected, checkable argument rather than five bullet points that merely sound compatible.

Each choice becomes a claim that has to hold true for the choice below it to make sense, backed by actual evidence rather than confidence.

Four dimensions the logic has to survive

The flow forces analysis across four areas in sequence: industry structure, is this arena actually attractive, and for whom; customer value, what specific need is being met better than alternatives.

Relative position, does the company's chosen how-to-win genuinely beat the likely competitive set here; and competitive reaction, what happens to the plan once rivals respond, rather than stand still.

Applying it to a real bet

Run against a masstige repositioning like Olay's, the logic flow would ask, in order: is prestige-adjacent skincare actually growing enough to be worth entering; does the thirty-five-to-fifty segment genuinely value the seven-signs-of-aging benefit enough to pay a premium.

Can Total Effects actually out-perform both mass rivals and lower-tier prestige rivals on that specific benefit; and what happens once a prestige incumbent cuts price or a mass rival copies the formula.

A plan that cannot answer that last question has not actually been pressure-tested yet.

Spotting a plan pretending to be a strategy

Run through this framework, a document that lists initiatives, investments, and financial targets but never states an actual where-to-play or how-to-win choice underneath them reveals empty links, activities with no strategic claim actually supporting them.

The tool's real value is not building a strategy from a blank page; it is diagnosing whether one that already exists is a genuine set of choices or a list of plans dressed up to look like one.

The PM-learning moment: chaining your own roadmap's claims

Write your product strategy as four linked claims mirroring the flow: why this market is worth the team's time right now, what specific customer value the roadmap addresses, why your product wins that value fight against the named alternative, and what you would do if that competitor responded next quarter.

A roadmap that cannot answer the fourth claim is one good competitor move away from falling apart.

Shorten Your Odds

Even a logically consistent strategy can fail, because no amount of analysis eliminates real market uncertainty. The book's final tool addresses the moment a team has to choose between several plausible options with no way to be certain in advance which will work.

Instead of debating which option is "right," a debate that tends to collapse into people defending whichever answer they arrived in the room with, the method is "reverse engineering": work backward from each option to what would have to be true in the world for it to succeed.

Turning a hunch into a list of checkable claims

For each strategic possibility, the exercise lists the specific market, cost, capability, or competitor-response conditions that must hold.

Some of those conditions are already known and can be checked immediately; others are genuinely uncertain and can be tested cheaply, through a pilot, a small experiment, existing market research, or a look at how a competitor has behaved before.

This all happens without committing the full capital a company-wide launch requires.

"What would have to be true?"

The most useful single question the book offers is exactly that phrase. Asked of a strategic option, it reframes the conversation from advocacy, defending a favored answer, to inquiry, finding out together whether the answer holds.

Once the question in the room shifts from "is your idea good" to "what would have to be true, and how do we find out," the original advocate for an option gains as much stake in testing it honestly as any skeptic in the room does.

What the method does and does not promise

Reverse engineering shortens the odds on a bet, it does not eliminate uncertainty in a competitive market where rivals are also moving.

The realistic goal is narrowing a field of live options down to the ones whose required conditions are actually plausible, before spending the resources a full commitment demands, not guaranteeing any single option's success in advance.

The PM-learning moment: replacing roadmap debate with a testable list

Before a roadmap bet goes into a quarterly plan, write the three or four conditions that would have to be true for it to pay off, mark which ones are already known and which are genuinely uncertain, and design the cheapest possible test for the uncertain ones.

A team that runs this exercise together stops arguing over whose instinct is right and starts arguing over which test to run first.

The Endless Pursuit of Winning

A great strategy does not stay great once it is set. Markets shift, customer needs move, and competitors respond directly to whatever edge a company has built, which means every choice in the cascade carries a shelf life rather than a permanent expiration-free status.

Winning, in this book's terms, is a continuous discipline that has to be re-run, not a project with a finish line.

When yesterday's answer blocks tomorrow's

The closing warning points back at P&G's own history: capabilities and management systems built to support one generation's how-to-win choice can, left unexamined, become exactly the thing that blocks the next generation's strategy.

A retail relationship built for a mass-channel play can slow a company down when the next arena calls for direct-to-consumer distribution instead.

Treating the cascade as decided once and then merely defended, rather than periodically revisited, is how yesterday's winning strategy quietly becomes tomorrow's constraint.

The habit that actually matters

The book's last message is not a new tool, it is a habit: return to the same five questions on a real cadence as conditions change, rather than assuming this year's answers are permanent.

The organizations that keep winning are not the ones that got the cascade right once; they are the ones that never stopped asking it the same five questions again.

The Entire Book in One Framework

Every tool in the book, the Strategic Choice Cascade, the Strategy Logic Flow, and reverse engineering, exists to answer one repeated failure pattern: strategy usually breaks down not because a company picked the wrong answer, but because it never made a real choice at all.

The cascade forces the choice by naming five specific questions that have to be answered together. The Logic Flow tests whether those five answers actually connect as one argument instead of five independent guesses.

Reverse engineering tests whether the riskiest of those answers can survive contact with real evidence before the company commits the capital a full bet requires.

Read as one system rather than three separate chapters, the sequence is: choose with the cascade, check the choices connect with the Logic Flow, then check the riskiest choice against reality with reverse engineering before scaling it.

Strategy is not a plan or a wish list; it is a set of choices specific enough to be wrong, working together because they were chosen as one connected argument, not five separate exercises.

10 Most Important Takeaways

• Strategy is a set of specific choices that could turn out wrong, not a plan, a budget, or a mission statement.
• Play to win, not to avoid losing; a hedged aspiration produces a hedged, mediocre strategy.
• The Strategic Choice Cascade has five linked levels: winning aspiration, where to play, how to win, capabilities, management systems.
• A winning aspiration has to be specific enough to disqualify some strategic options, not vague enough to fit every one.
• Where to play means choosing specific geographies, categories, segments, channels, and value-chain stages, and just as deliberately choosing what to skip.
• There are only two durable ways to win an arena: cost leadership or differentiation; running both at once usually delivers neither.
• Capabilities only count as strategic when they are feasible, distinctive, and defensible, built as a reinforcing system for the chosen how-to-win.
• Management systems, planning, incentives, resource allocation, have to visibly reward the chosen strategy, or employees will optimize whatever is actually measured instead.
• The Strategy Logic Flow turns five choices into a testable chain across industry structure, customer value, relative position, and competitor reaction.
• Reverse engineering replaces "is this the right answer" debates with "what would have to be true," turning advocacy into a shared, testable inquiry.

The deepest habit in the book is not any single tool; it is treating strategy as a chain of choices worth revisiting, not a document worth defending once it is finally signed off.