Setting Tempo on an Incident Bridge

In our Recovery Leadership cohort we ask participants to listen to an anonymised incident recording without taking notes for the first ten minutes. The exercise sounds gentle and is not. Most people surface from it with one clear observation: the bridge that resolved the incident well had a moment, somewhere in the first ten minutes, where someone deliberately slowed the tempo down.

The slowdown is not dramatic. It tends to sound like a single sentence — "let’s pause for a minute, what do we know, what are we guessing" — followed by a genuine sixty seconds of silence. In the recordings we use, that sixty seconds correlates more reliably with a calm resolution than any technical decision that follows.

The reason, we think, is structural. An incident bridge accumulates urgency the way a chat thread accumulates message count. Without a deliberate pause, the loudest interpretation tends to become the agreed interpretation, simply because nobody else has had time to say anything different. The pause restores the room.

The takeaway for new on-call leaders is small and practical. You do not need to know what to do. You need to give the room the space to say what it is seeing. Sixty quiet seconds is not slack; it is the most generous form of leadership you can offer a tired team at midnight.