Did You Accidentally Become the Bottleneck... or Did You Design It?

I've been asking myself the same question for years. I've seen some version of it in service businesses with 10 employees, in organizations with hundreds, in nonprofits, consulting clients, and family businesses.

The details change. The pattern doesn't: everything ends up back on one person's desk.

Wine tasting gone awry

A few years ago, I was on a wine tasting trip with friends, one of whom is a business owner. It was supposed to be a day off. Instead, their phone rang every fifteen or twenty minutes.

"Can we approve this invoice?"

"What should we charge this customer?"

"Can we move this job to Friday?"

"Should we order more materials?"

None of those questions were emergencies. None of them justified interrupting a Saturday afternoon.

Every call ended the same way: the owner answered, grew frustrated, solved an “issue”, hung up, and slowly tried to go back to enjoying the afternoon, until the phone rang again.

Watching it happen, I kept thinking: did this business become dependent on him, or was it designed that way? Not necessarily on purpose. Was he not “delegating” right?

Whenever this comes up, the advice is usually the same: delegate more, empower your team, trust your people. None of that's wrong. It just doesn't get at the root of it.

Delegation isn't just handing off work. People make good decisions when they know what decisions are theirs, what success looks like, and where the guardrails are. Without that, asking you is the safest option. Honestly, I'd probably do the same thing.

Unintended Codependency

One thing I wonder about: Do some business owners tie part of their identity to being needed? I don't think anyone starts a business hoping to spend years answering questions about invoices and scheduling. But I've watched this pattern enough times to think some leaders get so used to having all the answers that they don't notice they're enabling some co-dependency.

If every important decision runs through you, you feel important. You feel valuable. You feel indispensable. Until you can't take a weekend off without your phone ringing every twenty minutes.

I've watched owners complain that everyone keeps asking them questions. I've also watched those same owners do very little to change the system that created those questions. That's the part I find interesting.

Maybe we're fixing the wrong thing

I hear owners often say they wish employees would take more ownership. I think that's the wrong place to start. Instead of asking why employees aren't taking ownership, get curious about the quality of questions they're actually asking.

Most sound like this:

"Can I approve this invoice?"

"Should I call this customer?"

"Can we order this?"

Those are permission questions.

The ones that matter sound more like:

"What problem are we actually trying to solve?"

"Why does this process create so much rework?"

"Why are we paying for software but still doing this by hand?"

"Why do we keep making exceptions for customers who negotiate every price and question every invoice?"

Those are improvement questions. That's the difference between waiting for direction and thinking like an owner. And that doesn’t mean business owner. Realistically, no one is going to care about your business like you do. But you can have process owners, system owners, experience owners.

One of the biggest mistakes I see

One mistake I see a lot: assuming that because someone asks a question, they can't make the decision.

I don't think that's usually what's happening. More often, they're trying to find the boundary because no one's ever defined it.

People aren't mind readers. If you've never explained what decisions they own, never set what "good" looks like, if every customer becomes a special exception, if every mistake gets second-guessed because it wasn't handled exactly your way, why would anyone risk deciding on their own?

Asking you is the safest option they have.

Over time, people stop wanting to feel unsafe. They stop bringing you ideas. They stop challenging inefficient processes. They stop questioning why things are done a certain way. They ask permission because the business taught them that's how decisions get made.

Not every decision carries the same risk

One objection I hear a lot: "I can't let employees make those decisions, they'll get it wrong." Maybe. But not every decision carries the same weight.

What's the worst that happens if someone approves a small discount they shouldn't have? Orders the wrong supply once? Handles a customer conversation differently than you would have? Those can be coaching moments instead of reasons to take decision-making away entirely.

Employees shouldn't make every decision. The better question: which decisions actually need you, and which just need clearer guidelines?

Clear standards. Clear authority. Clear decision rights. Those are systems, and systems scale.

Teach people how to think

One idea has followed me through my career, whether I was coaching executives, running ERP implementations, or helping organizations redesign how they work: tell people what outcome they own, be clear on the standards, be clear on the boundaries, then give them room to use judgment.

They won't always decide the way you would. That's fine. The goal is a business that runs without you standing in the middle of every decision.

One question I'd leave you with

Next time someone interrupts you with a question, don't answer it right away. Ask yourself why it made it all the way to you.

Was the expectation unclear? Was the process undocumented? Was the authority never defined? Or did you unintentionally become the system?

I don't think most owners are bottlenecks because they can't delegate. I think they never designed how decisions get made in the first place.

That's fixable. Systems can be redesigned. People can learn. The business doesn't have to depend on you forever.