Being the person everyone comes to feels like recognition. It’s usually a diagnosis.
If every question routes to you, decisions can’t be made without you. That caps how large the business can get, guarantees you’ll be interrupted constantly, and means your team isn’t developing the judgement they’d need to take any of it off you.
None of which is their fault. You built it, one reasonable answer at a time.
How it happens
Nobody sets out to become a bottleneck. It’s constructed from sensible individual choices.
Early on you knew everything, because you did everything. Someone asked, you answered, and it was genuinely faster than explaining. They asked again. You answered again. Each instance took ninety seconds and saved twenty minutes of teaching.
Repeat for three years and you’ve taught an entire organisation that the route to an answer is you. They’re not being lazy. They’re doing what has always worked.
The tell is that the questions have stopped being hard. You’re being asked things you’d expect them to handle — which means the constraint isn’t capability, it’s permission.
What it actually costs
Your attention, in the worst possible shape. Not a solid block of interruption but a steady drip, each costing far more than its duration because of the recovery time. This is why owners end days exhausted with nothing built.
Their development. Someone who never decides never learns to decide. You can employ a capable person for four years and produce someone who still can’t run anything, purely by being consistently available.
The ceiling on the business. A company where all decisions pass through one person can only be as large as that person’s throughput. Every growth plan runs into this eventually, usually presenting as “we can’t find good people.”
And your ability to be absent. Holiday, illness, anything. If the business pauses when you do, you don’t own a business — you own a job with unusually high stress.
The framing that works
The instinct is to delegate tasks. That helps with workload and doesn’t fix this, because the questions keep coming about the delegated tasks.
What has to move is decision rights. Here’s the version I use with my own team:
I give you permission to make decisions, and those decisions need to make sense — for you, for me, and for the business.
All three parts are doing work.
For you, because a decision that makes your job impossible isn’t a good one, and people will make those to please you.
For me, because I answer for it, and that’s a real constraint rather than ego.
For the business, because plenty of choices are comfortable for the person making them and quietly expensive for the company.
It works because it’s a test someone can apply without me in the room. “Would Haley approve” requires imagining me. “Does this make sense for the business” requires thinking.
What I learned the expensive way
The failure everyone braces for is people who won’t decide anything. That’s not what actually happens.
What happens is someone decides confidently, in a direction you’d never have gone, and you find out weeks later when the invoice arrives. Something gets sort-of done, at considerable cost, in a way that makes no sense.
Which is why the rule I give now isn’t “come to me for approval.” It’s tell me if you have a problem. Different instruction entirely. It leaves the deciding with them and surfaces the things that are genuinely going sideways, rather than the routine choices I don’t need to see.
Practical moves
- Answer with a question. “What do you think you should do?” Most of the time they know, and you’ve just found out. Say it consistently for a month and the shape of what people bring you changes.
- Set spending authority with a number. “Up to $500 without asking” removes dozens of approvals a week. The number matters less than having one.
- Write down anything you’ve explained twice. If it’s been asked twice it’ll be asked twenty times. A short written answer, somewhere findable, ends that permanently.
- Name who owns what. Not job titles — decisions. Who decides on refunds, on scheduling, on which supplier. Ambiguity defaults to you.
- Be unavailable on purpose, occasionally. A half-day where you cannot be reached surfaces exactly which decisions are stuck behind you, because you’ll hear about all of them afterwards.
What to expect
It gets worse before it improves, and knowing that in advance is most of what gets people through it.
People will make decisions you wouldn’t have. Some will be wrong. The temptation at that point is to conclude they can’t handle it and take it back — which teaches everyone that the delegation wasn’t real, and you’ll never get another chance at it.
The useful response to a wrong decision is to ask how they reached it. Usually you’ll find they were missing one piece of context, which is fixable and worth far more than reversing the decision.
Allow months, not weeks. You spent years building the habit; it doesn’t unwind in a fortnight.
The thing worth noticing
Being needed is pleasant. There’s a real satisfaction in being the one who knows, and a quiet unease in being less necessary.
Worth being honest with yourself about, because it’s frequently the actual obstacle. Not that the team can’t handle it — that you’re not entirely sure who you are in a business that runs without you.
That’s a solvable problem too. But it’s a different one, and no amount of process design touches it.
More on what happens when the business depends on you and the weight that comes with it.
