Competitive War Gaming for Manufacturers
Competitive analysis tells you what your competitor has done. War gaming tells you what they will do — and rehearses your response before you need it.
Why War Gaming Beats Static Analysis
Analysis describes the past; rehearsal prepares the future.
♟️ Memos describe; games decide
A static analysis answers 'what is the competitor doing?' A war game answers 'what happens next, and what do we do about it?' The difference is commitment: analysis produces a document, war gaming produces pre-committed responses — decisions made in calm that the team can execute under pressure. In manufacturing, where competitive responses involve pricing, capacity, and contracts that take months to reverse, the pre-committed response is worth more than the most elegant competitive memo.
🎭 The empathy engine
Most competitive analysis is secretly self-analysis: we model the competitor's next move as what we would do in their position. War gaming breaks this by forcing the room to actually play the competitor — its economics, its capacity constraints, its announced strategy, its risk tolerance. Teams are routinely wrong about competitors they study every week, because reading about a competitor is not the same as thinking as them. The game surfaces the assumptions the analysis never questioned.
⚡ Blind spots are cheaper in a room
The most expensive discovery in competition is the one made after the fact: the move we did not see coming, the countermove we had not considered. War gaming manufactures those discoveries safely, in a day, at the cost of a meeting room. When Competitor A's table plays a pricing move your team never modeled, you have found a blind spot before the market finds it for you. That is the entire value proposition of rehearsal.
The One-Day Format
Four teams, three rounds, one decision — a format that fits a day and forces specificity.
🏛️ The four tables
Table one is You: your real position, cost base, capacity, and constraints — no wishful capabilities. Table two is Competitor A: built from your CI file — their announced strategy, their constraints, their apparent risk profile. Table three is Competitor B: the second rival, or in a two-player market, the new entrant or substitute that keeps the game honest. Table four is Market + Suppliers: demand, pricing pressure, regulatory moves, and supplier capacity — the environment neither company controls but both must answer to.
🔁 Three rounds of move and countermove
Round one opens the scenario: the decision is announced — a contract tender, a market entry, a price change — and each table makes its opening move. Round two is the countermove: how each player responds to the others, based on the CI signals already on the table. Round three is the resolution: the sequence of moves reaches a point where You must commit. Each round runs to a deadline, and every move must be stated as a concrete action with a timeline — 'we cut price on SKU line X by week four,' not 'we respond aggressively.'
🎯 Anchor on a real decision
The scenario is not a hypothetical; it is the actual decision in front of the business — bid the contract or not, enter the market or not, change the price book or not. An anchored game ends in a decision brief the leadership can act on Monday; an abstract game ends in a fun afternoon with no consequences. The anchor is also what makes the CI requirement workable: the room can only plan against what the competitors' signals actually support, so the game tests both the decision and the intelligence behind it.
Running the Game
Signals as moves, debrief as output, decision brief as deliverable.
📡 Every move must cite a signal
The one rule that keeps the game honest: no move without a CI source. If Competitor A's table wants to launch a product, they cite the hiring pattern, supplier approval, or patent filing that supports it; if they cannot, the move is cut. The rule does double duty — it forces the teams to work from the evidence file, and it exposes which competitors you actually have signal coverage on. The gaps the game reveals are a CI audit in themselves.
🕳️ The debrief is the deliverable, not the score
After the third round, run the debrief: what did each table believe, where were they surprised, which signals proved decisive, and which assumptions collapsed. The blind-spot list is the output — the moves nobody saw coming, the responses nobody had prepared, the market forces nobody had priced. Assign each blind spot an owner and a monitoring action. War gaming that skips the debrief is just an expensive meeting; the debrief is where the game becomes intelligence.
📋 Turn output into decisions
Within a week, the game must produce three artifacts: the decision brief on the anchored question (recommendation, rationale, and triggers for review), the pre-committed response matrix (if the competitor does X, we do Y, owned and dated), and the updated monitoring plan from the blind-spot list. The response matrix is the artifact that separates war gaming from analysis — it is not knowledge, it is readiness. Without these three, the day was theater; with them, it was rehearsal.