What a 90 Minute Crisis Simulation Reveals About Your Team
Every team has two operating modes. There is the mode you see in meetings, where time is abundant, stakes are deferred, and everyone performs a little. And there is the mode that appears when something breaks, the clock compresses, and the next decision actually matters. Most leaders only discover the second mode when a real crisis arrives, which is the most expensive possible way to learn it.
A crisis simulation exists to surface that second mode on purpose, at a moment you chose, with the failure safely fictional. Here is what 90 minutes under load reliably reveals, drawn from the patterns we watch for across crews on our starship bridge.
The communication funnel
Under normal conditions, teams communicate in a mesh. Everyone talks to everyone. Under pressure, the mesh collapses into a funnel. Updates start flowing toward whoever seems most in charge, and lateral communication, the peer to peer traffic that actually solves distributed problems, quietly dies. On the bridge this is visible within minutes. Engineering stops telling Helm about the power situation and starts reporting only to the Captain, who becomes a bottleneck with a badge. Ask yourself who your funnel collapses toward, because that is your organization's single point of failure.
The silent expert
Nearly every crew contains someone who saw the problem early, said it once, quietly, and stopped pushing when nobody responded. In the transcript it is unmistakable. The warning was right there, two minutes before the cascade, phrased as a polite observation. The crew paid for the miss, and the person who was right learned that being right does not help if you stop at one attempt. In real organizations, this pattern has a body count of projects. The fix is trainable, both for the expert who needs persistence and for the leader who needs to close the loop on weak signals.
Tempo domination
Some leaders respond to pressure by accelerating. Decisions come faster, orders get shorter, and requests for input disappear entirely. Speed reads as competence, which is exactly what makes it dangerous. The fastest mover on your team may also be your least collaborative, and the two facts hide each other. In a mission transcript, you can watch the tempo dominator win the first act and strand the crew in the second, when the problem shifts to something no single station could see alone.
The recovery moment
The most hopeful pattern is the one teams rarely notice themselves. Somewhere in a degrading mission, coordination gets rebuilt. Often it is not the Captain. Someone starts repeating station reports back to the bridge, confirming who owns what, and reopening the input loop. Within moments the crew is functional again. Finding the person who instinctively does this is worth the entire exercise, because they are your recovery asset in the real world, and they are frequently not who the org chart predicts.
Why 90 minutes is enough
Habits do not need months to show. They need load. A well designed scenario compresses several full decision cycles into an hour and a half, information arrives distributed across roles so no one can solo it, and consequences accumulate so the pressure is felt rather than described. Behavior under those conditions is not a performance. There is no time to perform.
The catch is that revelation without a record evaporates. Adrenaline makes for unreliable memory, and a team that just flew a mission will remember the fun and forget the funnel. That is why the record matters more than the ride. Our missions run with the Mission Analysis System listening, so the debrief works from a role labeled transcript rather than recollection. The report shows the funnel forming, the silent expert's exact words, and the moment coordination came back, each claim tagged with our confidence in it.
Run the mission for the experience. Keep the report for the truth.