A decision making bottleneck does not look like a problem at first. It looks like a full calendar and a useful day. Questions come to you because you have the answers, and answering them feels like leadership. But when every important call travels to the most senior person in the room, the company can still decide well while never building the ability to decide without you. That difference is the whole job.

Your real job is to build better decision makers
Culture / September 2026 / Bill Dickenson

The decision making bottleneck starts with feeling useful

We have watched capable owners answer every question brought to them and quietly teach their people to stop thinking. Nobody sets out to do that. The pattern builds slowly, because the fastest route through any single question is to answer it yourself. You know the customer, you know the margin, and you know what went wrong the last time. So you decide, and the job keeps moving.

Then a few years pass, and the team has learned one rule: bring it to him. A decision making bottleneck gets built one reasonable answer at a time. Being needed and being effective are not the same thing, which is the uncomfortable distinction behind Level 5 leadership.

Why judgment is the skill that compounds

Every leadership competency eventually surfaces as a decision. Strategy is a decision about where not to play. Culture is the sum of what an owner permits and refuses. So when judgment lives in one head, the business moves at the speed of one calendar.

The cost is measurable. In a McKinsey global survey, only about one in five respondents said their organizations excel at decision making, and roughly 61 percent said most of their decision-making time is used ineffectively. Growth makes it worse rather than better, which is the same failure we describe when scaling a business exposes weak processes.

There is one honest test. Look at what your team decided while you were unreachable last quarter. If the work waited, the capability is not there yet.

Four conditions that let judgment spread

People cannot decide well without context. A project manager who knows only the deadline and the budget can hit both and still make the wrong call, because nobody told him the customer is a repeat account with three more buildings coming. Send the reasoning with the work, not just the number.

Principles beat approvals. A good principle captures judgment that would otherwise stay trapped in your head, and it settles dozens of decisions you never hear about. “We absorb a change order under five hundred dollars when the mistake was ours” is a principle. It tells a foreman what to do at seven in the morning without calling you.

Decision rights need real boundaries. Your people should know which calls they own outright, which ones require alignment with someone else, and which genuinely belong to you. Bain built an entire decision-rights model, RAPID, around that single idea, though a whiteboard and an honest conversation work fine at your size.

Feedback closes the loop. Judgment improves only when people connect a decision to what followed it, so tell them how the call turned out. That habit is where company accountability actually starts.

The fifth condition: knowing the decision was yours

We add a fifth from our own practice, because four are not enough in a small company. People need clarity about the five key responsibility areas of their role. Most escalation happens for a quiet reason: the person was unsure the decision was ever theirs to make.

That is rarely a nerve problem. A service manager who believes pricing belongs to the owner will route every pricing question upstairs, even when she has better information than you do. Write down what the role owns, and half the traffic stops.

Role clarity also changes who you hire next. When the five areas are written down, you can interview against them instead of against a feeling, and a new manager knows on day one which calls are hers. That is a smaller version of the same discipline we use when helping owners hire qualified employees.

Coaching is how a decision making bottleneck actually breaks

This is where coaching stops being soft and becomes operational. The discipline is simple to describe and hard to practice: resist the answer long enough to ask the question. Four of them do most of the work.

• What evidence separates your two options?
• What assumption is doing the heaviest lifting in your recommendation?
• Which of these risks is reversible, and which one is not?
• What would you decide if I were unreachable this week?

Those questions do more than slow the moment down. They tell you whether you are facing a capability gap, a context gap, or a confidence gap. Those are three different problems, and handing over your answer solves one of them while making the other two worse. The point is never to withhold expertise. Spend it so that it leaves more judgment behind than you found, which is the practical core of leadership effectiveness.

How to break the decision making bottleneck this quarter

Take one decision that has been escalated to you more than once. Stop asking how to handle it faster next time. Ask instead what context, what principle, or what boundary would let your team make the next version of it well without you. Write that down and give it away.

This is Culture Intelligence work, and it compounds quietly. Confidence comes first and competence follows, while credibility is what your people earn when the decision holds and everyone knows it was theirs. The writer Darren Smith puts the trap plainly: your job is to create better decision makers. Clearing a decision making bottleneck is how that job actually gets done.