Most founders don’t decide to become the bottleneck. It happens gradually. You’re the one who knows how everything works, so questions come to you. You care about quality, so approvals come to you. You set the direction, so decisions come to you. One day you realise the whole business moves at the speed of your inbox.
The good news is that being the bottleneck is a systems problem, and systems problems can be fixed. Here’s the framework I use.
Step 1: Find out where you’re the bottleneck
For one week, keep a simple log. Every time someone waits for you, write down:
- What they needed (an answer, an approval, a decision, information)
- How long they waited
- Whether you were the only person who could really handle it
At the end of the week, sort the list into four groups:
- Information requests: “Where is…?”, “How do I…?”, “What did the client say about…?”
- Approvals: sign-off on work, spending, messages to clients.
- Decisions: choices between options.
- Work only you are doing: tasks stuck because you haven’t done your part.
Most founders find that information requests and approvals make up the majority. Those are the easiest to fix.
Step 2: Fix information requests with documentation
If people keep asking you how things work or where things are, the knowledge lives only in your head. Fix it by:
- Writing SOPs for your most-asked processes. Record yourself doing them and turn the recording into a document.
- Creating one source of truth. Client details, project status and files should live in your project hub, not in your email.
- Building a simple FAQ for your team, covering the questions you answer every week.
- Using an AI assistant loaded with your documents. A Claude Project or a custom GPT with your SOPs and policies can answer many “how do I…?” questions instantly. Make sure someone keeps it current.
Every question you document is a question you never answer again.
Step 3: Fix approvals with clear standards
Approvals come to you because the team doesn’t know what “good” looks like, or doesn’t feel trusted to decide. Fix both:
- Write down quality standards. A short checklist for each type of deliverable: what it must include, what it must not include, how to check it.
- Set approval thresholds. For example: client emails using an approved template need no approval; anything mentioning price, scope or deadlines does. Spending under $200 on tools needs no approval; above that does.
- Move to spot checks. Instead of approving everything, review a sample each week. If quality holds, reduce the checks further.
Step 4: Fix decisions with decision rights
This is the most powerful step. Write down who decides what. A simple way to do it is three levels:
- Decide and act. The team member decides and doesn’t need to tell you. Examples: scheduling, routine client replies, task order within their own work.
- Decide and inform. They decide and tell you afterwards in the weekly update. Examples: small scope changes, contractor deadlines, tool settings.
- Recommend and wait. They bring you a recommendation and you decide. Examples: pricing, hiring, new services, anything that affects a key client relationship.
Put this in a one-page document and share it. Review it every quarter, and move things down a level as trust grows.
The rule that makes it work: people should bring you a recommendation, not just a problem. “The client wants an extra revision. I suggest we do it and log it as goodwill, since they’re renewing next month. OK?” takes you ten seconds to answer. “The client wants an extra revision. What should I do?” takes you ten minutes.
Step 5: Protect time for the work only you can do
Some work really is yours: key sales conversations, creative direction, partnerships, big strategic decisions. When that work is stuck, everything behind it is stuck too.
- Block time in your calendar for it, two or three times a week, and protect it like a client meeting.
- Batch approvals and decisions into one or two set times each day, instead of answering as they arrive.
- Have someone triage your inbox and messages, so only the things that really need you reach you.
Step 6: Put someone in charge of the system
Documentation, standards and decision rights all drift without an owner. Someone needs to:
- Keep SOPs and the decision rights document current.
- Run the weekly operations rhythm, so issues are handled before they reach you.
- Notice when things start routing back to you, and fix the cause.
In a small business, this is usually the person who owns operations: an operations manager, an OBM, or a capable team member you’ve developed into the role.
What it feels like when it works
- You return from a day off to a short summary, not a long queue.
- Your team brings you decisions with recommendations attached.
- You spend most of your week on sales, clients and strategy.
- The business keeps moving when you’re unavailable.
Start with one thing
Don’t try to fix everything at once. This week, keep the bottleneck log. Next week, write the decision rights document. The week after, document your three most-asked questions. Small changes compound quickly.
If you’d like someone to take over the system so you can step back, that’s exactly what I do. Start with an Operations & AI Audit.