Free self-diagnosis. No email required.
The Founder Bottleneck Test Six signs, in the order they actually appear
Most lists of bottleneck symptoms are unordered, which makes them useless. By the time you recognise the famous ones, the cheap fixes have expired.
These six are sequenced from earliest to latest. Read down until one stops feeling hypothetical. That is roughly where your business is.
First, the part that most of this advice gets wrong. Being in everything was the correct decision once. In a company of three people, a founder who reviews every quote and answers every difficult client email is not micromanaging. They are doing the job properly, and the tight feedback loop is a genuine advantage.
Nothing about that behaviour changed. The company grew around it. So the question is not whether you have been doing something wrong. It is whether the thing that worked at three people is still working at fifteen.
- 1 Earliest
Your team stops deciding without you
Not because they cannot. Because they worked out that bringing it to you is safer than getting it wrong.
Check it this week: Ask three people what the last decision was that they made without checking with you first. If they have to think hard, you have your answer.
- 2 Early
Queue time creeps up on routine work
Not the hard calls. The ordinary ones. A discount approval, a scope question, a supplier choice.
Check it this week: Ask your team how long they typically wait between raising something routine and hearing back. More than one working day means the business is running at your latency rather than its own.
- 3 Building
Everyone reports to you and nobody reports to each other
A hub and spoke company. Information reaches you and stops, because you are the only person who sees the whole picture.
Check it this week: Draw who talks to whom in a normal week without you in the room. If most of the lines cross your desk, the structure is the constraint.
- 4 Building
You are the escalation path for anything unusual
Every exception routes to you, because no exception has ever been written down. Your team is not avoiding responsibility. They have no criteria.
Check it this week: Count the interruptions in one week that were genuinely novel versus ones you have handled before in some form. The repeats are documentation you never wrote.
- 5 Late
Your best person leaves
Top talent goes first, and the reason is structural. The people most able to decide are the ones most frustrated by not being allowed to.
Check it this week: Look at your last two resignations. If either of them had been asking for more ownership in the six months before they left, that was the signal.
- 6 Latest
Revenue is capped by your calendar
Growth now tracks your availability rather than demand. More marketing produces more work you personally cannot absorb.
Check it this week: Take two consecutive weeks off with your phone off and list what would break. Most founders will not run this test, and refusing to run it is itself the finding.
Recognised three or more?
Then it is worth thirty minutes to work out which kind you have and what the first move is. No pitch, no deck. If the answer is that you can fix it yourself, I will tell you that.
Book a 30 minute callWhich one do you have?
The three types need opposite responses, which is why a generic answer does not help. Match whichever signs you recognised most strongly.
Decision bottleneck
You recognised signs 1 and 2 most strongly.
Write spending thresholds, name an owner for each recurring decision type, and set a default of proceed unless told otherwise on anything reversible.
CEO bottleneck
You recognised signs 3 and 4 most strongly.
Separate the work only you can do, meaning direction, key relationships and capital, from the work that has simply never been handed over. Then hand the second pile over and stop reviewing it.
Owner bottleneck
You recognised signs 5 and 6 most strongly.
Move what you know out of your head and into checklists, thresholds and tools a competent employee can follow without asking. Start with client onboarding and quoting.
When it is not a bottleneck
Worth ruling out before you change anything. If your team is genuinely at capacity, the process works and there simply is not enough of it, then you have a capacity problem and hiring fixes it.
The two look identical from the outside and need opposite responses. Adding people to a systems problem makes the queue longer, not shorter. That distinction is the whole reason to run the checks rather than guess.
Go further
The full diagnostic framework, the four constraint areas, and what a structured intervention looks like are covered in the founder bottleneck guide. If you would rather talk it through, the call is free and thirty minutes.