And why delegation alone rarely solves it.

A services CEO I worked with had built a real management team around the business: experienced people, defined roles, clear functions, and genuine responsibility. On paper, there was no obvious reason everything should still depend on him. Yet most evenings, his phone told a different story: A client issue no one wanted to decide, a supplier problem that had already moved through two people, a question that needed his approval before anyone felt comfortable acting. He had hired precisely so this would stop.

It had not.

If you have built a company that has grown beyond its early stage, some version of this is probably familiar. The business gets bigger, you bring in good people, you create management roles, and you try to step back from work others should be able to handle, and still, too much of it finds its way back to you. Not the genuinely big calls; those should reach a founder. It is the ordinary decisions, the routine exceptions, and the problems that sit unresolved until you step in, the work the business should have been able to settle on its own. This is the founder bottleneck, and the first thing worth saying about it is that it is not automatically evidence that the founder cannot let go or that the team is not good enough. More often, it tells you something more useful about how the company has learned to operate.

Delegation is the usual advice, and it is rarely enough

When founders describe this, the advice comes quickly: delegate more, trust your people, let go, and get out of the weeds. There is truth in it. Some founders do hold on to work they should have released years earlier, and learning to hand over real responsibility matters. But delegation alone rarely fixes the problem, because the issue is usually not that the founder refuses to let go. It is that the business has nowhere reliable for the work to land when he does.

You can hand someone a task. You can give them a title. You can even tell them they are accountable. But if it is still unclear what they are allowed to decide, what happens when two functions disagree, or whether they will be backed when they make a hard call, the work travels upward again. The founder has delegated the responsibility. The organization has not absorbed it.

When the founder becomes the structure

As a company grows, certain things have to become clear enough that they no longer need the founder every time something unusual happens: who owns what, who can actually decide, what happens when two teams disagree, who handles the exception, and who closes the issue when the answer is not obvious. When those questions stay fuzzy, the founder quietly becomes the answer to all of them. He is the escalation path, the tie-breaker, the memory of how things are supposed to work, and the person everyone trusts to close what others leave open. None of those roles appears on the organization chart, and the company depends on every one of them.