Short answer: You've become the bottleneck when work stops without you — decisions wait for your input, information exists only in your head, and your team escalates rather than deciding. The fix is three things in order: document what only you know, delegate decision rights explicitly rather than tasks, and make information visible so people don't need to ask you.
How to tell
- Work visibly pauses when you're away for more than two days.
- Your calendar is mostly other people's questions.
- You're consulted on decisions well below your pay grade — and you have a view on each of them.
- Nobody else can produce a complete answer about a client, a project or a number.
- You've delegated tasks but everything still comes back for approval.
- You return from holiday to a queue rather than to progress.
Three or more, and you're the system rather than running it.
Why it happens to competent founders
Not through control-seeking, usually. It happens because in the early stage the founder genuinely is the fastest route to a correct answer, and that stays true long after it stops being efficient. Every time you answer instead of documenting, you optimise the next ten minutes and mortgage the next year.
The second cause is that judgement transfer is genuinely hard. Handing over a task is straightforward. Handing over the ability to decide requires articulating criteria you've never written down and may not consciously know.
Step 1: Document what only you know
Start with what people ask you most. For a fortnight, log every question you're asked. The clusters are your documentation backlog, ranked by frequency, without any analysis required.
Then write the answers — not as instructions, as decision rules. Not "ask me about discounts" but "discounts up to ten percent at your discretion; ten to twenty percent needs a reason recorded; above twenty percent comes to me." The second version removes you from the loop for most cases.
Step 2: Delegate decisions, not tasks
Task delegation without decision rights creates more work for you, because everything returns for approval. Real delegation means naming, for each area, what the person decides alone, what they decide and inform you about, and what genuinely needs you.
Write it down as a decision-rights document. Two pages covering your main areas. It's the highest-leverage document in a founder-led business and it's rarely written.
Then hold the line. The hard part isn't defining the boundary — it's not answering when someone brings you something inside their own authority. Redirect once, and it usually holds.
Step 3: Make information visible
A large share of the questions coming to you are information requests, not decisions. Where are we on this, has that been paid, what did we agree. Those are reporting failures, and they're solvable without any change in delegation.
Get the data into one system, build the views people need for their actual jobs, and point them there. The volume of questions drops noticeably, and the ones that remain are the ones that genuinely need you.
The uncomfortable part
Being needed is not unpleasant, and being the bottleneck can feel like being indispensable. There's often quiet resistance to fixing it — a preference for being consulted, or a worry about what the role becomes when it's no longer required for daily operations.
Worth naming, because unexamined it will undermine every structural fix you attempt. Systems that reduce founder involvement tend to be quietly bypassed by the founders who commissioned them.
Frequently asked questions
How long does this take?
Documentation and decision rights: a few weeks. Behavioural change: longer, and it's the harder part.
What if my team doesn't want more responsibility?
Sometimes true, more often a sign that previous delegation wasn't real — decisions were made and then overturned. Rebuilding that trust takes consistency more than process.
Isn't some founder involvement necessary?
Yes, in strategy, key relationships and genuine exceptions. The test is whether your involvement is deliberate or default.
Your operations work — they just shouldn't need this much of you. Start with a free systems audit.
