Building a Disruption War Game Your Board Will Actually Use

Most disruption war games sit in a shared drive, untouched after the first workshop.

The reason isn't complexity or cost. It's that most organizations build them backwards. They start with scenarios—the sexy part, the part that feels strategic. They layer in competitor moves, market shifts, technology shocks. They produce a beautiful artifact: a 40-slide deck, color-coded matrices, contingency trees that branch into the unknowable. Then they present it to the board. Then it dies.

The board doesn't use it because it wasn't built for the board's actual decision-making rhythm. It was built for the planning cycle. It was built to look complete. It wasn't built to answer the specific question that keeps your CFO awake at night, or the one your Chief Commercial Officer needs answered before the next budget cycle, or the one your CEO needs to defend to shareholders.

A war game that works is built around a decision, not a scenario.

This distinction matters more than most strategy teams realize, because it changes what you're actually building. You're not creating a comprehensive model of the future. You're creating a tool that forces clarity on what you'd do if X happened, and why. You're creating a shared language for disagreement. You're creating permission to talk about the unthinkable before it becomes inevitable.

The teams that get this right start differently. They ask: What decision will this board need to make in the next 18 months that we're not confident about? Not "what could disrupt us"—that's too broad. What specific move, investment, or pivot are we uncertain about? What would change our answer?

Then they build backwards. They identify the two or three scenarios that would genuinely flip your strategy. Not ten scenarios. Not a matrix of 16 possibilities. Two or three that matter. One where a competitor enters your core market with a different unit economics model. One where your customer's buying behavior shifts faster than your sales model can adapt. One where a regulatory change makes your current approach unviable.

Then—and this is where most teams fail—they don't build the scenarios in isolation. They build them as decision trees. What would you need to know to decide between Option A and Option B? What leading indicators would tell you which scenario is unfolding? What's your trigger for action? What's the cost of waiting versus the cost of moving too early?

This is where the war game becomes a living tool. Because now it's not a thought exercise. It's a monitoring system. It's a decision framework. It's something your Chief Strategy Officer can reference in a board meeting and say: "We identified this scenario six months ago. Here are the three signals we said we'd watch. Two of them are now present. Here's what we recommend."

The board uses it because it's not asking them to imagine the future. It's asking them to decide what they'd do if the future they already identified actually arrived.

The custom category playbook works the same way. You're not documenting every possible move in your market. You're documenting the moves that would force a decision. You're mapping the sequence of events that would require your organization to choose: Do we defend, or do we transform? Do we compete on the old terms, or do we accept that the category itself is being redefined?

The teams that build these well don't treat them as strategy documents. They treat them as decision infrastructure. They update them quarterly. They reference them in budget meetings. They use them to explain to the board why certain investments matter now, even if the threat feels distant.

That's the difference between a war game that sits in a folder and one that actually shapes how your organization thinks.