In many businesses, the answer is technically documented. Employees have titles, responsibilities and procedures. Yet when something falls outside the normal routine — even slightly — the decision travels upward.
A client asks for something unusual. A deadline is at risk. Two priorities conflict. An employee encounters a situation that is not covered perfectly by the procedure.
Instead of making a decision, the team asks the managing partner, executive director or another senior leader.
One question is harmless. Hundreds of small questions create an operating model built around escalation.
That creates an immediate efficiency problem, but it also exposes something more important: The organization may not be as prepared for leadership transition or disruption as it appears.
The Escalation Test
One way to identify this problem is to examine the decisions that repeatedly reach senior leadership.
For each one, ask three questions:
1. Does this decision genuinely require senior authority?
Some decisions should remain with leadership. Significant financial commitments, legal exposure, major personnel matters and strategic changes deserve escalation. But many operational questions do not.
2. Could someone closer to the work make the decision with clear boundaries?
Employees often escalate because they do not know where their authority ends. The solution is not simply telling people to “take ownership.” They need to know what they own.
3. What information would allow them to decide confidently?
Sometimes the missing piece is a procedure. Other times it is a spending threshold, priority rule, training gap or clearly identified decision owner. These questions separate necessary oversight from habitual escalation.
Build Decision Lanes, Not Bigger Procedure Manuals
The instinctive response to recurring questions is often to write another SOP. SOPs are valuable when work should happen consistently. They are less effective when employees must exercise judgment.
Instead, define decision lanes.
A useful decision lane answers four things:
- Who owns the decision?
- What can that person decide without approval?
- What conditions require escalation?
- Who is the backup decision-maker?
In a law firm, for example, a client-service issue might not need to reach the executive director every time. A department manager could be authorized to resolve routine scheduling, staffing or service-recovery questions within defined boundaries, while matters involving unusual cost, legal risk or a significant client relationship still escalate.
The specific boundaries will vary by firm, but the principle is the same: Employees should not have to guess whether they can act. Clear authority lets routine work continue while preserving leadership oversight where it actually matters.
Consider a routine vendor issue. Rather than requiring leadership approval whenever something goes wrong, the organization might authorize a manager to resolve the issue within a defined financial or operational threshold. Escalation occurs only when the situation exceeds that boundary.
The organization has not removed control. It has made control clearer.
Watch for the Shadow Approval Process
Formal procedures are only part of the operating system.
Organizations also develop unofficial rules: “Check with her first.” “He likes to approve those.” “Send that one upstairs just to be safe.”
These habits create a shadow approval process that may never appear in an organizational chart or SOP.
They are also easy to miss during succession planning.
A successor can inherit documented responsibilities and still discover that dozens of everyday decisions depended on one person's unwritten preferences.
Employees should not have to guess whether they can act. Clear authority lets routine work continue while preserving leadership oversight where it actually matters.
To uncover those dependencies, ask employees a revealing question: What do you regularly wait for leadership to answer before you can continue working?
The responses provide a practical map of leadership dependence.
Decision Ownership Is a Continuity Issue
Succession planning often focuses appropriately on leadership roles, client relationships, financial authority and institutional knowledge.
Operational decision-making deserves the same attention.
If a key leader were unexpectedly unavailable for two weeks, which decisions would stop moving?
Which employees would know what to do? Which would wait? Which decisions would bounce between departments because nobody was certain who owned them?
Those questions turn succession planning from a future leadership exercise into a test of present-day business continuity.
The goal is not to eliminate escalation. Healthy organizations escalate important exceptions quickly.
The goal is to eliminate unnecessary escalation created by unclear ownership.
Start with the decisions that repeatedly reach senior leadership. Identify which ones truly belong there. Move appropriate decisions closer to the people doing the work, define their boundaries and document when escalation is actually required.
That reduces everyday friction now.
More importantly, it creates an organization that can continue making good decisions even when a familiar decision-maker is not in the room.


