How to Enforce Escalation Discipline
Escalation discipline decides where decisions live. Done well, it keeps the organization fast by holding decisions at the lowest capable level and keeps trust high by handling what does rise quickly and predictably. Done badly, every hard call drifts upward and the COO's calendar becomes the company's constraint.
Developing
Start here. Build the foundation.- 1
Write the escalation list with your directs in the room: spend above a threshold, cross-functional conflict, new precedent, defined risk classes. Publish it where anyone can read it. You know it landed when a report cites the criteria to justify not bringing you something.
- 2
When an item shows up that belongs below you, hand it back the same day with one sentence: who decides, and that you back their call. The urge to just handle it is the test. Expect volume to rise briefly when criteria first publish, as hidden decisions surface; that is the system working. It is working when the same person stops re-escalating the same class of decision.
Proficient
Build consistency and rhythm.- 3
Give legitimate escalations a published service level, such as decided before the next operating review, and track it. When you cannot decide in time, route it or say what is missing. The signal: people keep escalating the right things instead of going around you.
- 4
Quarterly, list what reached you and sort by source. Where one area over-escalates, go find the cause: unclear rights, missing capability, or fear, and fix that. You are done with a source when its volume drops without being told to stop escalating.
Mastered
Operate at the highest level.- 5
Help each of your leaders write and publish their own criteria with their teams, and review how the tiers connect. The proof is structural: decisions stop skipping levels, and the discipline holds in parts of the organization you rarely visit. Mastery is when the discipline is the organization's, not yours.
Common Pitfalls
Avoid the common failure modes.- Absorbing misdirected decisions because solving them is faster than teaching the routing. Every one you quietly handle trains the organization to send the next.
- Criteria that exist but are not published, so escalation still follows fear and relationships instead of rules anyone can read.
- Punishing a legitimate escalation once. It quietly ends escalation and starts workarounds, and you will not hear about the next problem until it is expensive.