The Problem With Strategy Documents

Most strategy frameworks sit in slide decks and never get used. The Playing To Win Strategy Toolkit takes the Lafley-Martin choice cascade and turns it into something you can actually fill out instead of present at a retreat. It forces answers to five questions that most companies avoid because the answers are uncomfortable. The five questions are straightforward on paper: What is our winning aspiration? Where will we play? How will we win? What capabilities must we have? What management systems do we need? The toolkit provides worksheets for each one, plus a linking template that shows whether your choices actually connect.

I spent three years helping mid-market companies run this framework properly. The first version I built was just a set of Google Sheets. People hated it. It turned strategy into a homework assignment that got skipped. I reworked it into a single workbook with forced dependencies between sections so you can't fill out the "how to win" column without backing it with capability choices.

Playing To Win Strategy Toolkit

The core structure works like this. You start with the winning aspiration and write it as a single sentence that includes a time horizon. Not "be the best." Something like "become the dominant provider of X in Y market by Z date." If you can't write that, you don't have a strategy, you have a goal. Goals are fine. They're not strategy. From there you move to where you play. This means defining your customer segments, geographies, product categories, and channels. Most teams skip the "where we won't play" part. That's a mistake. The no-go list is where you find your actual constraints. I've seen strategy groups spend weeks debating where to expand before realizing they had already committed to three different customer segments that required completely incompatible operations.

How The Capability Section Actually Works

The "what capabilities must we have" section is where most toolkits fail. They list capabilities as bullet points. That doesn't tell you anything. You need to identify which capabilities are table stakes and which are true differentiators. Table stakes keep you in the game. Differentiators let you win. Mixing them up is the most common error I see. Here is a specific edge case I ran into. A client was using the toolkit for a SaaS company moving from SMB to enterprise. The winning aspiration was clear. The where-to-play was clear. But when we got to capabilities, the team listed "salesforce CRM" and "24/7 support" as differentiators. Those are table stakes for enterprise sales. The actual differentiator they needed to build was implementation methodology and executive-level account planning. We spent two hours stripping their capability list down to three real differentiators and three table stakes, and that exercise alone changed their entire go-to-market approach.

The toolkit template forces this distinction by requiring each capability to be tagged as differentiating or table-stakes, with evidence for the tag. Without that requirement, every team claims everything is a differentiator.

The Management Systems Trap

The fifth question is usually treated as an afterthought. It shouldn't be. Management systems are how you enforce the choices you made in the previous four sections. If your winning aspiration requires speed but your budget cycle is quarterly with monthly reviews, your system contradicts your strategy. The toolkit includes a systems mapping worksheet that overlays your existing KPIs, review rhythms, and incentive structures against each strategic choice. Misalignments show up immediately. I once watched a company try to pursue a cost-leadership strategy while their compensation system rewarded revenue growth. The toolkit exposed this in one afternoon. The conflict would have taken six months to discover organically through performance data.

Where This Toolkit Falls Apart

It does not work for companies in crisis mode. When you are losing money month over month, you don't have the bandwidth to fill out five interconnected worksheets. You need a triage framework, not a choice cascade. It also struggles with highly ambiguous markets where "where to play" is genuinely unknowable. In those cases, you need scenario planning alongside this toolkit, not instead of it. The biggest bottleneck is time. A proper run-through takes two to three weeks for a leadership team working part-time. If someone tries to compress it into a single offsite, it becomes theater. People fill in answers that sound good instead of answers that are true. The toolkit assumes you can afford the slowness.

What You Actually Get

A complete toolkit includes a lead worksheet, five choice-specific canvases, a capability gap analysis sheet, a systems alignment matrix, and a one-page strategy summary that forces everything onto a single slide. The summary page is the most important piece. If you cannot fit your strategy there, you do not have a strategy yet. You can build this yourself in a spreadsheet in about four hours. Commercial versions exist but add nothing substantial. The value is in the forcing function, not the formatting.