In many small businesses, the founder is the most capable person, the person who cares most and, without anyone intending it, the slowest step in almost every process. Quotes wait for their review. Content waits for their approval. Decisions wait until they have a free moment, which is never.
How founders become bottlenecks
It usually starts sensibly. Early on, the founder did everything, so they know the standards. As the team grows, they keep a final check 'just for now' to protect quality. Each check makes sense alone. Together, they mean nothing finishes without the founder's attention, and the founder's attention is the scarcest resource in the business.
The team adapts by waiting. They stop making decisions because they expect to be overruled. That makes the founder feel even more necessary, and the cycle continues.
Find your approval points
For two weeks, note every time someone waits for you before they can continue. Write down what they were waiting for and how long they waited. Patterns appear quickly: certain decisions you make every week, certain reviews where you rarely change anything.
Turn decisions into rules
Many decisions you make repeatedly follow rules you have never written down. Write them. 'Discounts up to a set limit can be approved by the sales lead; above that, ask me.' 'Social posts using approved templates do not need my review.' Rules let others decide confidently and consistently.
Where you genuinely need to stay involved, define exactly what triggers your review, so everything else can flow freely.
- Below a value threshold: team decides.
- Using approved templates or wording: team decides.
- New, high-risk or unusual: founder reviews.
- Anything with legal or financial commitment beyond a set limit: founder approves.
Review samples, not everything
If you are worried about quality, switch from approving every item to reviewing a sample after the fact. Check a few items each week and give feedback. You keep oversight and coaching, but work is no longer blocked waiting for you. Over time, as quality holds, you can sample less.
Batch the reviews that remain
For approvals you keep, set fixed review windows, such as twice a day, and stick to them. The team knows when they will get an answer and can plan around it, instead of waiting indefinitely and chasing you in chat.
Handing over one decision at a time
Do not try to hand over everything at once. Choose the decision that blocks people most often and has the lowest risk if it goes slightly wrong. Write the rule, explain the reasoning, and tell the team who now owns it. Then resist the urge to step back in unless something genuinely breaks the rule.
After a few weeks, review how it went. If decisions were sensible, choose the next one. If they were not, the rule probably needs a clearer example, not a return to founder approval.
Mistakes founders make when delegating
Delegation tends to fail in the same few ways:
- Delegating the task but not the decision, so the team still has to check every step.
- Overruling decisions in public, which teaches people to wait for approval again.
- Delegating without context, so people follow the rule but not its purpose.
- Taking a decision back after one small mistake instead of improving the rule.
What changes when you step back
Founders who hand over decision rules usually find that their team makes good decisions most of the time, that mistakes are smaller and easier to fix than expected, and that they finally have time for the work only they can do: strategy, key relationships and building what comes next.
Start this week
Start your two-week log of every time someone waits for you. At the same time, choose one decision you are confident you can hand over now and write its rule in three or four lines: what the decision is, the threshold, the owner and when to escalate.
Share it with the team, explain why, and set review windows for the approvals you keep. In two weeks, use the log to choose the next decision. Within a couple of months, you will likely notice that work moves faster and that your calendar has room for thinking again.
Key takeaways
- Track every time someone waits for you for two weeks.
- Write repeat decisions as rules with clear thresholds.
- Replace blanket approval with sampling and batched review windows.
