Coordination Rehearsal Session¶
Procedure — instantiates Shared Mental Model Alignment
A tabletop, simulation, dry run, or walkthrough in which people enact the shared plan against injected conditions, so residual divergence shows up as colliding action rather than as a later surprise.
Verbal agreement is cheap and misleading: people can nod at the same plan while imagining different behavior under pressure. A Coordination Rehearsal Session is the procedure that makes the difference visible by making people act. In a tabletop, a simulation, a dry run, or a walkthrough, the team executes the shared model against injected conditions — and the moments where two roles collide, contradict, or wait on each other are the residual misalignment surfacing as observable behavior. Its defining move is that it is behavioral testing of a model already thought to be shared: not building the plan, not merely discussing it, but running it far enough to see whether it survives contact. What a briefing asserts and a planning session agrees, a rehearsal puts under load — which is why it catches the divergence that words alone leave buried.
Example¶
Before a launch, a spaceflight team runs a wet dress rehearsal: the full crew and control room execute the countdown, in real time, with propellant loaded but no ignition — and then the test director injects an off-nominal reading. On paper, everyone "knew" the hold criteria. In the rehearsal, two consoles call for a hold on the same anomaly using different thresholds, and a third assumes a fourth is monitoring a parameter that nobody owns. None of that appeared when the procedure was written or briefed; it only appeared when the divergent readings turned into contradictory calls in real time. The team debriefs each collision, resolves who owns what and which threshold governs, and folds the fixes back into the procedure before a launch where the injects are real.
The rehearsal's whole value is that the surprise happens on the ground. A plan that reads clean can still contain a role nobody owns; only enacting it exposes the gap.
How it works¶
- Inject a scenario. Present the team with concrete conditions — nominal, then off-nominal — rather than an abstract "walk me through the plan."
- Enact roles in real time. People execute their actual roles against the injects, so behavior, timing, and dependency are exercised, not just recited.
- Observe the collisions. Watch for where actions contradict, where two people wait on each other, and where a call is made on a different threshold — the residual divergence.
- Debrief into the model. Convert each observed collision into a repair to the shared reference: an owned role, a resolved threshold, a clarified dependency.
Tuning parameters¶
- Fidelity — a talk-through tabletop versus a full-scale live simulation. High fidelity surfaces more real divergence but costs time, money, and staging; low fidelity is cheap but exercises intention more than behavior.
- Scenario stress — rehearsing the nominal path versus injecting worst-case surprises. Stress reveals where the model breaks; a soft scenario validates rather than tests.
- Repetition — one pass versus iterated runs. Repetition drills the repaired model in but risks memorizing a specific script rather than the underlying coordination.
- Observer role — self-run versus an outside white-cell scoring the run. An outsider catches shared blind spots; insiders read tacit context faster.
When it helps, and when it misleads¶
Its strength is that it reveals divergence that verbal alignment hides — the residual mismatch that only appears once people act under time and uncertainty. It is most valuable exactly where the cost of discovering the gap live is high.
Its central failure mode is rehearsing the happy path: a scripted, gentle scenario the team already knows how to pass, which validates confidence instead of testing the model — training to the test. The classic misuse is a rehearsal whose injects are chosen to be survivable, so it certifies readiness that isn't there. The discipline that guards against this is to train as you fight[n1] — inject the surprises and the worst cases the real situation can produce, and treat a rehearsal that surfaces no divergence as suspect rather than reassuring.
How it implements the components¶
Coordination Rehearsal Session fills the enact-and-detect components — the ones only acting out the model can produce:
coordination_rehearsal— it is the rehearsal: an enacted test of whether the shared model actually guides coordinated action under conditions.misalignment_signal— divergent behavior under the injected scenario is the signal; a collision between two roles is misalignment made observable.
It does not build the plan or map roles, dependencies, and escalation up front — assumption_comparison, role_constraint_state_map, and escalation_path are the work of Cross-Functional Planning Session; and it does not maintain the standing reference artifact (shared_reference_model, model_owner) — that is Common Operating Picture. Unlike Pre-Mortem, which imagines failure without enacting anything, this mechanism physically runs the model to find where it breaks; and unlike the retrospective After-Action Review, it tests before the event rather than harvesting lessons after.
Related¶
- Instantiates: Shared Mental Model Alignment — the rehearsal is the behavioral test that turns a nominally-shared model into one proven to guide joint action.
- Consumes: Cross-Functional Planning Session — it rehearses the plan and role map that a planning session produces.
- Sibling mechanisms: Briefback · Common Operating Picture · Incident Briefing · Handoff Checkback · Pre-Mortem · Shared Situation Model · After-Action Review
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Coordination Rehearsal Session operates as a bounded trial, probe, simulation, or rehearsal that generates evidence from performance because it a tabletop, simulation, dry run, or walkthrough in which people enact the shared plan against injected conditions, so residual divergence shows up as colliding action rather than as a later surprise.
Independent corroboration: The frozen evidence defines Coordination Rehearsal Session as 'A tabletop, simulation, dry run, or walkthrough in which people enact the shared plan against injected conditions, so residual divergence shows up as colliding action rather than as a later surprise', 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 exercises and war games cohered rehearsal of shared plans against injected conditions to expose conflicting role assumptions before action.
Related originating lineages:
- Disaster Management & Risk Reduction — Emergency-management exercises independently institutionalized rehearsals of roles, communications, handoffs, and contingencies.
Review resolution: Both reviewers agree on the military primary and disaster-management alternate. Exercise traditions converged across military and emergency response; organizational teams are later users rather than an independently necessary origin.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] "Train as you fight" — the military maxim that rehearsal must reproduce the stress, friction, and surprise of the real event, because a team that has only rehearsed the easy case will coordinate no better than one that never rehearsed at all when the hard case arrives. ↩