How do I stop being the bottleneck in my business?
Write down the five decisions people bring you most. Set who can make each one, and up to what amount. Then review them once a week instead of approving them one by one. The bottleneck is the decisions that only live in your head, so the team has to come find you.
Last updated:
Why you became the bottleneck
For a very long time it might not even feel like a bottleneck. It feels like leadership. It feels like helping everybody. Someone hits a wall, they come find you, you unblock them, and everybody moves on with their life.
Usually, it comes down to three things:
- The rules were never written down. The steps live in people's heads, so every exception comes back to you.
- Nobody has a limit. Your managers could decide, but nobody told them up to what amount, so they ask.
- The numbers don't agree. Two systems give two answers, so you end up as the one who knows which is right.
The 7-day decision log
For one week, write down every decision someone brings you: what they asked, who asked, and whether it has come up before. At the end of the week, sort each one:
- Keep it. Only you should make this call.
- Hand it off. Someone else can decide, with a limit.
- Write a rule. The answer is the same every time.
- Kill it. Nobody needed to ask.
Write the decision, not the task
Most SOPs list the steps and skip the judgment call. The steps aren't why people come to you. The decision is. So write down what good looks like, who decides, and up to what limit.
The owner's logic and judgment need to be written down too, because that's what made the company great in the first place. You don't have to start from a blank page. We start from a library of pre-built SOPs and fit them to how your company actually works.
Set authority limits
Every recurring decision gets one owner and one number. Written down, that's a decision authority matrix. For example:
| Decision | Who decides | Up to | Above that |
|---|---|---|---|
| Refunds | Office manager | $500 | Owner |
| Discounts | Sales lead | 10% | Owner |
| Overtime | Shift supervisor | 5 hours per person per week | Operations manager |
| Hiring | Department manager | Inside the approved budget | Owner |
Your numbers will be different. What matters is having one.
Replace approvals with a weekly rhythm
Once the limits exist, stop approving and start reviewing. Hold one weekly operations meeting: the numbers, what went over a limit, and who decided. No status updates.
If the same exception shows up three weeks in a row, the limit is wrong. Change the number and keep the decision where it is.
How long it takes
The decision log takes one week. What comes after depends on how many decisions live only in your head. In one engagement, $1.2M of $1.4M in overdue receivables was collected in three months, once one person owned receivables.
What this has to do with AI
You can't hand a company to AI if you can't hand the work to another competent operator without recreating your judgment every time. If a new hire can't make the call from what's written down, an agent can't either. Every agent runs until it hits a gate a person still owns.
Efficiency Sprint makes companies operationally ready for AI. The operational AI readiness check takes about two minutes and shows where your company stands.
Questions
Should I hire a COO to stop being the bottleneck?
A COO helps once the decisions are written down. Without that, a new COO learns them the slow way, by asking you one decision at a time. Write the decisions and limits first, then hire into a seat that has them.
What should I delegate first?
Start with decisions that repeat every week and touch money: refunds, discounts, overtime. Each one looks too small to write down. Together, they fill your day.
How do I know I'm still the bottleneck?
Count the approvals waiting for you to sign off. Watch what happens when you're gone for a week. If the work stops, you still are.
Can AI take decisions off my plate?
The ones with a written rule and a limit, yes. Under the limit, the agent acts. Over it, a person decides. You always need to know who is responsible. And it can't be AI.