A supervisor gets a question about a missed shift swap. Unsure how to answer, she forwards it to her manager. The manager, wanting cover, loops in a director. The director, unsure whether there is a policy implication, adds an executive. Within the hour, four people who were nowhere near the original question are discussing a shift swap the supervisor could have resolved in the same conversation — if she had known she was allowed to.

Run the tape the other way and the failure looks different but costs the same. A recurring billing error quietly overcharges a small amount every month. The person who notices it does not want to “bother leadership” with something so small. Months later, the small amount has become a material one, and leadership hears about it for the first time as a number nobody expected.

Neither organization has a discipline problem. Both have a governance problem: nobody defined, in advance, what belongs at which level. When escalation rules are unclear, organizations compensate with either too much upward communication or too little. Both are governance failures, and both are fixable with the same design work.

Escalation Exists Because Authority Is Bounded

No role in a well-run organization holds unlimited authority, and that is by design, not by accident. A frontline role can typically resolve a routine complaint, a minor scheduling problem, or a small deviation from standard process without asking anyone. A manager can usually absorb a larger financial threshold, a staffing tradeoff, or a disagreement between two teams. Senior leadership exists to hold what neither level should: material risk, policy change, strategic commitment, the exception that sets a precedent. The point is not hierarchy for its own sake. It is alignment between the authority a role holds, the consequence a decision can produce, and who is ultimately accountable for the outcome.

Escalation begins where legitimate local authority ends.

Over-Escalation Weakens the Organization

Sending everything upward can look like caution. It is usually something else — unclear decision rights, fear of being blamed for a bad call, thin training, or an approval culture that has quietly replaced trust with process. The cost compounds. Leaders spend their attention on decisions that never needed them. Staff stop exercising the judgment they were hired to use, because using it has rarely been rewarded and second-guessing it always has. Decisions slow down, and ownership becomes something people perform rather than hold.

A system that escalates everything is not necessarily well governed. It may simply be under-delegated.

Under-Escalation Hides Risk

The opposite failure is quieter and, over time, more expensive. Local ownership is not the same as isolation. An issue should move upward when it exceeds the current level’s authority, when it touches legal or ethical exposure, when a customer commitment may materially change, when safety or privacy is at stake, or when a pattern of failure suggests the problem is structural rather than incidental.

Good local ownership includes knowing when the issue is no longer local.

Build Escalation Around Consequence, Not Emotion

Issues get escalated for reasons that feel urgent in the moment — irritation, political sensitivity, personal discomfort — and none of those reasons are the same as organizational consequence. A more reliable test asks about financial impact, operational disruption, customer impact, policy conflict, safety, reputation, legal or ethical risk, whether an authority boundary has been crossed, and whether the issue has happened before.

Emotional intensity and organizational consequence are not the same thing.

Repetition Changes the Escalation Decision

One missed deadline, one customer complaint, one manual workaround can usually stay local. The fifth occurrence of the same thing is a different question. A pattern that repeats has stopped being an isolated event and started describing a structural weakness — whether the workaround belongs to a person or, increasingly, to an automated process quietly making the same exception every time.

Frequency can turn a local issue into a governance issue.

Escalation Should Carry a Decision Request

Vague upward communication wastes the escalation it uses. “Just so you know this happened” asks nothing of the person receiving it. A usable escalation states what happened, why it matters, what has already been tried, why the current level cannot resolve it, and what decision is actually needed. That last element is the one most often missing, and its absence is why so many escalated issues sit unresolved — nobody stated what decision would close the loop.

Escalation should transfer a decision, not merely transfer anxiety.

The Escalation Ladder

Roe & Associates uses a four-level ladder to keep this decision consistent rather than situational, whatever the size of the organization running it.

Do Not Confuse Consultation With Permission

A subtler failure hides inside organizations that believe they have already delegated authority. Employees ask, “What do you think?” when what they actually mean is, “Will you approve this?” Consultation means seeking insight while retaining the decision. Approval means another role holds the decision rights. Escalation means the issue has crossed a defined authority boundary and the decision has genuinely moved.

If people must seek permission for decisions they supposedly own, authority has not actually been delegated.

Leaders Must Stop Pulling Decisions Upward

Delegated authority can be undermined without a single policy changing. It happens when a leader second-guesses a decision after the fact, intervenes before the owner has finished working the problem, reacts personally to a complaint addressed to someone else, or makes an exception without involving the person who was supposed to own it. None of this looks like a takeover. It looks like helping. But every time leadership rescues a decision that belongs lower in the system, it teaches the system where the real authority lives — and the lesson is learned quickly. Sometimes the right response from a leader is simply: “You own that decision. Use the standard, and let me know the result.”

Exceptions Need Escalation Thresholds Too

Exception paths need the same discipline. A club treasurer approving a small variance in an event budget, a volunteer coordinator waiving a late-registration fee, a consultant adjusting a project scope by a day — none of this needs board-level review. Larger exceptions do. Defining which exceptions a role can approve alone, which need a manager’s signoff, and which require executive or board-level review prevents two failures at once: the bottleneck of routing everything to the top, and the quiet workaround of nobody routing anything at all.

A governed exception path includes not only who may approve the exception, but how far upward the decision actually needs to travel.

AI Escalation Should Fit the Same Governance Model

The same logic applies to automated workflows that flag their own uncertainty, the subject of Day 4 this week. When a system cannot resolve a case with confidence, the question is not only whether to send it to a person — it is which person, using which existing decision structure. Does every ambiguous case need senior leadership, or can trained staff resolve the routine exceptions the way they already do for cases a person flagged?

AI should escalate into the organization’s real decision structure, not create a parallel one.

Return to the shift-swap question. An organization should not need four people to answer something the first person could have resolved in the same conversation. Neither should a treasurer quietly absorb a growing loss because raising it felt like an overreaction. The goal is neither maximum escalation nor maximum autonomy. The goal is proportionate authority with clear thresholds.

Mature systems keep decisions as close to the work as responsibility allows, and move them upward only when consequence, authority, or risk genuinely requires it.

A mature system does not ask, “Who else should know?” first. It asks, “Who actually has the authority required to resolve this?”

Escalation Threshold Audit

Choose one recurring issue that frequently moves upward and answer:

Strategic Reframe

• Instead of “Better safe than sorry — send it up,” ask: “What actual threshold has been crossed?”
• Instead of “I want leadership to know,” ask: “Does leadership need awareness, consultation, or a decision?”
• Instead of “They should ask before deciding,” ask: “Did we actually delegate authority?”
• Instead of “This keeps coming up,” ask: “Has repetition turned this into a structural issue?”
• Instead of “The AI escalated it,” ask: “Where should this type of uncertainty enter our existing decision structure?”