Executives have legitimate concerns during major incidents—ensuring appropriate urgency, allocating resources, understanding impact. But their presence can inadvertently create pressure that slows resolution or discourages people from surfacing problems.
Example
When executives joined the bridge during the Google Cloud outage, they didn't speak up to interrogate decisions or push for faster resolution. They stayed out of the way. When the engineer called in to identify their change as the likely cause, the incident commander's response was purely functional: "Thank you for that information. Now let's validate whether your fix worked." Recognition and debrief came later, after recovery. In the moment, the focus was on creating space for information to flow.
Context
This requires pre-established norms about executive involvement in incidents. Executives need to trust that responders have appropriate urgency without adding pressure. Responders need to know that executives are there to unblock and support, not to judge. The instinct to "help" by asking questions or offering suggestions can backfire when it adds cognitive load or creates fear of judgment. Sometimes the most valuable thing leadership can do is make sure the right people have what they need, then stay quiet.
When This Might Not Apply
– Incidents with immediate existential business threats (revenue completely halted) where escalation is required. – Leadership without pre-established incident norms (needs training first).
Variations
– For remote executives, use separate stakeholder update channels rather than main bridge. – In cross-team incidents, have executives allocate additional on-call engineers rather than joining technical discussion.
