The Surplus Expert: Designing Wargames That Survive Too Much Subject-Matter Knowledge in the Room

Most wargame designers worry about the room being too ignorant. Players who don't know the domain, who push pieces around without grasping the operational stakes, who need thirty minutes of background briefing before they can make a single meaningful decision. That failure mode is real and well-documented.

Photo by Matias Luge on Pexels.

The opposite problem gets almost no attention. What happens when the room knows too much?

Call it the surplus expert problem. You've assembled a group of former operators, senior analysts, retired flag officers, and subject-matter specialists who collectively hold decades of direct experience in exactly the domain your scenario covers. On paper, this looks ideal. In practice, the game dies inside the first hour.

Here's what the death looks like: players converge rapidly on the "correct" response. Someone with twenty years in theater recognizes the situation pattern and names it aloud. Everyone else nods. The decision cycle that should take four tense turns takes one. Tail outcomes get dismissed as unrealistic before the umpire can even introduce them. The scenario that was supposed to stress-test institutional assumptions instead confirms them, because everyone in the room built those assumptions.

This is not a failure of player engagement. These are serious, motivated people. The failure is a design failure.

Why Expert Consensus Kills Variance

Expert groups share more than knowledge. They share a vocabulary for dismissing possibilities. When a seasoned planner says "that's not how the logistics actually work" or "no commander would ever authorize that," the statement carries social weight that stops exploration cold. Junior players defer. Facilitators hesitate to push back. The game snaps to a stable, comfortable equilibrium.

Shared professional priors also make players faster at pruning the decision tree. That speed is genuinely useful in real operations. In a wargame designed to surface black swans, it's lethal. You need players to linger in the uncomfortable branches, not race toward the familiar trunk.

The 2002 Millennium Challenge wargame (JFCOM, Joint Forces Command) is the most cited example of what happens when unconventional play breaks expert consensus from the outside. Van Riper's Red force improvised specifically because conventional expert play had colonized Blue's decision cycle so thoroughly. But that case gets read backward: people focus on Van Riper's innovation rather than on Blue's brittleness. Blue was brittle precisely because expert consensus had foreclosed its ability to model an opponent who refused to follow doctrine.

Four Design Moves That Reopen the Decision Space

You can't uninvite the experts. You can build the game so their expertise doesn't become a veto.

Give experts the wrong domain. Assign the senior naval officer to run the logistics cell. Put the strategic analyst in charge of the local civilian population role. Expertise still enters the room, but it can't map directly onto familiar patterns. Players have to reason under genuine uncertainty rather than pattern-match their way to a conclusion.

Inject a mandatory anomaly turn. Before the game's midpoint, require each team to submit one move that their real-world counterpart would never make. Not a stupid move; an unexpected one. This is a design forcing function. It breaks the rhythm of expert consensus by making deviation procedurally required rather than socially transgressive. When deviation is the rule, no single player can shut it down by invoking operational realism.

Use a silent second game. Run a parallel track with a smaller group of non-experts or junior staff. Don't show either group the other's moves until a designated reveal point. Expert groups, when confronted with a divergent solution path from people they quietly dismissed, are forced to articulate why their path is better rather than simply assuming it. That articulation surfaces assumptions. Surfacing assumptions is the whole point.

Constrain the vocabulary. Prohibit domain jargon for the first two turns. No doctrinal terms, no theater-specific shorthand, no acronyms. This sounds punishing and slightly absurd; that's the point. Experts forced to describe a situation in plain language find that some things they treated as obvious are not obvious at all. The jargon was doing load-bearing work, and without it, the load becomes visible.

graph TD
    A[Expert Group Convenes] --> B{Consensus Forming?}
    B -- Yes --> C[Deploy Anomaly Turn]
    B -- No --> D[Continue Normal Play]
    C --> E[/Document Divergent Moves/]
    D --> E
    E --> F((Silent Track Reveal))
    F --> G{Assumptions Surfaced?}
    G -- Yes --> H[Post-Game Capture]
    G -- No --> C

What You're Actually Designing For

The goal of these moves isn't to make experts feel stupid or to privilege naive play. Expertise matters enormously in adjudication, in reality-checking, in preventing the game from becoming pure fantasy.

What you're designing against is the social physics of credential gravity: the way a room full of experienced people naturally orbits toward the most authoritative voice and the most recognizable pattern. Tail events don't look like recognizable patterns. That's definitionally what makes them tails.

If your wargame can only surface outcomes that your most senior player would have predicted before the game started, you haven't run a wargame. You've run a very expensive briefing.

Design the room so expertise is a resource, not a governor.