Executives get trained on entry. Nobody trains them on exit.
So they drift. They stop talking, stay on mute, and eventually drop off the bridge without saying anything. The team cannot tell whether authority left with them, so they wait. Silence from the most senior person in the room reads as supervision.
Google's Site Reliability Engineering handbook is blunt about this, and it was written for engineers, not executives. On handing off incident command at the end of a shift: the outgoing commander “should be explicit in their handoff, specifically stating, ‘You're now the incident commander, okay?’, and should not leave the call until receiving firm acknowledgment of handoff.”
Say that sentence out loud and notice how uncomfortable it is. Then notice that you have never said anything like it while leaving an escalation.
Three conditions confirm you can go. Command, cadence, authority.
Command is stable, and someone is visibly running the response. The customer communication cadence is running on schedule. Authority for every remaining decision has already been delegated. All three, not two.
Learn those three words. You will use them for the rest of this series and for the rest of your career, and they take about four seconds to run in your head while the bridge is live.
The fear underneath this is that leaving makes it look like you stopped caring. It looks that way when you vanish. It looks like leadership when you name it: who has command, what you are still available for, and when you want the next update.
Next week: the senior leader who walks in at hour six and takes the room without meaning to.
Stepping back on purpose does not read as absence. It tells the room the structure holds without you.
Source: Google SRE, "Managing Incidents," sre.google/sre-book/managing-incidents