Playing to Win: five linked choices, and where most teams lose them

Playing to Win is not a plan. It is five choices that stand or fall together. The hard part is not making them at an offsite. The hard part is keeping them connected all the way from the boardroom to the portfolio that has to deliver on them.

Roger Martin and A.G. Lafley set the frame in their book Playing to Win. The point is simple and slightly uncomfortable: a strategy is not a list of initiatives. It is a set of linked choices about where you compete and how you win there. If the choices do not connect, you do not have a strategy. You have an ambition with good formatting.

Here are the five choices, what they mean, and the test each one has to pass.

The five choices

| # | Choice | The question | The test | |---|--------|--------------|----------| | 1 | Winning aspiration | What does winning look like for us? | A concrete picture of success, not a mission and not a vision | | 2 | Where to play | Where do we compete, and where do we not? | You can point to something you deliberately ruled out | | 3 | How to win | How do we create value no one else does in those arenas? | Either lower cost or real differentiation, not "quality and focus" | | 4 | Capabilities | What must we be better at than anyone else? | The capabilities exist, or there is a concrete plan to build them | | 5 | Management systems | What supports the four choices day to day? | Budget, targets and ownership follow the choices |

The cascade is read top down. It is tested bottom up. A fine winning aspiration means nothing if there are no capabilities and systems behind it.

Where most teams lose the cascade

Most leadership teams make the first two choices and stop. Winning aspiration and where to play can be written in an afternoon, and they feel strategic. How to win quickly turns into a hygiene sentence. Capabilities get handed to HR. Management systems get handed to finance. And in that same move the cascade breaks, because the three choices that make the strategy true have been passed downward as operations.

This is not a thinking problem. It is a connection problem. The choices exist, but they exist separately. The ambition lives in a strategy slide. Capabilities live in a competence wheel. The applications and technologies live in a spreadsheet in IT. No one can see the whole chain at once, so no one can see where it breaks.

That is exactly the point where a strategy stops being a strategy and becomes a collection of good intentions that do not point the same way.

A cascade is only real when you can trace it

The test of a Playing to Win cascade is not whether it sounds good. It is whether each choice can be traced down to something concrete.

A how to win rests on capabilities. A capability rests on applications, technologies and the people who own them. A where to play trade-off has to show up in where the money and attention actually go. If you cannot draw the line from the top choice down to the application that supports it, you do not know whether the strategy is true. You are hoping it is.

That line is the whole difference. A strategy you can trace is a strategy you can steer. One you cannot trace becomes an annual exercise everyone has forgotten by March.

How we see it at Spekir

Atlas is built on that connection. The Strategy module in Atlas is a Playing to Win cascade: themes, objectives and initiatives that hang together top down. But it does not stop at the strategy layer. Each choice can be linked to the capabilities it requires, and each capability to the applications and technologies that actually carry it.

That means you can see the whole chain in one view, from the boardroom ambition to the portfolio that has to deliver on it. And when something does not connect, an objective with no capability behind it, a capability with no owner, an initiative that points at nothing you chose, Atlas catches it and says so. We call it alignment. It is just another word for keeping the cascade honest.

This is not a new framework on top of Playing to Win. It is Playing to Win, turned into something you can see and steer by, not only something you write down once a year.

A short honesty check

Take it to your next leadership meeting. Each question should be answerable with yes and proof, or with no.

• Can you state the five choices on one page, without how to win turning into "quality and customer focus"?
• Can you name something you deliberately ruled out in where to play, and held the line on when a customer outside that choice called?
• Does each how to win rest on a capability you can point to, and that someone owns?
• Can you follow the line from your most important strategic choice down to the application or technology that supports it?
• Can the strategy be read in where the budget and attention move this year?

If you answer no to one of them, that is not a weakness in the strategy. It is the place where the cascade is not connected yet. And that is something you can fix.

So what

Playing to Win is still the sharpest test a leadership team can put its own thinking through, because it forces you to rule something out. But the test is not passed when the choices are made. It is passed when the choices can be seen all the way down into the portfolio, and when it is immediately visible if one of them has nothing behind it.

That is the part most tools do not help with. Strategy lives in one place, architecture in another, and the gap between them is where the value disappears. Closing that gap is the whole idea behind Spekir.

Frequently asked questions

What is Playing to Win? A strategy framework by Roger Martin and A.G. Lafley. It defines strategy as five linked choices: winning aspiration, where to play, how to win, capabilities and management systems. The point is that the choices have to connect, otherwise it is not a strategy.

Is Playing to Win only for large companies? No. It often works better in the midmarket, because there are no resources to mask a weak strategy with sheer execution. The discipline of ruling things out frees up both focus and capital.

How does it relate to architecture? Every strategic choice requires capabilities, and capabilities rest on applications and technologies. When you connect the two layers, you can see whether the strategy can actually be delivered by the portfolio you have. That is what Atlas does.

Playing to Win was developed by Roger L. Martin and A.G. Lafley. Spekir is not affiliated with the authors, we use the framework as a way to read strategy inside Atlas.