Domino Tabletop Exercise¶
Rehearsal exercise — instantiates Cascade Pathway Management
Rehearses a mapped cascade scenario as a facilitated talk-through, stress-testing who has authority to act and whether the response can outrun the front.
A Domino Tabletop Exercise takes a specific, already-identified cascade scenario and walks a response team through it out loud, injecting one downstream development at a time to see whether the humans and their decision rights hold up under the pace of a real chain reaction. Its defining property is that it exercises the response, not the pathway: the dominoes are given, and the test is whether the right person can be found, given authority, and made to act at each hop before the next domino falls. Nothing in the real system is touched — it is a discussion around a table — but the clock is the point. It surfaces the fatal gap the archetype calls control without authority: everyone knows what should happen and no one is allowed to make it happen in time.
Example¶
A county emergency-management office prepares for a chemical release at a riverside plant. The pathway is already mapped, so the exercise is not to discover consequences but to rehearse the response. Around the table: the plant's incident commander, the county fire chief, a water-utility manager, a hospital liaison, the schools' safety officer, and a public-information officer. A facilitator runs the clock and injects developments.
"T+0: a chlorine leak is detected at the plant." The plant commander orders evacuation — but the injects come faster than comfortable. "T+12 minutes: the plume is drifting toward the water intake." Who has the authority to shut the intake — the utility manager, or does it need the county's sign-off? The room discovers the answer is unclear, and in the pause the notional plume reaches the intake. "T+25: schools downwind must shelter in place" — but the safety officer's authority to order it crosses into the school district, a different jurisdiction, and the hand-off protocol turns out to be a phone number nobody has tested. The exercise's value is exactly these discovered gaps: two decisions that needed pre-delegated authority and one cross-boundary hand-off that would have failed. They are fixed on paper before a real leak ever forces the question.
How it works¶
- Start from a given scenario, not a blank page. The cascade is pre-selected and its pathway assumed; the exercise spends its energy on the response to that scenario, not on inventing it.
- Inject developments against a clock. A facilitator feeds the next downstream event at a realistic tempo, so the team must decide and act inside the window the real cascade would allow — the race between response and propagation is simulated by pacing.
- Test authority at each decision point. At every hop the exercise asks who may act and whether that authority is pre-delegated, exposing decisions that would stall waiting for someone who isn't in the room.
- Stress the boundary hand-offs. Where the response crosses into another jurisdiction or organization, the exercise walks the hand-off explicitly, because cross-boundary transfers are where real responses most often break.
Tuning parameters¶
- Inject tempo — how fast developments are fed. A brisk tempo exposes decision bottlenecks under realistic pressure but can overwhelm learning; a slow tempo is easier to discuss but lets a stall pass unnoticed.
- Curveball rate — how often an inject departs from the expected script. More curveballs test adaptability and hidden dependencies; fewer keep the exercise focused on the primary chain.
- Authority realism — whether players may invoke authority they don't actually hold. Enforcing real authority surfaces true gaps; relaxing it keeps the exercise moving but can paper over the very problem being tested.
- Scope breadth — how many downstream domains the scenario is allowed to reach. Broader scope stresses more hand-offs but dilutes depth; narrower scope drills one interface hard.
When it helps, and when it misleads¶
Its strength is cheap, safe discovery of the human failures a diagram can't show: the missing pre-delegation, the untested phone number, the jurisdictional seam where a hand-off silently drops. Because it costs only a room and an afternoon, it can be rerun after every reorganization to keep the response current. It follows the established discipline of scenario-based response rehearsal.[n1]
Its failure mode is that talk is not action. A team can perform beautifully around a table and still freeze when real alarms sound, adrenaline spikes, and the injects are messier than any facilitator's script. Tabletops also drift toward the comfortable path — players cooperate, information arrives cleanly, and the exercise validates a response that reality would shred. The classic misuse is treating a successful tabletop as proof of readiness, when it has only proven the plan is coherent on paper. The guarding discipline is to inject genuine friction and authority-gaps, to escalate periodically to live or functional exercises that actually move people and systems, and to log discovered gaps as fixes rather than as reassurance.
How it implements the components¶
response_authority_map— its core work: it walks each decision point and verifies who is authorized to act, exposing where authority must be pre-delegated.cascade_breakpoint_set— it rehearses when and by whom the pre-identified breakpoints are actually pulled, testing the decision to cut rather than the cut itself.cross_domain_boundary_map— it stresses the hand-offs where the response crosses into other jurisdictions or organizations, the seams most likely to fail live.
It exercises a scenario given to it; it does not discover the pathway — surfacing what a trigger might set off, and running a residual_cascade_review_loop, is its nearest process-twin, Consequence Cascade Workshop. Nor does it execute anything: it never runs a scenario_or_simulation_model against a real or emulated system — that live injection belongs to Propagation Simulation or Fault Injection. The workshop imagines the dominoes, this exercise talks through catching them, and the simulation actually knocks one over.
Related¶
- Instantiates: Cascade Pathway Management — the exercise is the archetype's response-readiness rehearsal against a chosen cascade.
- Consumes: Consequence Cascade Workshop or a pathway map supplies the scenario the exercise rehearses.
- Sibling mechanisms: Propagation Simulation or Fault Injection · Consequence Cascade Workshop · Cascade Circuit Breaker · Rate-Limit or Quarantine Gate · Cascade Dependency Graph · Dependency Cut-Set Review · Leading-Link Indicator Dashboard · Beneficial Cascade Seeding Plan
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Domino Tabletop Exercise operates as a bounded trial, probe, simulation, or rehearsal that generates evidence from performance because it rehearses a mapped cascade scenario as a facilitated talk-through, stress-testing who has authority to act and whether the response can outrun the front.
Independent corroboration: The frozen evidence defines Domino Tabletop Exercise as 'Rehearses a mapped cascade scenario as a facilitated talk-through, stress-testing who has authority to act and whether the response can outrun the front', so its operative form is Experiment, Test & Rehearsal.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Disaster Management & Risk Reduction
Origin pattern: Single lineage
Present-day reach: Specialized
Rationale: Emergency management cohered tabletop exercises as facilitated, discussion-based rehearsals of cascading incidents, authority, communication, and response timing.
Related originating lineages:
- Military & Strategic Studies — War-gaming and staff exercises supplied an older lineage of talking through sequenced contingencies.
Review resolution: Emergency management cohered facilitated cascade table-tops, with military staff exercises an older, materially formative lineage.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Tabletop exercise — in emergency management (e.g. the US HSEEP framework), a discussion-based session where responders talk through their roles in a hypothetical incident. It is deliberately distinguished from functional and full-scale exercises, which mobilize real people and equipment. ↩