Take a week away from the business and count the calls. Most owners of established businesses already know the answer. The phone doesn’t stop. Approvals wait. Decisions queue up until you are back.
The team isn’t incapable. The business was built around one person’s judgement, and it still is.
How the bottleneck forms
It is a side effect of success. In the early years, the owner’s involvement in everything was the advantage: faster decisions, sharper judgement, relationships nobody else had. Customers bought from you because they got you.
The business grew. The habits didn’t change. Every decision that once took a minute now joins a queue at one desk, and that desk has a limit. Growth slows to the speed of the owner’s attention, and the owner reads it as the team being slow.
Three signs you are the constraint
- People bring you problems they could solve. Not because they can’t, but because the last time they decided alone, it was overturned.
- You learn the status of things by asking. If the only way to know whether something is on track is a phone call, the information isn’t flowing on its own.
- Things slow down when you travel. The clearest test there is. A business that runs well only when you are in the building is running on you.
A business that needs you for everything can only grow as fast as you can answer your phone.
Design, not delegation
“Delegate more” is advice nobody can act on. Delegation fails when it is a hand-off without the structure underneath it: the team gets the work but not the authority, the information or the rules. So it comes back to you.
What works is designing four things deliberately.
1. Decision rights
Write down which decisions belong to whom, and where the limits are. Not a philosophy. A table.
| Decision | Who decides | Comes to you when |
|---|---|---|
| Vendor payment within approved budget | Accounts lead | Outside budget, or a new vendor |
| Customer discount within the agreed band | Sales head | Beyond the band |
| Hiring for an approved role | Department head | Senior or new roles |
| Fixing a customer complaint | Service lead | Refunds above the set limit |
The last column matters most. It tells the team exactly when to bring something to you, and, just as important, when not to.
2. Information that arrives without asking
One page you read on Monday morning: what is on track, what is late, what is at risk, and who owns each. If you have to ask for status, the system has already failed once.
3. A rhythm
Ad hoc calls are what fill the gap when there is no rhythm. A short daily check-in for operating leads, a weekly review with a fixed agenda and a monthly look at the numbers replace most of them. Same questions, same time, every time.
4. Escalation rules
Agree in advance what happens when something slips: who hears about it, and when. Clear escalation removes the need to chase, because nothing can wait quietly for long.
The hardest part is you
Systems like this rarely fail because the team rejects them. They fail because the owner steps back in. A decision gets overturned, and the team learns that the rules are optional.
There is a simple discipline that prevents this. If you disagree with a decision made inside the rules, change the rule, not the decision. The team keeps its authority, and the system gets better each time.
The two-week test
If you disappeared for two weeks, what would stop? Write the list. Be honest about it.
Every item on that list is a design task: a decision right to write down, a report to automate, a rhythm to set, a rule to agree. Work through the list and the business gets lighter to carry.
The aim is not to make you unnecessary. It is to put your time where only you can add value: relationships, capital and direction. The rest should run without you holding the thread.