Decision-Cycle Wargame¶
Adversarial simulation method — instantiates Decision-Tempo Decoupling
Simulates how rival actors force, compress, delay, or misdirect each other's decision cycles — so the tempo trap is discovered in rehearsal, not in the live contest.
Most tempo failures are invisible on an org chart or a strategy deck; they only appear when two clocks run against each other. Decision-Cycle Wargame manufactures that collision in a sandbox. It plays out the contest before it is live, with one cell chartered to win on tempo — to force, compress, and misdirect the other side's decisions — and watches where the friendly cycle gets captured. Its defining move is giving the adversary genuine agency and a faster clock, rather than a cooperative foil: the game's unit of play is each side's orient-and-decide loop and how long it takes, so it surfaces timing failures that a move-by-move plan hides entirely. What it produces is not a prediction but a set of witnessed breakpoints and the response branches that survive them.
Example¶
A company's board suspects an activist investor is about to launch a public campaign. Before anything is live, the corporate-defense team runs a Decision-Cycle Wargame. One cell plays the activist: it drafts the open letters, times the leaks for Friday afternoons, and stacks demands to force rushed board responses. Another cell plays the company. Played out, the team discovers its weak point is not strategy but cadence: the board can only convene and approve a response on a multi-day cycle, while the activist can publish daily — so by the time the company answers one letter, two more have landed. That discovery reshapes the plan: a standing response envelope for the investor-relations lead, a pre-agreed set of holding statements, an emergency-quorum rule for the board. None of it was visible on the strategy deck; it surfaced only once the two clocks were run against each other.
How it works¶
- Give the adversary a real clock and real agency. The opposing cell is licensed to win on tempo — to force, compress, and misdirect — not to play a convenient sparring partner.
- Run cycles, not just moves. The unit of play is each side's orient-and-decide loop and its duration, so the game exposes timing failures a move-list conceals.
- Branch the response repertoire. At each forced moment, explore the several responses available — ignore, prepared action, delegate, delay — and see which branch the opponent was counting on you to skip.
- Harvest the breakpoints. Record where the friendly cycle was captured, and turn each into a design change before the live contest can exploit it.
Tuning parameters¶
- Adversary aggression — how hard the opposing cell may push tempo. Too gentle and the trap never appears; too cartoonish and you rehearse a fantasy.
- Fidelity vs. speed — a two-hour tabletop or a multi-day run with real communication latency. Higher fidelity exposes subtler tempo failures at higher cost.
- Scenario spread — one scripted contest or many divergent openings. A single script risks preparing for exactly one future; a spread tests cadence robustness.
- Fog level — how much the friendly cell is denied perfect information, since tempo traps bite hardest under uncertainty.
- Branch depth — how many response options are explored at each decision point before the game moves on.
When it helps, and when it misleads¶
Its strength is that it converts an abstract worry — "we might be too slow" — into a concrete, witnessed failure, and does so cheaply, before any real commitment is on the table. The whole aim is to get inside the adversary's decision cycle in rehearsal: to learn where your loop can be shortened and theirs lengthened while the stakes are only a scorecard.[n1]
Its failure modes are the wargamer's classics. A scripted scenario rehearses the wrong contest, leaving the team superbly prepared for the one attack that never comes. The exercise is easily run backwards — staged to validate a plan leadership has already chosen rather than to break it — which breeds false confidence exactly where it is most dangerous. And a game whose adversary is too weak certifies a cadence that will shatter on contact. The discipline that guards against this is a genuinely adversarial red cell, several divergent scenarios, and treating a wargame that fails to break your cycle as evidence the game was too easy, not proof that you are ready.
How it implements the components¶
Decision-Cycle Wargame fills the rehearsal-and-discovery part of the archetype — the components that model the contest before it is real:
contested_decision_cycle_map— play builds a dynamic, two-sided model of both actors' loops and where they intersect.tempo_asymmetry_profile— the game reveals, in motion, how much faster one clock runs and precisely how the gap is exploited.action_repertoire_branching— at each forced moment it explores the branching set of available responses, mapping the decision tree the live contest will walk.
It rehearses and stress-tests the design but does not run it live: prepared responses are stored in the Preauthorized Playbook, the standing intake structure is the Asynchronous Decision Queue, and lessons from real surges come from the Cadence Reset Retrospective.
Related¶
- Instantiates: Decision-Tempo Decoupling — the wargame is the pre-contest laboratory where the design's tempo weaknesses are found and fixed.
- Consumes: the Tempo Pressure Map, whose current picture of the contested cycles supplies the wargame's opening position.
- Sibling mechanisms: Cadence Reset Retrospective · Tempo Pressure Map · Tempo-Trap Red-Team Review · Preauthorized Playbook · Mission Command or Delegated Authority Cell · Response-Obligation Matrix · Trigger-Based Response Rule · Asynchronous Decision Queue · Deliberate Response-Delay Window · Rate Limit and Cooldown Rule · Independent Signal Verification Lane
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Decision-Cycle Wargame operates as a bounded trial, probe, simulation, or rehearsal that generates evidence from performance because it simulates how rival actors force, compress, delay, or misdirect each other's decision cycles — so the tempo trap is discovered in rehearsal, not in the live contest.
Independent corroboration: The frozen evidence defines Decision-Cycle Wargame as 'Simulates how rival actors force, compress, delay, or misdirect each other's decision cycles — so the tempo trap is discovered in rehearsal, not in the live contest', so its operative form is Experiment, Test & Rehearsal.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Military & Strategic Studies
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Military wargaming cohered adversarial sandbox exercises in which opposing cells have genuine agency and competing decision tempos, revealing breakpoints and viable response branches.
Review outcome: Independent reviewer agreement; high confidence.
Notes¶
The wargame and the Tempo Pressure Map both touch the contested-cycle picture, but in different tenses: the map charts the current, standing asymmetry, while the wargame sets that picture in motion against a thinking adversary. Use the map's baseline as the wargame's opening position, and feed the wargame's discovered breakpoints back into the map.
[n1] The OODA loop (observe–orient–decide–act), articulated by strategist John Boyd, who argued that prevailing in a contest often means operating inside the opponent's decision cycle — deciding and acting faster than they can reorient. A decision-cycle wargame is a way to rehearse exactly that dynamic. ↩