The Decoy Briefing: Designing Wargames That Test Whether Players Actually Read the Intelligence

Most wargame designers spend serious time crafting intelligence packets. Order-of-battle estimates, diplomatic cables, intercepted communications, satellite imagery summaries. Hours of work. Then players glance at the folder, confirm what they already believed, and execute the plan they had before the game started.

Photo by Matias Luge on Pexels.

This is not a player failure. This is a design failure.

If your intelligence materials can be ignored without penalty, they will be ignored. The question worth asking before you run your next exercise: how would you even know?

The Problem Has a Name

In decision research, this pattern goes by several labels. Confirmation bias is the obvious one. But the sharper framing for wargame designers is "plan continuation bias": the tendency to keep executing a committed course of action even when new information should trigger a reassessment. Aviation accident investigators have documented it extensively. Military historians find it everywhere, from Gallipoli planning to the intelligence failures preceding Operation Market Garden in September 1944.

Standard wargame design does almost nothing to stress-test this bias. Players receive information. Players act. Facilitators assume the information was absorbed. That assumption is usually wrong, and nobody checks.

What a Decoy Briefing Actually Does

A decoy briefing is an intelligence packet deliberately seeded with signal traps: pieces of information that should visibly alter player decisions if absorbed, but that confirm prior assumptions if ignored.

The design goal is not to trick players. The goal is to make information consumption legible. You want a measurable gap between "players received this" and "players acted on this."

Here is a concrete example. Your scenario involves a coalition stabilization operation. Standard assumptions in the player community hold that the host-nation government is a reliable partner. Your decoy briefing includes three items buried across different appendices: a field report noting the interior minister has been meeting with opposition factions, a financial intelligence summary showing irregular transfers to a provincial militia, and a human intelligence report (marked low confidence) describing a parallel command structure operating outside official channels.

None of these items scream "betrayal." Each is individually deniable. Together, they point at a fragile partner relationship that should reshape how players sequence their operations.

If players treat the host-nation government as fully reliable anyway, you have learned something real about how your organization processes ambiguous warning signals.

graph TD
    A[/Intelligence Packet/] --> B{Player absorbs signal?}
    B -->|Yes| C[Decision reflects updated model]
    B -->|No| D[Decision reflects prior belief]
    C --> E((Record: signal processed))
    D --> F((Record: signal ignored))
    E --> G[Post-game: trace why it landed]
    F --> G

Building the Trap

Three design principles make decoy briefings work.

Distribute, don't highlight. Information that should change decisions must be spread across the packet, not flagged with bold text or a red border. Real intelligence rarely arrives pre-emphasized. If your signal is too obvious, you are testing reading speed, not analytical judgment.

Make inaction the confirming case. Design the scenario so that ignoring the signal produces a plausible outcome for several moves, then a costly one. Players who missed the signal should feel the consequence in game terms, not in a facilitator lecture after the fact. The game itself has to punish the skip.

Build a move log that captures intent. Before each major decision, ask players to record in one or two sentences what intelligence they are acting on and what they are discounting. This is not a quiz. Frame it as standard operational planning hygiene. The log becomes your evidence base during the debrief. You can now trace exactly when the divergence between available information and acted-upon information occurred.

What the Debrief Reveals

When you run this properly, the debrief stops being a narrative reconstruction and becomes a forensic exercise. You are not asking "what happened?" You are showing players the gap between what they had and what they used.

That gap, when made visible, is usually uncomfortable. Players who are certain they read everything carefully discover they filtered aggressively. Senior players often filter more than junior ones, because they have stronger prior models to defend.

This is the data your organization actually needs. Not "did we win the scenario," but "at what point did our analytical process stop updating?"

Speculation: organizations that run decoy briefings repeatedly over eighteen months or more would likely see measurable changes in how players annotate and cross-reference intelligence materials. The game behavior transfers to real planning cycles. That claim has not been formally studied at scale, but the behavioral logic is sound, and it is worth designing toward.

Build the trap. Run the game. Read the log. The intelligence packet your players ignore is the most important one you will ever write.