The Theory · Episode 1

War Gaming Your Product Roadmap: Plan Like You're Playing an Opponent

18 August 2026

Episode 1:

Welcome to The Theory, a companion to The Position — same mission, different lens. Where The Position covers the practice of competitive intelligence, The Theory covers the science underneath it: the game theory, strategy research, and decision frameworks that explain why competitor analysis works when it's done right. New edition every week, four days after The Position.

First up: why your roadmap planning process might be missing an opponent.

The Thesis

Most roadmap planning is single-player. A team maps customer requests, technical debt, and strategic bets, then sequences them against capacity. It's a good process — for a game with no other players.

But B2B SaaS is not single-player. Every roadmap decision you make is a move in a game where competitors get to respond. Military strategists have known this for over a century: you don't plan an operation by asking "what's optimal for us," you plan it by asking "what's optimal for us given what the other side does next." That discipline is called war gaming, and almost no product team does a version of it.

The Setup: What War Gaming Actually Is

War gaming isn't prediction. It's structured adversarial simulation — you build out how an intelligent opponent would respond to your move, then respond to that, several moves deep, before you commit.

Military and strategic planning uses this to pressure-test decisions before they're irreversible. The core discipline has three parts:

Red teaming — a designated group argues and plans from the competitor's perspective, not your own
Move-countermove sequencing — you don't just ask "what's our best move," you ask "what's our best move after their most damaging response"
Branch mapping — decisions are evaluated across multiple future branches, not a single expected outcome

Applied to a roadmap, this reframes the central planning question. Not "what should we build next" — but "what should we build next that still holds up after our two most credible competitors respond to it."

Where This Actually Bites in B2B SaaS

The undefended feature bet A team ships a flagship feature with no plan for what happens when a well-funded competitor fast-follows within a quarter. The feature was the whole strategy — there was no branch for "they copy it in 90 days," so there's no next move ready when it happens.
The roadmap that assumes a static market Sequencing decisions get made against last quarter's competitive landscape. By the time the feature ships, the competitor who prompted it has repositioned entirely, and the "response" lands as a non-sequitur.
The single-scenario budget Resourcing gets locked against one expected future (a specific competitor stays quiet, a specific segment stays uncontested), with no cheap contingency built in for the branch where that assumption breaks.

In every case, the miss isn't a bad roadmap decision in isolation — it's a roadmap decision made as if no one else in the market gets to move.

The ROI Logic: Why War Gaming Changes the Math

War gaming isn't about slowing roadmap decisions down with hypotheticals. It's about making the existing decision cheaper to defend and faster to adjust.

Cheaper mistakes. A roadmap bet that's been pressure-tested against a competitor's most damaging response gets its failure modes identified before the engineering hours are spent, not after.
Faster second moves. Teams that branch-mapped a decision in advance already know what their move is when a competitor responds — no scramble, no reactive sprint.
Better resourcing calls. Structural intelligence — not just "what did they ship last week" but "what does their funding, hiring, and positioning suggest they can credibly do next" — is what makes branch mapping realistic instead of guesswork. This is the same move-level vs. structural distinction The Position covered in Episode 9: reacting to moves is copying; planning against structure is strategy.

Framework to Steal: The Three-Move Roadmap Check

Before committing a roadmap item to the next planning cycle, run it through three moves:

Move 1 — Your move What are we building, and what does it signal to the market?

Move 2 — Their most credible response Given our two closest competitors' actual capability and positioning (not worst-case fantasy), what's the response they're most likely and able to make?

Move 3 — Our answer to that response Do we already have a next move ready if they make it — or are we planning to figure that out later?

If you can't answer Move 3 before you commit to Move 1, the roadmap item isn't fully planned — it's a bet with no contingency. That's not a reason to cut it. It's a reason to build the contingency now, while it's cheap, instead of during a reactive scramble later.

The Prisoner's Dilemma You're Already Losing

First published as an edition of The Theory, Pro-Position.AI's newsletter on competitive intelligence, product strategy and go-to-market.

Keep exploring: