Clarity must be verified, not assumed
Every leader believes they briefed the team clearly. The simulation is where you find out whether the team received the same brief you thought you gave.
Ask a leader whether their team knows the priority this quarter and you will almost always get a yes. Ask the team, separately, and the answers spread out. Not wildly. Just enough that four people are optimising for four slightly different things, and nobody knows it.
This is the most common pattern we see in the room, and it is almost never a communication failure in the way people mean when they say communication failure. The brief was given. It was clear to the person giving it. What was missing was the step after.
What the simulation shows
In a pressured simulation, information is deliberately constrained and conditions get disrupted partway through. Under those conditions leaders default to what feels efficient, which is to restate the instruction, louder and faster. The instruction was never the problem. The problem is that nobody has checked what was received.
The teams that hold up do something small and specific instead. They stop, and they ask someone else to say the plan back. It costs about fifteen seconds. It is the single highest-leverage behaviour we observe, and it is the one most likely to be skipped when the pressure is on, because it feels like a delay.
Reset the system, don't push harder.
Why it disappears under pressure
Pressure narrows attention. A leader under load is tracking the clock, the obstacle, and their own read of the situation. Verification is the first thing to fall off, precisely because it feels like it produces nothing. Nothing new gets said. No progress is visible.
What verification produces is the absence of a problem you would otherwise discover twenty minutes later, when two people have built on incompatible assumptions. The cost is invisible when it works, which is why it is undervalued, and obvious when it is skipped.
What leaders do with this
The useful part is not the observation. Most leaders will nod at it. The useful part is seeing it in their own team, with their own people, in a moment they watched happen.
That is the difference between a principle and a piece of data. A principle gets agreed with and forgotten. A moment where your own team drifted, and you watched the drift start, tends to stay.
So the read we hand leaders is not a score on communication. It is the specific point in the simulation where clarity was assumed rather than confirmed, who noticed, and what it cost. From there the development work is obvious, and it is small.