A director makes the call at 11 pm to hold a customer's release. By 9 am, a VP has reversed the decision. Nobody says anything. Next time, the director will wait for the VP to make the final decision.
You cannot blame people for waiting when the organization has trained everyone that complex decisions move upward.
This week comes last for a reason. The first four moves changed a process. This step changes what the process has been teaching.
Your team is reading the evidence. If the last four hard calls made under pressure got revisited, softened, or quietly reversed, they learned something true about how this place works. Nobody meant to teach that. It got taught anyway.
Waiting is the rational move in a system that overturns the people who move.
I watched this for a decade on the escalation floor. Every time, I saw capable people reading their own history correctly.
We inspect the system before we blame the person. The system includes what happens after somebody decides.
One reversal done in the open teaches something different from one done quietly.
Where these five weeks stop.
You can take these five moves alone, and they are worth taking. They still live in one head. Command, cadence, and authority fit in a four-second checklist, but a checklist in your head does nothing for your team while you are on a plane.
If you decide to build something that runs without you, whether that is software, a process, a workshop, or a hire, check four things first:
- Can someone use it in the middle of an escalation?
- Does it name one owner for each decision?
- Will your team practice it before a real customer tests it?
- Will you measure the load before you start, so you can see if it moved?
If any answer is no, the load stays with you.
You stop being the system. You become the executive who built one.
Take the free Authority Leak Scorecard. Ten minutes, and it shows where authority is leaking and how much of your escalation load sits with you.