The Invisible Bottleneck: Why Approval Authority Concentrates at the Top Without Anyone Deciding to Put It There

Most senior leaders believe they have distributed authority throughout their organizations. They have signed off on job descriptions that include decision rights. They have told direct reports to own their domains. They have, at some point, explicitly said the words "I trust you to handle it." Yet in practice, a striking volume of decisions continues to arrive at the director, VP, or C-suite level without anyone consciously routing them there.

This is not a failure of delegation intent. It is a failure of system design, and it compounds quietly until leaders notice they are spending the majority of their week resolving questions that, by any reasonable logic, should never have reached them.

How Centralization Happens Without a Decision

Authority does not concentrate at the top because senior leaders refuse to let go of it, though that does occur. More commonly, it concentrates because the organization never built the infrastructure that would allow decisions to close anywhere else.

Consider what a mid-level manager actually needs to finalize a meaningful decision without escalating. They need clear parameters for what falls within their authority versus what does not. They need access to the relevant context, data, and cross-functional input. They need confidence that a decision they make will not be quietly reversed by someone above them after the fact. And they need a track record of making similar decisions that was met with something other than correction.

When any of those four conditions is absent, escalation becomes the rational choice. It is not laziness or lack of confidence. It is a reasonable response to an environment where the cost of an unsanctioned decision is high and the cost of asking upward is low. Organizations that unintentionally reward escalation, even through the simple act of responding quickly and helpfully when questions arrive, train their people that routing decisions upward is safe and appropriate.

Over time, this pattern normalizes. Leaders who initially expected questions to taper off find that the volume holds steady or grows. New hires learn the escalation habit by watching how their peers and predecessors behaved. The org chart says authority exists at multiple levels; the actual decision flow tells a different story.

What the Pattern Costs

The most visible cost is senior leader bandwidth. When directors and above are resolving decisions that belong two or three levels down, they are not doing the work that justifies their position: setting direction, managing risk at the appropriate altitude, building organizational capability, and thinking beyond the current quarter. Their time is finite. Every hour spent approving a vendor choice or clarifying a policy interpretation is an hour unavailable for the work only they can do.

The less visible cost falls on the people below. When managers learn that decisions will eventually be resolved above them, they stop developing the judgment that comes from living with the consequences of their own choices. The organization ends up with capable people who are experienced at gathering information and presenting options but are genuinely underprepared to finalize and own outcomes. When those people are eventually promoted, the gap between their title and their decision-making capacity becomes a problem.

There is also an organizational speed cost. Decisions that should close in a day wait for calendar access to a senior leader. Projects stall not because of resource constraints but because a required input cannot be secured without a meeting that has not been scheduled yet. The organization experiences this as slowness without identifying where the drag originates.

Diagnosing Before Redesigning

Before attempting to redistribute authority, it is worth understanding precisely where decisions are actually landing versus where the organization believes they should land. A useful diagnostic is straightforward: ask a representative sample of managers across levels to log, for two or three weeks, every decision they either made independently or escalated, along with a brief note on why they chose to escalate when they did.

The patterns that emerge are frequently surprising. Organizations often discover that escalation clusters around specific topics, not because those topics are genuinely complex, but because a past decision in that area was reversed and no one has felt safe since. They discover that certain leaders have become default approval nodes not by organizational design but by reputation for responsiveness. They discover that ambiguous role boundaries cause escalation at the intersection points between functions, where no one is confident they have jurisdiction.

This diagnostic is more useful than asking leaders whether they think their teams have sufficient authority. The perception at the top is almost always that authority has been granted. The experience at the operating level is almost always more constrained than the top believes.

Rebuilding the Conditions for Distributed Decisions

Once the actual escalation pattern is visible, redesign becomes more targeted than a general push to "empower teams."

The first intervention is clarifying decision parameters explicitly rather than inferring them from job levels. This means specifying, by decision type, what a manager can authorize independently, what requires notification after the fact, and what genuinely requires prior approval. General language like "significant financial decisions" creates the ambiguity that produces escalation. Specific thresholds and defined categories reduce it.

The second intervention is separating reversals from feedback. When senior leaders override decisions that were within a manager's authority, they should make the distinction clear: this was reversed because the authority boundary was misunderstood, or this was reversed because I chose to exercise a prerogative I hold, not because your judgment was wrong. Conflating these signals teaches managers that their authority is nominal.

The third intervention is building explicit track records. Managers develop decision confidence through repetition and feedback, not through being told they are trusted. Creating low-stakes opportunities for managers to make real decisions, receive honest assessments, and observe that their choices hold is how judgment develops at scale. Organizations that bypass this step and simply announce that authority has been redistributed typically see escalation volumes unchanged within months.

The Senior Leader's Role After Redistribution

Perhaps the most counterintuitive aspect of reducing decision centralization is that it requires more discipline from senior leaders, not less involvement. The temptation when a subordinate's decision seems suboptimal is to intervene. Each intervention, however well-intentioned, signals that the distributed authority was conditional. Maintaining credible restraint, limiting senior leader involvement to genuinely strategic decisions and pre-defined exception categories, is the behavior that makes redistribution durable.

Organizations that do this well find that their senior leaders become significantly more effective, not because they worked harder or hired better people, but because they stopped absorbing work that belonged elsewhere. The decisions that required senior attention received it fully. The decisions that did not stopped arriving.