Tabletop Exercises and War Games: Rehearse Decisions Before They Count
How discussion-based tabletop exercises and adversarial war games let a team rehearse hard decisions, with practical steps drawn from NIST and UK military guidance.
Strategy Chaos · Last reviewed October 23, 2026 · 6 min read
Plans look tidy on paper. The gaps show up when real people have to make real decisions under pressure: who calls whom, what gets cut first, which assumption turns out to be wrong. Rehearsal exposes those gaps while mistakes are still cheap.
Two rehearsal formats are especially useful for strategy under uncertainty. A tabletop exercise walks a team through a hypothetical situation to check that a plan, and the roles in it, actually work. A war game goes further, putting your strategy up against thinking opponents and letting the consequences of each decision play out. This guide explains both, using the U.S. National Institute of Standards and Technology's guide to exercises (NIST SP 800-84) and the UK Ministry of Defence's Wargaming Handbook.
What a tabletop exercise is
NIST SP 800-84, published in 2006, was written for IT plans, but its description applies well beyond IT. It defines tabletop exercises as discussion-based events where people with roles in a plan meet in a classroom setting or in breakout groups to discuss their roles during an emergency and their responses to a particular situation. A facilitator guides the discussion toward predefined objectives, and the exercise does not involve deploying equipment or other resources.
According to NIST, a tabletop typically runs two to eight hours, depending on the audience, topic and objectives. It recommends that senior-level teams and operational-level teams exercise separately at first, because their responsibilities differ, and then together to check coordination between them. It puts senior-level sessions at two to four hours.
Designing a tabletop
NIST describes four phases: design, development, conduct and evaluation. In design, the team chooses the topic, scope, objectives, participants and staff. Planning typically starts at least one month ahead, or three months for large, complex exercises.
The staff is small. NIST suggests a facilitator who leads the discussion and a data collector who records what happens. Both should know the plan being exercised and the objectives well.
The materials are simple too:
- A briefing with the agenda and logistics.
- A facilitator guide with the purpose, scope, objectives, scenario, discussion questions and a copy of the plan.
- A participant guide with the same information but a shorter list of questions.
- An after action report, built against evaluation criteria written before the exercise.
On the scenario itself, NIST makes a point many teams learn the hard way: a common misconception is that scenarios must be very detailed. With long, detailed scenarios, participants often spend more time dissecting the story than working on the objectives. A short, concise scenario usually works better.
Running the session
NIST's guidance for the day itself is practical. Participants are usually not seated with their own teammates, to encourage independent thinking and exposure to other parts of the organization. The facilitator opens with introductions and the briefing, walks through the scenario, and starts the discussion with a prepared question designed to prompt a decision or coordination. If the conversation stalls, the facilitator adds questions from the guide until the objectives are met.
Immediately afterward comes a debrief, often called a hotwash. NIST suggests asking where participants felt they did well, where they need more training, and which parts of the plan should be updated. The data collector's notes and the debrief feed the after action report, and someone is then assigned to update the plan. That last step is the whole point: an exercise that changes nothing was only a meeting.
What a war game adds
A tabletop checks whether your plan and roles hold together. A war game tests whether your strategy survives an opponent who is trying to beat it.
The UK Ministry of Defence's Wargaming Handbook, published in 2017, describes wargaming as a decision-making technique that provides structured but "intellectually liberating safe-to-fail environments" to explore what works and what does not, typically at relatively low cost. It calls being adversarial perhaps the key characteristic of wargaming. Challenge comes from opposing players acting as active, thinking and adaptive competitors, from the game controllers, and from a red team that challenges assumptions.
The handbook draws a careful distinction here. A red cell is the group of players representing the opposing side. A red team is a separate group whose job is to subject an organization's plans, ideas and assumptions to rigorous analysis and challenge. Outcomes are decided by adjudication, usually by an objective person, and the handbook advises applying it with as light a touch as possible so that player decisions stay at the center.
It also describes several formats that translate to business use:
- Seminar games: open-ended, argument-based discussion among experts, who make decisions and then face the consequences.
- Matrix games: players argue for the success of a proposed action, others make counter-arguments, and a facilitator or umpire decides the outcome before the next round.
- Course of action wargames: a systematic way to test a plan and ask "what if" questions as it unfolds.
Know the limits
The Wargaming Handbook is frank about what games cannot do. Wargames are not predictive: they can show that something is plausible, not that it is probable, and a single run risks false lessons. Running multiple games with different scenarios, starting conditions or players allows more robust conclusions. Wargames are also qualitative, best used to raise questions and insights rather than produce a definitive answer, and they are only as good as the participants.
The handbook also warns that games must not be designed to reinforce preconceived answers. It illustrates the point with a business case it recounts: FMC Corporation commissioned a wargame to assess a potential merger, and the game repeatedly pointed to a different partner than the one its leader favored. According to the handbook, when he asked why no one had told him it was a bad idea, an employee answered, "Because it was your idea, boss." The lesson it draws is that games let people challenge their superiors in a risk-free setting, but only if leaders are open to the result.
A simple way to start
For example, imagine a hypothetical 25-person food manufacturer whose main packaging supplier could stop shipping without warning.
- Set two or three objectives, such as confirming who decides on alternative suppliers and how quickly customers are told.
- Write a one-paragraph scenario, plus two or three timed updates, such as "week two: the backup supplier cannot meet your volume."
- Invite the people who would actually make those calls, and name a facilitator and a note-taker.
- Run a 90-minute session, finish with a hotwash, and write a one-page after action report with named owners for each fix.
Once that feels routine, try a simple war game: assign two or three colleagues to play a competitor responding to your next big move, and let them argue their best counter-moves.
Key takeaways
- A tabletop exercise is a facilitated discussion that tests whether a plan and its roles work in a hypothetical situation.
- NIST describes tabletops as typically two to eight hours, with a facilitator, a data collector and a short, focused scenario.
- Always finish with a hotwash and an after action report, and assign owners to update the plan.
- War games add thinking opponents and consequences; keep adjudication light and separate the red team from the red cell.
- Neither format predicts the future; use them to surface questions, test assumptions and rehearse decisions.
Sources
Spotted something out of date? Let us know.