Stop Being the Bottleneck

If every decision routes through you, every piece of work gets checked by you and every client expects to deal with you personally, you are the bottleneck. It is not a compliment, and it is not evidence of how important you are. It is a structural limit on everything the business can do, and it caps growth at whatever one person can process in a week.

It rarely forms deliberately. It builds through small, individually sensible decisions: doing a task yourself because it is quicker, keeping a client relationship personal because that is what they expect, signing off on something because the process is not quite trusted yet. Each one is defensible. The cumulative effect is a business that runs through you rather than around you.

Signs it is you

• Work stalls when you are unavailable, including for a single day.
• People bring you problems rather than recommendations.
• Clients bypass the team to contact you directly, and you let them.
• You are consistently the busiest person in the business.
• Nothing feels quite right until you have touched it.
• The same questions come back to you repeatedly, from different people.

A worked example: one week of decisions

Illustrative figures. An owner logs every decision, approval and query that lands with them over five working days. The total is 61 items, sorted afterwards:

• 9 genuinely needed the owner — pricing on a large tender, a partnership question, two people decisions.
• 22 were repeat questions — the same handful of situations coming back from different people, because there is no written answer anywhere.
• 18 were spend approvals under £500 — every one approved, none refused.
• 12 were client queries that a named account owner could have handled had one been named.

Now the fixes, in order of effort. Setting a £500 authority limit for two team leads removes 18 items and takes ten minutes. Writing one page covering the six recurring questions removes most of the 22. Naming an account owner for each client and telling the clients removes the 12 over a couple of months.

That takes 61 items to roughly 12, and only the ten-minute change was free. The rest is a couple of days of work in total. The reason it does not happen in most businesses is not difficulty — it is that nobody ever logs the week and sees the shape of it.

Put a value on it if you need the argument: if handling those 49 items consumes six hours a week of owner time, that is roughly 280 hours a year. What those hours are worth depends entirely on what you do with them instead.

The delegation ladder

Delegation is not binary. It is a ladder, and most failures come from trying to jump the whole thing at once:

• You do it.
• You decide, they carry it out.
• They recommend, you decide.
• They decide, check with you first, then act.
• They act within defined limits and tell you afterwards.
• They own it entirely.

Move a task one rung at a time. Trust is built through a series of small bets, not one leap of faith — and an owner who jumps from rung one to rung six, watches it fail, and concludes that delegation does not work has learned the wrong lesson from a self-inflicted experiment.

Brief properly or expect rework

Most delegation fails at the briefing, not the doing. Be explicit about the outcome you want rather than the method, the standard it has to meet, the deadline, and what they can decide without asking. Ten minutes briefing well saves hours of correction, and the correction is what convinces owners it is easier to do it themselves.

Then tolerate a different approach. If the outcome meets the standard, the method is theirs. Intervening because you would have done it differently undoes everything you have just built.

Follow-up is not micromanagement

Delegation without follow-up is abdication, and it usually ends with the owner taking the work back and quietly deciding the person could not handle it. Agree the checkpoints up front — a weekly ten minutes, a shared tracker, a standing update — so you get visibility without hovering.

When you take the work back

Almost every owner does this at least once: something is delegated, it goes slightly wrong, and it quietly comes back. Usually without a conversation, because taking it back is easier than explaining why.

What the person learns is not "I need to improve". It is that the delegation was conditional and they cannot be trusted with the next thing either. One silent retrieval undoes several months of building. If work has to come back, say so directly, explain what specifically was not right, and set out what would have to be true for it to go out again. Then put a date on it.

The same applies to the smaller version — rewriting the email they drafted, correcting the quote before it goes out, fixing the report without mentioning it. Every silent correction teaches the team that your standard is unknowable, so they stop trying to meet it and start waiting for you to apply it.

The checklist

• Log one week of everything that comes to you. Decisions, approvals, questions, client contacts. Do not change anything yet.
• Sort into four piles: genuinely needs you, repeat question, low-value approval, should belong to someone else.
• Set spending authority limits in writing, this week. Most owners find they have never refused anything below the limit they are about to set.
• Write the answer once. Every repeat question becomes a one-page rule that anyone can apply.
• Name an owner for every client account and tell the client who it is. This is the slowest fix and the highest value.
• Move three tasks one rung up the ladder this month. Not to the top — one rung.
• Insist on recommendations, not problems. "What do you think we should do?" asked consistently retrains the habit within a few weeks.
• Agree checkpoints when you delegate, and then hold to them rather than checking in between.
• Re-run the week log in three months and compare the count.

The questions to sit with

• If you were unreachable for two weeks from tomorrow, what would actually break — and what does that list tell you?
• Out of 10, how much of what came to you last week genuinely needed you?
• Which task do you refuse to hand over, and is the reason really about standards or about identity?
• What would have to be true for you to trust someone else with the thing you are holding onto hardest?

Common questions

My team are not capable of taking this on. Sometimes true, and if it is, that is a hiring and development problem rather than a delegation problem — and it needs naming as such. More often the team have never been given a clear standard, the authority to act, or the room to get something slightly wrong.

Clients want me personally. Some do, and a few are worth accommodating. Most have simply never been introduced to anyone else. Bringing a second person into the relationship early, deliberately and by name is the unwind, and it takes a couple of quarters rather than a couple of weeks.

It is genuinely quicker to do it myself. This week, yes. That is exactly how the bottleneck was built. The question is whether it is quicker over a year, counting every future occurrence of the same task.

Is the goal to make myself unnecessary? No. It is to make the business less fragile and to move your time to work only you can do. A business that runs well when you are in it and keeps running when you are not is worth more, commercially and personally, than one that stops when you do.