Incident bridges don't waste time on technical problems — they waste it on social overhead: who's leading, who's talking, who's writing, what "done" means. Five rituals fix most of it. None cost money.
1. The 15-second role claim
The first words on any bridge are roles, not status: "I'm IC, Alex is comms, Sam on ops." If nobody claims IC within 15 seconds of the second person joining, the loudest voice becomes IC by default. That's how bridges turn into debates. Make the claim explicit and scripted.
2. One scribe, always
If nobody's writing, nobody's learning. One person (IC or a rotating scribe) posts a running log in the incident channel: timestamps, decisions, owners. Not a transcript — decisions. This log becomes the post-mortem skeleton for free and stops the "wait, when did that happen?" archaeology.
3. Speak in decisions, not updates
Ban "just checking in" talk. The IC runs the bridge on a fixed loop: "Status: X. Actions: Y, owner Z, next update in 10." Everyone else gives exceptions only. If your update wouldn't change anyone's next action, don't say it. This one rule halves bridge length in practice.
4. The parking lot
Side conversations kill bridges. When someone drags the call into root-cause details irrelevant to the current fix, the IC parks it: "Noting for post-mortem, moving on." Say it kindly, say it every time. The parking lot is written into the scribe log so it's never lost — just deferred.
5. The 25-minute check
Every 25 minutes, the IC asks one question: "Are we still working the right problem?" It's the difference between a bridge that drifts for two hours and one that pivots at 25 minutes when the first fix didn't hold. Timer in the channel, not in someone's head.
Make them the default
These work because they're scripts, not judgment calls. We ship the wording — role claims, scribe format, the parking lot line, escalation ladder, handover template — in The Automation Starter Pack (A$19, HIVE-LAUNCH30 for 30% off the store).
Free starting point: The First 30 Minutes — the opening checklist that pairs with the role-claim ritual above.
Related: Severity matrices: why 3 levels stick · The escalation ladder that ends pager ping-pong
Top comments (0)