There is a particular kind of manager who is always busy and always behind. Every decision routes through them. Every proposal waits for their review. Every customer escalation lands on their desk because nobody below them is quite sure what they’re allowed to approve. From the outside it looks like dedication. From the inside, it’s a traffic jam with one lane open.
I’ve watched this pattern show up in sales floors, call centers and operating companies of very different sizes, and the cause is almost never laziness or incompetence. It’s the opposite. The bottleneck is usually the hardest-working person in the building. That’s what makes it so hard to fix.
The bottleneck is almost always a promotion problem
Most managers get promoted because they were excellent at doing the work. The best closer becomes the sales manager. The most reliable supervisor becomes the operations lead. Nobody hands them a new job description that says: your output is no longer your output, it’s your team’s output. So they keep doing what earned them the role, and they add oversight on top of it.
Running a business teaches you that this is a math problem before it’s a character problem. One person can review a certain number of decisions per day. Once the volume of decisions exceeds that number, the queue grows every single day no matter how many hours that person works. You cannot out-hustle arithmetic. Numbers matter here more than intentions.
In my experience, the warning signs are consistent. Work sits waiting for approval. Good people stop proposing ideas because the response time makes it pointless. Your calendar is full of meetings where you’re the only one who can answer the question. And the tell that’s hardest to admit: when you take a week off, things don’t get worse — they stop.
The Garrett O’Rourke leadership view: delegation is not distribution
A lot of managers think they delegate. What they actually do is distribute tasks. There’s a real difference. Distributing a task means someone else executes your decision. Delegating means someone else makes the decision, and you live with it.
That second version is uncomfortable, and I understand why. When you’re responsible for a team, you’re responsible for the results regardless of who touched the work. Handing over a decision feels like handing over your reputation. But the alternative is a business where judgment only exists in one head, and that business can’t grow past the size of that head.
My background runs through sales, business development and call-center ownership and operations, and as President of Commercial Development Group I’ve spent a lot of time on the operational side of growth. Call centers make this lesson unavoidable. You have a floor full of people having live conversations with customers in real time. You cannot supervise every call. What you can do is decide in advance what good looks like, train against it, measure it, and then let people work. That is a very different management posture than approving things one at a time.
Ownership is what makes delegation safe
The reason delegation fails is rarely the person receiving it. It’s that they received a task without receiving ownership. Ownership means four things are clear:
- The outcome. Not the activity. Not “make calls” — what result are we actually after, and by when.
- The boundaries. What can this person decide alone, what requires a conversation, and what genuinely needs to come to me. If you don’t define this, people default to asking about everything, which puts you right back in the bottleneck.
- The measure. How we’ll both know whether it worked, agreed on before the work starts rather than debated afterward.
- The consequence. Good or bad, this person’s name is on it. That’s not a threat. That’s what makes the work worth doing.
One thing I’ve learned is that people are far more willing to be held accountable than managers assume — as long as the expectations were clear at the start. Almost every accountability conversation that goes badly goes badly because the standard was invented after the fact. If the target moves once someone has already missed it, you haven’t held them accountable. You’ve just told them their effort doesn’t correlate with the outcome, and you’ve taught them to wait for instructions next time.
Practical ways to get out of the way
None of this is theoretical. A few things that work:
- Audit your inbox for a week. Sort what came to you into three piles: things only you could decide, things someone else could have decided with a bit of context, and things someone else should already be deciding. The second pile is your training plan. The third pile is your problem, not theirs.
- Delegate the decision, not just the execution. Instead of telling someone what to do, ask what they’d do and why. If the reasoning is sound, let it run even when you’d have chosen differently. Judgment is built by using it.
- Set a dollar or risk threshold. Anything under a defined threshold, they decide and tell you afterward. Over it, you talk first. This single rule removes an enormous volume of unnecessary approvals.
- Replace status meetings with standards. If you need a meeting to know how things are going, your reporting is broken. Fix the measurement and the meeting gets shorter.
- Let people be wrong at a survivable scale. Nobody develops judgment in a job where every mistake is prevented. Pick the mistakes you can absorb and let those happen on purpose.
- Give credit publicly and correct privately. If you take the credit for delegated work, you’ll only ever get compliance back, never ownership.
Where leaders get this wrong in both directions
The bottleneck manager is one failure mode. The other is the manager who hears “delegate more” and simply disappears — hands off the work, skips the standards, skips the follow-up, and calls the resulting mess empowerment. That isn’t delegation either. That’s abdication with better vocabulary.
The distinction is accountability. Real delegation keeps the leader on the hook. You gave someone the decision, so the outcome is still yours to answer for. That’s the deal. If it goes wrong, the useful question isn’t who to blame — it’s whether the expectation was clear, whether the training was adequate, and whether the person had the authority to actually fix the problem when they saw it coming. Usually one of those three was missing.
As an investor, I think about this the same way I think about evaluating a business from the outside. Patience and disciplined evaluation matter, and one of the things I look at is whether an operation depends on a single person’s constant intervention. A business that only works when one individual is in the room is carrying a risk that doesn’t show up cleanly on any statement. Durable operations have judgment distributed through them. (That’s a personal perspective on how I read businesses, not individualized financial advice.)
The broader principle
Over the years, the thing I keep coming back to is that leadership is mostly about building capacity in other people, and capacity is built by giving away real decisions with real consequences attached. Experience matters, but experience that stays locked inside one manager’s head isn’t an asset to the business — it’s a dependency.
The honest test is simple. If you stepped away for two weeks, what would stop? Whatever answer comes to mind first is your next delegation project. Not because you’re replaceable, but because the point of leading is to make sure the work doesn’t need you standing over it to get done well.
Photo by Christina @ wocintechchat.com M on Unsplash