Debottlenecking the Smartest Person in the Room
What I See From the Other Chair, Part 6
The founder is usually right. That is exactly the problem. When one person's judgement is the fastest route to a good decision, an organisation quietly stops building a second one.
A founder I worked with had built something genuinely impressive: a company that had grown well past the point where one person could reasonably know everything happening inside it. And yet almost every meaningful decision still seemed to need this one person in the room, not because anyone insisted on it, but because this person was, by a wide margin, usually right. Better instincts, faster pattern recognition, a sharper read of what mattered. The company hadn't outgrown its founder's judgement. It had outgrown the idea that judgement alone could keep scaling with it.
This isn't a story about ego, or about a leader who needs to 'let go'. Most of the time, the person at the centre of this pattern isn't hoarding control, they're simply the most reliable node in a system that was built, often without anyone deciding it on purpose, to route everything through them. That's a design problem, and design problems have design solutions.
Why being the best answer becomes the constraint
Early in a company's life, having one person with consistently excellent judgement is an enormous asset. Decisions move fast because there's no ambiguity about who decides, and the quality bar stays high because that person's instincts are usually sound. The same structure that's an asset at 15 people becomes something different at 150, not because the judgement got worse, but because the volume of decisions needing that judgement grew faster than any one person's available hours. The constraint isn't the person. It's a system that never built a second or third node as good as the first one.
This is, in a real sense, a success problem. It only shows up because the company grew enough to need more decision-making capacity than one excellent brain can supply. Few problems are better to have.
What debottlenecking actually looks like
The instinct is often to frame this as the founder needing to delegate more, which is true but too vague to act on. Delegation that simply hands a decision to someone less equipped to make it well doesn't debottleneck anything, it just moves the bottleneck downstream and adds a quality problem on top. The more useful version of this work is specific: identifying the two or three decision types that consume the most of a senior leader's judgement, and then deliberately building the second brain for each one, not by hoping someone grows into it, but by actively coaching a specific person against a specific category of decision until their judgement on that category is genuinely trustworthy.
This tends to work best one decision category at a time rather than as a blanket push to 'delegate more'. A founder who is the bottleneck on pricing calls, hiring at the leadership level and product trade-offs doesn't need three vague reminders to trust the team. They need three different people, each deliberately built up against one of those three categories, with real decisions, real stakes and real room to be wrong occasionally while that judgement develops.
The role of structure, not just trust
Organisations can build this on purpose rather than waiting for it to happen organically, which it rarely does on its own. A clear map of decision rights, who can decide what without checking, reviewed and updated as people prove themselves against specific categories, turns a vague hope of 'more delegation' into a visible, trackable structure. Pair that with a deliberate second-in-command model for the two or three decision types that matter most, rather than one generic deputy expected to be excellent at everything, and the bottleneck starts to dissolve in the exact places it was actually costing the company speed.
What actually helps here is usually narrower than it looks from the outside: not a general push to trust people more in the abstract, but working through specific recent decisions to find exactly where a leader's judgement is genuinely still needed and exactly where it's now showing up out of habit rather than necessity. Once that line is visible in real instances, the handing-over tends to happen faster and with far less anxiety than expected going in.
If you're a founder or senior leader recognising this pattern, the question worth sitting with isn't 'how do I stop being the bottleneck'. It's narrower and more answerable: which two or three decision categories, specifically, are costing you the most hours right now, and who on your team is closest to ready to own one of them fully?
For an organisation, the parallel question is just as direct: do you have a real, current map of who can decide what without checking, or is that map only sitting in one person's head? Building it on paper, deliberately, is usually the fastest way to find out how much capacity has been waiting, unused, the whole time.
Deepak Narayan is an independent leadership coach and consultant at Rivi Consulting.