When You're the Bottleneck: Recognizing It and Acting
Being the bottleneck is the most common structural problem in a scaling company and the one founders are slowest to diagnose, because from the inside it does not feel like a bottleneck. It feels like being busy, needed, and slightly behind. The signals arrive as other people’s problems — a team that is slow, a decision that stalled, an executive who did not take initiative — which is why founders usually work on the symptoms for a year before recognising the cause. This page is about identifying which kind of bottleneck you actually are, because there are five and they have different fixes.
What’s inside
It is a design outcome, not a character flaw
Five types of bottleneck
How to measure yours
The fix that matches each type
Why the obvious fixes fail
When it means something bigger
Where Blomma fits
It is a design outcome, not a character flaw
Every founder becomes a bottleneck, because every startup is deliberately designed to have one. In the first two years, routing everything through the founder is correct: you have the most context, the highest standards, and the fastest decision loop, and the coordination cost of a single point of decision is trivial at eight people.
The design never gets revisited. You keep the decisions you are best at, leave a boundary undefined because you can resolve it personally, appoint two strong leaders and become their tie-breaker. Each individual choice is efficient. The aggregate is a company whose throughput is capped by your calendar, and no amount of hiring changes that — which is why founders in this position often experience new senior hires as adding work rather than removing it.
The useful consequence of framing it this way: a bottleneck is a structural condition with structural fixes, not a personal failing requiring you to be better or work harder. Working harder is in fact the standard first response and it makes the situation worse, because it raises your capacity slightly and thereby delays the redesign.
Five types of bottleneck
Five distinct versions, frequently mistaken for each other.
Decision bottleneck.Decisions wait for you because nobody else has authority. Symptom: your calendar is the critical path on unrelated initiatives, and people describe themselves as “waiting on you.” The most common type and the most fixable.
Approval bottleneck.Others make the decisions but nothing ships without your sign-off. Symptom: a queue of finished work awaiting review, and quality being defined as “what the founder accepts.” Distinct from the first, because the authority exists but you have retained a veto.
Information bottleneck.You are the only person who knows things — customer history, the reasoning behind past decisions, what the board actually wants. Symptom: work gets redone after you see it because a constraint nobody knew about surfaces, and people preface requests with “I don’t know if this is right, but.” This is the least visible type and the one that most reliably makes competent teams look incompetent.
Integration bottleneck.You are the only person who can see across functions, so any cross-functional issue routes to you. Symptom: your week is spent resolving things between other people’s teams, and two leaders who cannot agree both come to you rather than to each other.
Relationship bottleneck.You personally hold the key customers, partners, or candidates. Symptom: important external relationships have no second point of contact, and your absence puts specific revenue at risk. Often the most business-critical and the least discussed.
Most founders are two or three of these at once, in which case the sequence matters: information and decision bottlenecks tend to be upstream, and fixing them frequently dissolves the others.
How to measure yours
Subjective assessment is unreliable here, and busyness is not a measurement. Three tests, in increasing order of usefulness.
Audit four weeks of your calendar and inbox.For each meaningful item, mark whether you were the decision-maker, the approver, the information source, or the referee between two other parties. The distribution names your type directly, and it usually surprises founders — most expect decision and find integration or information.
Count what is waiting on you.Ask your executives to list what they are currently blocked on that requires you, without softening it. Ask for the list in writing, because in conversation people minimise. The length of that list is your bottleneck, quantified, and the request itself signals that you want the real answer.
Take two genuinely unreachable weeks.The highest-fidelity test available. What stalls is your dependency structure, mapped precisely. What people decide in your absence tells you which authority you had informally withheld. And the specific things that break are your fix list, in priority order — no analysis required.
Run at least the second one before you conclude anything. Founders who diagnose this by intuition routinely fix the wrong type.
The fix that matches each type
The fixes are specific, and applying the wrong one is why founders often report that delegation “did not work.”
For a decision bottleneck: write down decision rights.A short list of the decisions that matter — pricing, senior hires, roadmap, spend above a threshold — and for each, who decides and who is consulted. Then hold to it, including when you disagree with an outcome. It reads bureaucratic for your size and it removes the single largest source of founder bottleneck, because vague delegation reverts to the founder under pressure unless the alternative is written.
For an approval bottleneck: replace review with standards.Define what good looks like specifically enough that someone else can judge it, name who owns the judgment, and take yourself out of the path. Expect the first several outputs to be worse than yours. That is the cost of the transition, and intervening resets the whole thing to zero.
For an information bottleneck: write things down.Unglamorous and the highest return of the five. The context in your head — why the pricing is structured this way, what happened with that customer, what the board actually cares about — needs to exist outside you. A few hours of writing removes weeks of downstream rework.
For an integration bottleneck: build the executive team’s ability to resolve among themselves.Explicitly tell two leaders in conflict to resolve it and report the outcome, rather than adjudicating. Then establish a forum where cross-functional trade-offs get made without you. This one takes about a year and is the only fix for a company that needs to grow past your bandwidth.
For a relationship bottleneck: introduce a second owner to every key relationship now.Not a handover — a second point of contact, immediately, on every relationship that matters. This is also the one with genuine business risk attached, so it should not wait for the others.
Why the obvious fixes fail
Three standard responses that reliably do not work, and why.
Hiring more senior people.Sensible, and insufficient on its own. A senior hire dropped into a structure that routes decisions through the founder becomes an expensive person waiting on the founder. Without explicit authority they cannot relieve the bottleneck, and they leave within eighteen months — which then gets diagnosed as a hiring problem.
Delegating tasks.Handing over work while retaining the decisions moves the labour and keeps the bottleneck. The thing that must move is authority. This is the most common misdiagnosis in the entire subject: founders delegate extensively, feel they have delegated, and remain the constraint.
Working harder.Raises throughput slightly, delays the redesign indefinitely, and produces a founder who is exhausted and still the constraint. It also actively conceals the problem, because a heroically productive founder makes the structural issue invisible until they break.
The pattern connecting all three: each addresses capacity, and a bottleneck is a question of authority and information, not capacity.
When it means something bigger
Most of the time this is a design problem you fix and move past. Occasionally it is telling you something about the seat.
The distinguishing test is whether it persists after an honest attempt. If you have written decision rights, given real authority, documented the context, hired the missing executive, and you are still the constraint six months later — that is a different signal, and worth taking seriously alongside the broader question of whether a founder should step down.
But the sequence matters, and founders frequently invert it. Being the bottleneck is not itself evidence that you are the wrong CEO. It is evidence that a structure designed for eight people is still running a company of ninety. Do the structural work first; only what survives it tells you anything about the seat.
Where Blomma fits
The hard part of this is not knowing that you should delegate. Every founder knows. The hard part is that the specific act of letting go is a conversation you have not had before — telling your best engineer you are no longer reviewing their work, telling an executive that a decision is now theirs and meaning it, sitting with an outcome you would have done differently and not stepping in.
Blomma is an always-on AI career coach with no stake in how you run your company. Use it to work out which of the five types you actually are — the diagnosis founders most often get wrong. Use it to draft the decision-rights list and pressure-test whether it is specific enough to hold under disagreement. Use it to rehearse the handover conversation, and to think through the moment two weeks later when the work comes back worse than you would have done it and every instinct says intervene. When it warrants a human who has redesigned around themselves at your stage, bring one in..
Every scaling company has a founder-shaped bottleneck, because every startup was built with one on purpose. The companies that get past it are not the ones with more disciplined founders. They are the ones where someone noticed the design had not been revisited in three years, and changed it deliberately.