Operational Scenario Rehearsal¶
Rehearsal drill — instantiates Operational Context Validation Testing
Puts real operators through end-to-end operational scenarios — including contingencies and the rollback drill — to validate the human-in-the-loop workflow before go-live.
An Operational Scenario Rehearsal takes the real people who will run the system and has them enact the whole operational workflow — normal cases, edge cases, contingencies, and the cutover-and-revert drill — under conditions close enough to go-live that the enactment is real work, not a walkthrough. Its defining idea is that the thing under test is not the artifact but the socio-technical loop: operators, procedures, handoffs, communications, and tools together, exercised as a system. A machine can pass every bench test and still fail on day one because the humans around it were never rehearsed in the scenarios that matter — the confusing alarm, the degraded-mode handoff, the moment someone must decide to fall back. The rehearsal is where those scenarios are practiced with the actual crew before the stakes are real.
Example¶
A city's 911 center is cutting over to a new computer-aided dispatch (CAD) system. The software passed its acceptance tests, but a dispatch floor is a human machine, and a bad cutover means dropped emergency calls. So before go-live, the actual dispatchers — the panel who will run it live — work a full rehearsal against scripted scenarios: a routine medical call, a multi-unit structure fire with mutual aid, a mass-casualty surge, and a mid-shift system slowdown. They run each scenario end to end on the new CAD, including the handoffs to radio and the escalation to a supervisor, verifying that each required dispatch behavior actually happens under their hands. The final scenario is the one nobody likes to practice: the CAD degrades, and the crew rehearses reverting to the fallback paper-and-radio procedure and back. The rehearsal exposes that the surge scenario overwhelms the new call-queue view — a workflow failure invisible to any test of the software alone.
How it works¶
- Assemble the real crew. The people who will operate the system on day one are the participants — not testers or stand-ins — because the workflow being validated is theirs.
- Script scenarios across the operating envelope. Normal, boundary, degraded, and emergency scenarios are scripted so the rehearsal exercises the procedures and handoffs that the routine case never reaches.
- Verify required behavior in the loop. Each scenario is checked against what the workflow is required to produce, so a rehearsal yields pass/fail on procedures, not just impressions.
- Rehearse the fallback. The cutover and its reversal are drilled explicitly, so reverting under pressure on go-live day is a practiced motion rather than an improvisation.
Tuning parameters¶
- Scenario coverage — how much of the operating envelope is scripted. Broader coverage rehearses more contingencies but costs crew time and scenario design.
- Fidelity of conditions — tabletop discussion, part-task drill, or full-dress rehearsal under realistic load and time pressure. Higher fidelity reveals more but is costly and disruptive to staff.
- Crew representativeness — top performers, or the actual shift mix including new and tired staff. Representative crews surface real workflow friction; hand-picked crews flatter it.
- Injected surprise — fully scripted, or with unannounced faults and curveballs. Surprise tests adaptability but is harder to run and to evaluate fairly.
- Debrief depth — quick sign-off versus structured after-action review. Deeper debriefs extract more learning at the cost of time.
When it helps, and when it misleads¶
Its strength is that it validates the part of deployment that lives in people and procedures — the handoffs, the degraded-mode decisions, the muscle memory of falling back — which no test of the artifact alone can reach, and it builds the crew's competence in the same motion. Its central failure mode is the gap between work-as-imagined and work-as-done: a rehearsal validates the scenarios someone thought to script, and real operations improvise around exactly the situations the script never imagined, so a flawless rehearsal can still miss the workaround that appears in week two.[n1] The classic misuse is a scripted, over-prepared rehearsal run for stakeholders that certifies the crew on a tidy fiction. The guarding discipline is to inject unscripted surprise, use a representative crew, and treat the rehearsal as complementary to observing real work once live.
How it implements the components¶
An Operational Scenario Rehearsal fills the people-and-procedures slice of the archetype:
site_and_user_panel— the real operating crew is the panel; the workflow under test is theirs to enact.requirement_behavior_trace— each scenario is judged against the behavior the workflow is required to produce, giving procedure-level pass/fail.deployment_reversibility_plan— the cutover-and-revert is drilled as a scenario, so the reversibility plan is rehearsed, not just written.
It does not implement operational_context_model or representative_environment_selection — it does not build or select the environment it runs in; it supplies people enacting scenarios *within an environment. Engineering that high-fidelity replica is the Production-Like Testbed's job, and standing instrumentation of real ongoing work is the Workflow Observation Log's.*
Related¶
- Instantiates: Operational Context Validation Testing — validates the socio-technical workflow and builds crew readiness before go-live.
- Consumes: Production-Like Testbed — a high-fidelity rehearsal is typically staged in a production-like environment so the enactment feels real.
- Sibling mechanisms: Field Acceptance Test · Shadow-Mode Trial · Canary or Limited Rollout · Production-Like Testbed · Environmental Stress Run · Workflow Observation Log · Go/No-Go Review Gate
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Operational Scenario Rehearsal operates as an active test, trial, simulation, drill, or rehearsal that generates evidence through a deliberate attempt or perturbation because it puts real operators through end-to-end operational scenarios — including contingencies and the rollback drill — to validate the human-in-the-loop workflow before go-live.
Independent corroboration: The frozen evidence defines Operational Scenario Rehearsal as 'Puts real operators through end-to-end operational scenarios — including contingencies and the rollback drill — to validate the human-in-the-loop workflow before go-live', so its operative form is Experiment, Test & Rehearsal.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Military & Strategic Studies
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Military staff practice established structured scenario rehearsal and war-gaming as a way to expose operational assumptions, coordination failures, and branch conditions before live action.
Related originating lineages:
- Aviation & Aeronautics — End-to-end operator rehearsals and simulations are canonical in aviation training and operational certification.
- Disaster Management & Risk Reduction — Operational Scenario Rehearsal is most directly rooted in disaster management and risk reduction's traditions of preparedness, stress exercises, response, and recovery. The lineage fits its defining practice: Puts real operators through end-to-end operational scenarios — including contingencies and the rollback drill — to validate the human-in-the-loop workflow before go-live.
- Engineering & Design — Resilience and safety engineering materially shaped work-as-done validation, rollback, and recovery testing.
- Organizational & Management Science — Operational Scenario Rehearsal also draws materially on organizational and management science's practice of coordinating people, authority, strategy, knowledge, and work, which shaped this mechanism rather than merely adopting it as an application.
Review resolution: Authoritative-source research resolves the primary-origin disagreement in favor of military strategic studies. Homeland Security Exercise and Evaluation Program — FEMA documents the formative practice or theory represented here. The retained alternate domains identify material co-development or translation, while current applicability is recorded separately as domain_reach=multi_domain; origin_mode=convergent describes the historical relationship among lineages.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] The distinction between work-as-imagined (how procedures assume work is done) and work-as-done (how people actually accomplish it under real constraints), central to resilience engineering, explains why a rehearsal of scripted scenarios can pass while the improvised realities of live operation later expose gaps. ↩