Strategy framework
A strategy is a chain of choices, not a list of goals.
"Grow revenue," "delight customers," "become the market leader" — none of these is a strategy, because none of them constrains anything. A strategy framework is what turns ambition into a set of linked choices, where each one narrows what the next one can be. Break the chain and the ambition stays, but the strategy doesn't.
The chain
Five choices, each constraining the next
Most documents called a "strategy" are really a set of independent decisions bundled under one heading: a goal here, a market here, an initiative there, none of them required by the others. That's the tell. A real strategy framework forces the choices into a chain, where an earlier link rules out most of what the later ones could otherwise be.
The five links below are the shape most strategy work eventually takes, in one form or another. What matters isn't memorizing the five names — it's the constraint running through them, top to bottom.
Winning aspiration
What winning actually means, stated specifically enough to be wrong about. Not "be the best," but a definition concrete enough that someone could look at the business in three years and say clearly whether it happened.
Everything below has to serve this definition, not a vaguer one nobody wrote down.
Where to play
Which markets, customer segments, channels, and geographies to actually compete in — and just as important, which to deliberately not. "Everyone, everywhere" isn't a where-to-play choice; it's what a where-to-play choice looks like when nobody made it.
This rules out most possible sources of advantage before the next link is even considered.
How to win
The specific source of advantage in the arena just chosen — lowest cost, superior service, a proprietary capability, a purpose-built fit for an underserved need. It has to be a real answer to "why us, in this arena, instead of them," not a value that sounds good on any slide.
A how-to-win chosen without reference to where-to-play is the single most common break in this chain.
Capabilities
What the organization must be able to do exceptionally well for that source of advantage to actually hold up — a specific skill, asset, process, or relationship. Not a wish list of nice-to-haves; the small set of things that, if missing, quietly falsify the how-to-win.
If the how-to-win requires a capability the organization doesn't have and isn't building, the chain is already broken here.
Management systems
The measures, incentives, and processes that sustain those capabilities once the excitement of launch wears off. A capability that depends entirely on one person's judgment, with nothing reinforcing it structurally, tends to erode the moment that person moves to something else.
This is what makes the previous four links durable instead of a one-time decision.
Signature tool
Does the pairing actually hold?
Pick a where-to-play arena, then pick a how-to-win. The framework's whole argument is that these two choices aren't independent — some pairings reinforce each other, and some quietly fight.
Getting it wrong
Where the chain most often breaks
"Everyone" as where to play
A where-to-play choice that includes every segment isn't a choice — it's a decision to make one later, usually under pressure, without the framing this stage was meant to provide.
How to win picked before where to play
A source of advantage decided in the abstract, then a market found to fit it, tends to produce an advantage that's real nowhere in particular.
Capabilities assumed rather than checked
Listing capabilities the how-to-win requires is different from confirming the organization actually has them, or has a credible plan to build them.
Incentives that reward something else
A management system still measuring last strategy's numbers will quietly pull capability investment back toward what it used to reward.
Questions
Common questions
What makes something a strategy framework rather than a goals list?
A goals list states what you want. A strategy framework forces a linked set of choices about how you'll get it, where each choice constrains the ones that follow. A list of ambitions with no constraining choices behind it isn't a strategy, however inspiring it reads.
Why does where to play constrain how to win?
Different arenas reward different kinds of advantage. What wins in a price-sensitive mass market — lowest cost to serve — is often the opposite of what wins in a premium segment, where depth of service usually matters more. Choosing a market and a source of advantage independently is how a how-to-win ends up fighting its own where-to-play.
Why is choosing where NOT to play part of the framework?
Because resources and attention are finite, and an advantage strong enough to matter in one arena rarely stays strong enough to matter in every arena at once. A where-to-play choice that includes everyone is a decision not to choose, and it usually shows up later as a how-to-win vague enough to apply anywhere — which functionally means it applies nowhere.
What's the difference between capabilities and management systems here?
Capabilities are what the organization must do well for the how-to-win to hold — a specific skill, asset, or process. Management systems are what sustains those capabilities over time: the metrics tracked, the incentives set, the processes reinforced. A capability with no system sustaining it tends to erode once the person who built it moves on.