Scenario Tabletop Review¶
Ritual — instantiates Completeness Audit
Walks a group through plausible scenarios, edge cases, incidents, or user journeys to discover missing rules, owners, data, or response paths.
A Scenario Tabletop Review gathers the people who would actually respond and walks them, out loud and in real time, through a handful of selected plausible scenarios — an incident, an edge case, a user journey — asking at every step: who acts, under what rule, using what data, down what path? Its defining move, distinct from every list-confirming sibling, is that it is generative: by enacting a scenario rather than checking a pre-made list, it surfaces gaps nobody had enumerated — a step with no owner, a decision with no rule, a hand-off with no data — the taxonomy blind spots a static audit structurally cannot see. Because the scenario space is unbounded, it probes with a representative or adversarial few rather than pretending to enumerate them all.
Example¶
A hospital runs a two-hour tabletop of a ransomware scenario, with clinicians, IT, security, legal, and communications in the room. The facilitator injects the opening: "It is 2 a.m., the electronic health record is encrypted, and the on-call physician cannot pull a patient's medication list." The group plays it forward, and gaps appear immediately that no checklist held. No one is certain who has the authority to declare a clinical downtime. The paper-fallback medication list has not been refreshed in a year — data that should be there is missing. The communications plan assumes email that is now, in the scenario, down — a response path with no route. Each surfaced gap is written into the after-action record with a named owner and a due date. The exercise did not confirm a known list; it discovered the unknown by living it.[n1]
How it works¶
The review selects a small set of representative or worst-case scenarios — a probe of the space, never a census of it — and injects them step by step under something like real conditions. At each step it elicits the four things a response needs (owner, rule, data, path) and records wherever one is absent. What distinguishes it from its siblings is dynamic enactment: gaps are found by playing the situation out, which is the only way to expose the combinations, transitions, and unexpected pathways that a pre-authored taxonomy quietly omits. Every discovered gap is then bound to an owner and an action so that discovery converts to closure rather than a memorable anecdote.
Its use of representative-or-adversarial sampling makes it a cousin of the Test Coverage Audit, which also probes rather than enumerates — but that mechanism runs automated mutations over code, whereas this one runs a human group over lived scenarios.
Tuning parameters¶
- Scenario selection — representative versus worst-case versus adversarial injects. Adversarial finds more but can feel unrealistic, eroding buy-in.
- Injection realism — a high-level walk versus live curveballs and time pressure. More realism surfaces more, at higher prep cost and participant stress.
- Participant breadth — responders only versus including boundary roles (legal, communications, frontline). A missing role hides exactly the gaps that role would own.
- Facilitation stance — letting the group self-report versus actively probing stated assumptions.
- Documentation rigor — informal notes versus a structured after-action record with owners and due dates.
When it helps, and when it misleads¶
Its strength is that it is the only mechanism here that finds gaps on no list at all, and it builds shared situational memory in the responders as a byproduct. Its failure mode is inherent to sampling: a scenario you did not play is a gap you did not find, so a tabletop proves nothing about the unplayed space, and a poorly chosen scenario set breeds false confidence. The classic misuse is the "success-theater" tabletop, scripted so the team looks capable, which surfaces nothing because it was designed not to. The guarding discipline is to choose scenarios adversarially from real incidents and near-misses, vary them across exercises, and treat the review strictly as gap discovery — never as coverage proof.
How it implements the components¶
sampling_probe— it audits an unbounded scenario space by enacting a representative or adversarial sample of scenarios rather than enumerating them.gap_analysis— each enacted step exposes missing rules, absent data, or unowned response paths: gaps discovered by playing the scenario out.accountable_gap_owner— every gap the exercise surfaces is assigned a named owner and an action in the after-action record, so a discovery becomes a tracked commitment.
It runs as a discrete exercise, not a standing schedule, so it does not keep the recurring audit_cadence that Risk Register Review maintains; and it discovers and assigns gaps but does not set the formal disposition rules — that gap_resolution_policy is Policy Gap Analysis. (Its owner-assignment attaches to gaps discovered live, whereas Risk Register Review binds owners to standing register rows.)
Related¶
- Instantiates: Completeness Audit — it discovers coverage gaps that no pre-made list contains.
- Sibling mechanisms: Coverage Checklist Walkthrough · Data Completeness Check · Policy Gap Analysis · Risk Register Review · Stakeholder Inclusion Review · Test Coverage Audit · Requirements Traceability Matrix
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Scenario Tabletop Review operates as an active test, trial, simulation, drill, or rehearsal that generates evidence through a deliberate attempt or perturbation because it walks a group through plausible scenarios, edge cases, incidents, or user journeys to discover missing rules, owners, data, or response paths.
Independent corroboration: The frozen evidence defines Scenario Tabletop Review as 'Walks a group through plausible scenarios, edge cases, incidents, or user journeys to discover missing rules, owners, data, or response paths', so its operative form is Experiment, Test & Rehearsal.
Nearest alternative: Assessment, Review & Assurance — Scenario Tabletop Review includes features of a bounded evaluation of existing evidence or work that produces a finding or disposition, but its defining operation is an active test, trial, simulation, drill, or rehearsal that generates evidence through a deliberate attempt or perturbation.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Disaster Management & Risk Reduction
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Discussion-based tabletop discovery of response gaps is emergency-preparedness practice.
Related originating lineages:
- Human-Computer Interaction — User-journey walkthroughs independently expose missing paths.
- Military & Strategic Studies — Military planning, readiness, and strategic operations supplies a parallel or contributing lineage for the mechanism's defining operation: walks a group through plausible scenarios, edge cases, incidents, or user journeys to discover missing rules, owners, data, or response paths.
- Organizational & Management Science — Cross-functional review materially identifies owners and policy gaps.
- Public Administration & Policy — Public administration, policy implementation, and program oversight supplies a parallel or contributing lineage for the mechanism's defining operation: walks a group through plausible scenarios, edge cases, incidents, or user journeys to discover missing rules, owners, data, or response paths.
Review resolution: Both blind reviewers agree that disaster_management is the primary historical origin. Explicit reconciliation of alternate_origin_disagreement, domain_reach_disagreement, encyclopedia_synthesis_disagreement starts from reviewer_a's mechanism-specific evidence: Discussion-based tabletop discovery of response gaps is emergency-preparedness practice. Reviewer A proposed alternates=human_computer_interaction, organizational_management, origin_mode=convergent, domain_reach=multi_domain, and encyclopedia_synthesis=true; reviewer B proposed alternates=military_strategic_studies, public_administration_policy, origin_mode=convergent, domain_reach=universal, and encyclopedia_synthesis=false. The final record retains every independently supported alternate from either review (human_computer_interaction, organizational_management, military_strategic_studies, public_administration_policy) without an arbitrary cap, selects origin_mode=convergent to represent the combined lineage evidence, and records domain_reach=universal and encyclopedia_synthesis=true. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] A tabletop exercise is a discussion-based, facilitated walkthrough of a scenario used in emergency management and incident response (formalized in frameworks such as FEMA's Homeland Security Exercise and Evaluation Program), typically closing in an after-action report that captures findings and assigns corrective actions. Its purpose is discovery and shared understanding, not a pass/fail certification of readiness. ↩