War gaming is a facilitated, multi-round simulation in which internal teams role-play as specific competitors to anticipate their likely moves, then stress-test the company's own strategic plan against those simulated reactions before any resources are committed. Instead of asking "what should we do," it asks "what will they do when we do it, and what do we do next": a sequence of moves and countermoves that surfaces how a market might actually respond rather than how a planning deck assumes it will. Teams are typically split into a Blue Team playing the client company and one or more Red Teams representing named, real competitors, sometimes with additional roles for regulators, customers, or new entrants.
The practice is a direct descendant of military wargaming. Its most-cited ancestor is the Prussian Kriegsspiel, formalized in the early 1800s, with the Prussian army adopting a physical game-board version around 1811, and the U.S. Naval War College began using wargaming for officer training in 1887. The business adaptation is generally described as emerging after World War II, with broader corporate uptake from the mid-1980s onward. There is no single canonical inventor of the business version; it is a borrowed concept with several parallel schools of practice, including a realistic competitor-role-play approach associated with Benjamin Gilad, who wrote a book on business war games, and a more formal game-theoretic variant associated with Niall Fraser.
Today it is a taught, recognized competitive-intelligence technique. The Academy of Competitive Intelligence teaches it as a named course module, and CI consultancies offer it as a standard deliverable. It is the step that turns collected competitor intelligence into tested strategy.
How a war game is structured
A business war game is a facilitated workshop run over several sequential rounds. Participants are divided into teams, each assigned a role: a Blue Team representing the sponsoring company and one or more Red Teams each playing a specific, named competitor. Larger games add teams for a regulator, a major customer segment, or a plausible new entrant, so the board reflects more than a single rivalry.
The defining mechanic is move and countermove. In each round a team commits to actions such as a price change, a launch, a partnership, or a market entry, and the facilitator resolves the consequences before the next round begins. Because each round's decisions cascade into the conditions of the following round, the exercise exposes second- and third-order effects that a one-shot analysis misses: the discount that triggers a competitor's retaliation, the entry that invites a regulatory response. The output is usually a stress-tested plan, a set of early-warning indicators to watch for, and clearer executive alignment on priorities.
Evidence-based role briefs, not guesswork
The quality of a war game depends almost entirely on the quality of the briefs each competitor team plays from. A Red Team told only to "act like the aggressive incumbent" will reproduce the sponsoring company's own biases about that rival. A Red Team handed the competitor's financials, published pricing and packaging, product roadmap signals, hiring patterns, and recent public statements will make choices grounded in how that competitor actually behaves and what it can afford to do.
This is where a war game consumes competitive intelligence directly. The role briefs are built from the same continuous signal feed that a competitor-tracking workflow produces: pricing-page changes, job postings that reveal where a rival is investing, press and launch announcements, and executive commentary. A team that monitors those sources on an ongoing basis can assemble evidence-based briefs quickly and refresh them between games, so the simulated competitor stays anchored to observed behavior rather than to a year-old assumption.
War gaming vs. scenario planning
The two are often confused because both explore the future before it arrives, but they work differently. Scenario planning develops several plausible external futures, such as shifts in technology, regulation, or demand, and examines a strategy against each in a largely static, non-sequential way. Its goal is shared understanding of the problem space and resilience across futures that are mostly outside any one player's control.
War gaming instead runs a dynamic, multi-round simulation where the future is produced by the players' own interacting decisions. The competitor is an active agent that responds to your move, and its response reshapes the next round. Put simply, scenario planning stress-tests a plan against conditions; war gaming stress-tests it against opponents. The two are complementary: scenarios can define the environment a war game is played within, and a war game can pressure-test how rivals would behave inside a given scenario.
War gaming vs. red teaming
Red teaming and war gaming overlap but are not the same. A red team plays a single adversary, or a composite of them, with a narrow purpose: to attack, critique, and expose the weaknesses in an organization's existing plan or assumptions. It is an adversarial-critique pass.
War gaming is broader and usually multi-phase. It typically fields several distinct competitor teams, sometimes with non-competitor roles, and runs the interaction across rounds rather than in a single challenge. Red teaming is frequently used as a component inside a larger war game: one Red Team is, in effect, red teaming the Blue Team's plan, but a full war game also models how multiple rivals interact with each other, not just how one adversary breaks your strategy. Separately, both are distinct from quantitative business-simulation software or formal game-theoretic modeling: those are computer-run projections that may inform a war game, but war gaming is fundamentally a live human role-play exercise.
Common mistakes and limitations
The most common failure is role briefs built on assumption rather than evidence, which turns the game into an echo of the home team's existing beliefs about a competitor. Anchoring each Red Team to real intelligence, things like financials, pricing moves, hiring signals, and public statements, is what separates a useful game from a confidence-building theater exercise.
Other pitfalls are structural. A war game is a snapshot of a moment's competitive dynamics, so its conclusions decay as the market moves and the briefs go stale. Facilitation matters: without a neutral facilitator resolving each round consistently, the loudest team or the most senior executive can steer outcomes. And the exercise is resource-intensive relative to a desk analysis, so it is best reserved for high-stakes decisions like a major launch, a pricing overhaul, or an entry into a contested market, where understanding the likely sequence of competitor reactions justifies the time. It reveals how rivals may respond, not a finished plan for how to win.