An executive should join a customer escalation when a written threshold is crossed: business impact past a defined line, regulatory or legal exposure, a customer executive escalating to their level, or a commercial commitment above a set limit.
They should step out once three conditions hold: command is stable, customer updates are running on schedule, and every remaining decision has an owner. Then they hand off out loud and wait for the acknowledgment before leaving.
Joining: test your rule against your history
Pull the last five escalations you joined and write the reason next to each one. If the reasons read like account size, a relationship with the customer, or a bad feeling at 9pm, there is no entry rule at work. There is a reflex, and your organization has learned to trigger it.
Now write your rule in one sentence and test it against those five. If the sentence would have kept you out of two of them, it is a rule. If it would have let you into all five, it is a description of your habit.
Stepping out: command, cadence, authority
Executives get trained on entry. Nobody trains them on exit, so they drift: they stop talking, stay on mute and eventually drop off the call. The team can't tell whether authority left with them, so they wait.
Three conditions confirm you can go:
- Command: someone is visibly running the response.
- Cadence: customer updates are going out on schedule.
- Authority: every remaining decision has already been delegated.
All three, not two. Then say it. Google's incident guidance tells an outgoing incident commander to be explicit, say "You're now the incident commander, okay?", and stay on the call until the handoff is acknowledged. The same discipline works for an executive leaving an escalation: who has command, what you are still available for, and when you want the next update.
Joining one that is already running
If you join hours in, do three things in order. Ask for a 60-second summary. Ask which threshold decision needs you. Then say out loud that the commander still has command. If command, cadence and authority all hold, you have nothing to add by staying.
Pressure does not eliminate authority. It redistributes it.
Source: Google SRE, "Managing Incidents," sre.google/sre-book/managing-incidents.