Are You Leading Your Team or Being Its Bottleneck?

Most hospitality founders would not describe themselves as bottlenecks.

They'd describe themselves as hands on. Involved. Present. Standard bearers. All of which sound like virtues. All of which the industry celebrates as evidence of a founder who really cares about their business.

But if everything in your business has to pass through you before it can happen, the pattern is the pattern regardless of what you call it.

And the reason it matters isn't that it slows things down, although it does. The reason it matters is that a bottleneck shapes the team around it. Over time it produces exactly the team the founder is often complaining about. The one that can't be trusted to make decisions. The one that always brings everything back to the founder.

That team wasn't born that way. It was made that way. By the founder.

The Bottleneck Nobody Sees

What makes the bottleneck pattern almost impossible to see from the inside is that it looks like virtue.

You're the person who fixes things. You're the person the team comes to. You're the person who knows what needs to happen. All of that feels like leadership. It looks like leadership. It gets celebrated as leadership.

But if it's become the way the business actually runs, if every question and decision and operational hiccup ends up on your plate, then something has quietly shifted. You're not leading the team. You're carrying it.

For far too long at Ojo Rojo I was the person who came in to fix the wifi. The card machines. Anything that broke. My team knew that if something went wrong, they called me. It felt efficient. What I didn't see was that they never learned how to handle any of it themselves because I was always the answer.

I only shifted it when I decided, deliberately, to stop being the answer. I showed them how. I made them do it once with me. Then twice on their own with me on the phone. Then on their own. Within a few weeks, the wifi and the card machine problems stopped touching me.

The Rota Realisation

The bigger version of this for me was the rota.

I did it myself for years. I told myself I did it because I had the best overview. Who worked well together. What shifts were bigger than they looked. All of that was partly true. What was more true was that I hadn't taught anyone else to do it and I hadn't handed it over because it felt like too important a task to let go of.

When I finally handed it to management, two things happened I did not expect.

The first was the time it freed up. Not just the hours spent doing it. The hours spent thinking about it. The background load it had been running in my head. All of that was suddenly available for actual founder work.

The second was more interesting. The rota got better. Not the same. Better. Because it was being done by people who were actually in the building, seeing the dynamics up close, making the small adjustments only someone in the room could make with real insight.

The lesson isn't that I was bad at the rota. The lesson is that the rota didn't need me.

Ten Signs You're the Bottleneck

One. The team calls you first for problems they could solve themselves.

Two. You do work that isn't yours because you don't trust anyone else to do it properly.

Three. You know the answer to almost every operational question before it's asked.

Four. You feel physically uncomfortable when you're not in the building.

Five. Your team asks permission for things they don't need permission for.

Six. You get frustrated at your team for not thinking for themselves, and then override them when they do.

Seven. You can't remember the last time a significant decision was made without your input.

Eight. Your holidays are interrupted. Consistently.

Nine. You know that if you stepped back for two weeks, the business would suffer.

Ten. You describe yourself as hands on or involved, when what you actually mean is that you can't let go of anything.

If more than three of those landed, you're a bottleneck. If more than five, you've been one for a long time.

Why the Pattern Keeps Itself Alive

The bottleneck pattern reinforces itself. That's what makes it so hard to break.

You are the person the team brings things to. Because you've always been that person, the team has never developed the muscles to handle those things without you. So when you try to step back, the things get handled badly. You see the poor handling as evidence that the team can't be trusted. So you step back in. Which reinforces to the team that you are the person to bring things to. Which prevents them from developing the muscles. Which locks you into being the bottleneck for another cycle.

The team is behaving exactly as they have been trained to behave. The only way to break the loop is for the founder to deliberately do less, deliberately teach more, deliberately tolerate the awkward middle period where the handover is happening and things don't yet run smoothly.

That period is uncomfortable. It looks worse than the bottleneck version. But that discomfort is the price of the shift. And on the other side is a team that can actually think for itself and a founder who can actually lead.

What to Do This Week

The Energy Leak Tracker is the perfect starting point for this specific pattern.

Do it for one week with this pattern in mind. And every time something shows up that felt like a drain, ask one question.

Was that mine to do?

Not was that important. Not was that necessary. Was that mine.

If the honest answer is no, then you've found something to hand over. The wifi call. The rota question. The supplier decision. Each one is a small opportunity to start unwinding the bottleneck.

You don't need to unwind them all at once. Just identify the ones that shouldn't have been yours, and then, deliberately, teach the person who should be doing them how to do them.

That's how you stop being the bottleneck. One handover at a time.