How to Run a Competitive War Game That Actually Predicts Something

A competitive war game is the only exercise that forces your team to think like the other guy. You sit in a room, hand someone the competitor's playbook, and make them attack you. Most teams skip it because it sounds like a consulting circus — flip charts, role play, a facilitator who says "let's unpack that." It doesn't have to be any of that. A properly run war game is a half-day simulation that surfaces your blind spots faster than six months of passive monitoring ever will.

The reason is simple. Monitoring tells you what a competitor has done. A war game tells you what they're likely to do next, and more importantly, what you'd be defenseless against if they did it. Those are different questions, and the second one is worth far more.

Why Your Team Will Resist, and Why You Should Ignore Them

Every war game hits the same wall: senior people don't want to pretend to be the enemy. They spent years building the product and they'd rather defend it than attack it. The VP of Sales will spend the whole exercise explaining why your current messaging is fine and the competitor's is doomed. That's not a war game; that's a pep rally.

The fix is to force the role. If you're running the exercise, you don't ask for volunteers to "play the competitor" — you assign the smartest, most cynical person in the room to the red team, and you give them permission to win. The competitor team's job is to put you out of business, and if they do it well, the whole room learns something. If they do it badly, you've just discovered you can't articulate your competitor's strategy, which is its own finding.

This is the same instinct behind designing a CI function that actually works — the value comes from structuring the exercise so the truth has nowhere to hide, not from hoping people volunteer for uncomfortable jobs.

What You Need Before You Start

A war game runs on three inputs. Skip any of them and you're doing improv with a whiteboard.

1. A concrete scenario

Don't war-game "the market." War-game a specific, dated decision. Good scenarios sound like this:

• "Competitor X drops their mid-tier price 30% next quarter. What do we do?"
• "Competitor X launches a feature that closes our biggest gap. Do we match, reposition, or acquire?"
• "Competitor X lands in our top segment with a hostile migration offer. How do we keep the install base?"

The scenario has to be plausible and uncomfortable. If it doesn't make someone in the room wince, it's too safe. Pick the move you secretly dread.

2. A facts sheet everyone agrees on

Before anyone role-plays, you need a shared, boring list of what you actually know: pricing, product gaps, install base, funding, and any signals you've picked up from hiring patterns, review trends, and changelog velocity. This keeps the simulation grounded. The moment someone invents a fact mid-exercise — "well, their engineering is a mess" — you stop and ask for evidence. War games die when teams start fighting over the map instead of the battle.

3. A real decision on the table

The output of a war game is a decision, not a deck. If leadership isn't willing to commit to at least one action item at the end, you're running a team-building exercise with more homework. State up front what's at stake: pricing, roadmap, hiring, a specific segment. Everything else is scenery.

The Four Roles

You need four roles, and every one of them is mandatory. The temptation is to collapse the customer role into "and then the customer prefers us" — resist it.

• The home team. Your actual leadership, playing themselves, making the real decisions with the real constraints.
• The competitor team (red team). One to three people assigned to play the specific rival, briefed on their actual product, pricing, and incentives — not your caricature of them.
• The customer. One person playing the buyer in the scenario. Their job is to be ruthlessly self-interested and a little unpredictable, because real buyers are both.
• The controller/facilitator. Runs the clock, enforces facts, and keeps score. They don't play; they referee.

The red team is the make-or-break role. Most war games fail because the competitor team is staffed with junior people who don't know the product well enough to attack credibly, or senior people who sandbag because they don't want to make leadership look bad. Put your sharpest operator there and tell them losing is a success condition.

Running It: Three Rounds, Ninety Minutes

You don't need a full day. Three timed rounds, ninety minutes total, keeps the energy up and stops people from negotiating themselves in circles.

Round 1 — The Red Team Moves (15 minutes)

The competitor team presents the scenario as their opening move: what they're doing, why it makes sense for them, and what they're trying to force you into. The rule is they have to argue the move from the competitor's incentives, not from yours. "We're dropping price because we're losing deals on price and our CAC is climbing" is a legitimate move. "We're dropping price to annoy you" is not.

Round 2 — The Home Team Responds (30 minutes)

Your leadership responds under a timer. The customer role is in the room here and gets to interrupt: "I don't care about your roadmap, I care about my renewal in March." This is where the exercise earns its keep, because most teams discover their "obvious" counter-move is anything but. A competitor who drops price 30% can't be answered with "we're premium, they're cheap" when the customer in the room shrugs and says the product is good enough.

Round 3 — The Counter and the Debrief (45 minutes)

The red team counters the home team's response, the customer picks a winner, and then everyone drops character and argues about what actually happened. The debrief is where the real intelligence gets extracted: what did the red team know that leadership didn't, and what did the home team assume that turned out to be false?

A war game doesn't predict the future. It stress-tests the assumptions you didn't know you were carrying.

The Moves the Red Team Always Makes

If you run a few of these, you'll notice the competitor team keeps reaching for the same handful of moves. That's not a coincidence — they're the moves you're structurally vulnerable to. Write them down and treat the list as a pre-mortem for your strategy.

• The price cut into your fat margin. If the red team can find a tier where you're overcharging, they will. This is why tracking competitor pricing as a weekly signal matters more than any single scrape.
• The feature that closes your gap. The red team will build exactly the one thing you've been telling yourself they can't ship. If it lands hard, you've been underestimating their roadmap.
• The hostile migration offer. Free onboarding, white-glove data transfer, a year of credits. The red team will buy your install base out from under you if your switching costs are lower than your NPS says they are.
• The narrative flip. They reframe the category so your differentiator becomes table stakes. Hard to defend against because it's a marketing move, and engineers don't believe marketing can beat them. It can.

Notice what these have in common: they're all aimed at where you're comfortable, not where you're already worried. That's the point of the exercise. The threats you already know about are the ones you've been quietly managing. The war game is for the ones you've been dismissing.

What Comes Out the Other Side

A war game is only worth the afternoon if it ends in commitments. Before you break, the controller writes down three things on the wall:

1. Three vulnerabilities the red team exploited that you didn't have a good answer for.
2. One assumption the home team made that the facts sheet contradicted.
3. Two actions — one you'll take this month, one you'll take this quarter, each with an owner and a date.

If you end the session without a single owner and a single date, you ran a debate, not a war game. The metrics that matter here aren't the number of slides produced — they're whether the decisions you made in the room actually changed anything about pricing, roadmap, or hiring in the following quarter.

How to Keep It Cheap and Repeatable

War games have a reputation as an annual offsite with a five-figure facilitator. It doesn't need to be that. Here's the version that costs you a conference room and one afternoon:

• Quarterly, not annually. The value is in the cadence. A war game every quarter keeps the red team sharp and catches strategy drift before it hardens into a bad quarter.
• Rotate the red team. Different people attack from different angles. Your best engineer will find the product vulnerability; your best AE will find the sales objection; your best PM will find the positioning gap.
• Feed it with real monitoring. The more current your facts sheet, the sharper the simulation. If your input is six months of stale screenshots, the red team will just be guessing. This is exactly where an automated competitive intelligence program pays for itself — the monitoring runs continuously, and the war game is where a human finally makes sense of it.

You don't need a dedicated CI team to run one of these. You need one person willing to be the controller, one cynical operator willing to be the enemy, and a leadership team willing to lose an argument in front of each other. That last part is the hard one, and it's the whole reason the exercise works.

The Real Deliverable Isn't the Answer — It's the Muscle

The first war game you run will be clumsy. People will break character, the customer role will get awkward, and someone will spend ten minutes arguing about a margin number. Run it anyway. The point isn't to produce a flawless simulation; it's to train your team to think from the other side of the table as a reflex, not a quarterly chore.

That reflex is what separates teams that get surprised from teams that saw it coming. Monitoring gives you the data. Presenting to executives gets you the buy-in. But a war game is the thing that turns all of it into a decision you're actually willing to defend. The competitor in your head is always dumber than the one in the market. Spend an afternoon a quarter making sure you're not the dumber one.

And if you want the facts sheet to write itself, that's what we do — the weekly monitoring runs in the background, and your war game starts from a live picture instead of a stale one.