Decision-Making Bottlenecks: Why Everything Goes to the Top

Research found that only 20% of respondents believed their organizations were good at decision-making. A majority also said much of the time spent making decisions was used ineffectively.

It would be easy to blame bureaucracy or overly cautious leadership. But there is another explanation that is less obvious:

Organizations teach people where decisions belong through everyday habits.

It can start innocently enough.

A supervisor encounters something unusual and asks a manager what they think. The manager gives an answer. A department leader wants another perspective and calls a director. An operational issue reaches an executive who has seen it before, so the executive steps in, makes the call, and keeps the work moving.

Nothing about those interactions looks dysfunctional. In the moment, they are helpful.

The problem appears when the exception becomes the pattern.

The next time something similar happens, the supervisor remembers who made the decision last time. The manager remembers what the director wanted to see. The department leader knows the executive has an opinion on the subject.

Nobody changed a policy. Nobody rewrote an approval process.

But the organization learned where that decision goes.

The Approval Structure You Won't Find on the Org Chart

Most organizations have a formal authority structure.

They also have an informal one.

I think of this as the shadow approval structure.

The formal structure tells you who manages the work. The shadow structure tells you who people believe they need permission from before the work can move.

The two can look surprisingly different.

A manager may be responsible for a department but routinely seek a director's approval before changing priorities.

A project leader may own a deadline but need several people to agree before reallocating the resources required to meet it.

An operations leader may be accountable for an outcome while meaningful operating decisions continue to move above the role.

This is where organizations can unintentionally separate responsibility from authority.

Giving someone responsibility for an outcome does not necessarily give them the authority to make the decisions required to produce it.

When those two things are separated, what looks like ownership on the organizational chart can function more like dependency in practice.

And dependency tends to travel upward.

Not Every Decision Should Travel the Same Route

Research on organizational decision-making shows that different types of decisions require different approaches.

That sounds obvious. In practice, organizations don't always operate that way.

A major capital commitment should not follow the same decision path as a routine scheduling adjustment. A decision affecting several business units may reasonably require broader input. A recurring operational decision may be better made closer to the work.

The mistake is treating all involvement as approval.

There is a difference between the person who recommends a decision, the people whose expertise should inform it, the person with authority to make the final call, and the people responsible for carrying it out.

As organizations grow, those distinctions matter more.

Being involved in a decision is not the same as owning the decision.

A leader may need to know about something without approving it.

Finance may need to provide input without having the final call.

Operations may need to consult another department without creating a requirement for consensus.

When those distinctions aren't clear, consultation has a tendency to become approval.

Another name gets added to the email.

Another person gets invited to the meeting.

Another review gets inserted into the workflow.

Nobody sat down and intentionally designed a more complicated decision process.

It accumulated.

Decision-Making Bottlenecks Grow With the Organization

Informal decision-making can work extremely well in a small organization.

When there are 25 employees, a founder or senior leader may know nearly every customer, project, manager, and operational issue. Walking into someone's office and getting an answer may take five minutes.

The same habit becomes much more expensive at 100 or 500 employees.

There are now more customers, managers, projects, exceptions, and decisions, but many of those decisions may still be traveling through the same handful of people.

At that point, the leader hasn't necessarily become slower.

The queue in front of the leader has become longer.

That's an important distinction.

An organization can add employees, managers, technology, and production capacity while leaving its decision capacity largely unchanged. That is how decision-making bottlenecks form. If more work continues to generate more decisions for the same people, growth increases pressure on the same handful of leaders.

Eventually, leadership availability becomes part of the organization's cycle time.

A decision waits until Tuesday because the director is traveling Monday.

A project waits until the weekly meeting because that's when everyone who “needs to weigh in” will be together.

An operational change waits because nobody is quite sure whether the manager has the authority to make it.

Individually, none of those delays may look significant.

Collectively, they determine how quickly the organization can move.

Follow the Decisions That Keep Coming Back

If you want to understand the real decision structure of an organization, stop looking at the org chart for a moment.

Follow the decisions.

Which questions keep returning to the same leader?

Which approvals routinely require the same names?

Where do people say, “I just want to run this by you” before proceeding?

Which meetings exist largely because nobody is certain who has the final call?

What stops moving when one particular person is unavailable?

Those patterns tell you where authority actually lives.

They can also reveal something leaders may not recognize about their own role in the system.

When a leader repeatedly answers a question that could have been resolved elsewhere, they aren't only solving today's problem. They are also teaching the organization what to do the next time that problem appears.

People learn what gets rewarded.

They also learn what feels safe.

If escalation consistently produces an answer while independent judgment carries uncertainty, escalation becomes a rational response.

That doesn't necessarily mean people are unwilling to take ownership.

It may mean the organization has never made the boundaries of their authority clear.

The Issue Isn't How Many Decisions Leaders Make

Senior leaders should make consequential decisions. That's part of the job.

The better question is whether their attention is being used on decisions that actually require their level of judgment.

Strategic decisions need appropriate senior leadership involvement.

Cross-functional decisions need clarity about who contributes and who ultimately decides.

Routine operating decisions need owners who understand where their authority begins and ends.

Without those distinctions, organizations create approval structures they never consciously designed.

Eventually, a leader looks at an inbox full of questions, a calendar crowded with meetings, or another issue waiting for their response and asks:

“Why am I involved in this?”

That's a useful question.

But there is a better one:

“How did the organization learn that this decision belonged to me?”