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.

I call that Founder Gravity: the pull that keeps drawing decisions, exceptions, and stuck work back toward the founder, even after the company has hired people and built management around them. The founder bottleneck is what you feel; Founder Gravity is what keeps recreating it.

That services CEO had effectively become the company switchboard. His phone was the real coordination system, the place anything unresolved eventually got routed. The people around him were not incapable; several were very good. But over the years they had hey had learned that when a decision carried any real weight: anything unusual, ambiguous, or risky, the safe move was to bring it to him rather than close it themselves. Not because it truly needed the founder, but because deciding it alone had never felt safe.That was never written down. It did not need to be. People learn quickly how a company really works, and once those habits set, they do not dissolve because the founder decides one Monday to delegate more.

The cost is bigger than the founder's diary

At first this looks like a time problem: too many calls, too many interruptions, and too many decisions. The real cost is larger. The founder's attention, which should increasingly go to the few things only he can do, gets consumed by triage. At the same time, the team gets fewer chances to build the judgment the company will need later.

That compounds in a way worth naming. When a manager hands a difficult decision upward and the founder resolves it, both sides are learning something: the manager learns that the hard call ultimately belongs elsewhere, and the founder learns that stepping in is faster. Both can be right in the moment. Repeated often enough, they make the company more dependent, not less. A decision someone is repeatedly rescued from is one they never fully learn to own.

This is why the problem tends to become more visible as the business grows, not less. More customers create more exceptions, more people create more coordination, and more functions create more boundaries where ownership blurs. If those still travel upward, growth does not free the founder; it gives the company more reasons to need him. Adding people does not automatically reduce dependence. Sometimes it just creates more routes back to the same person.

Ask a different question

So I would not start with how do I delegate more. I would start somewhere else: where are decisions actually being made in this company, and where should they be made? When something difficult happens, how far does it travel before someone feels able to close it, and why that far? What can the business genuinely handle without you, and what still stops until you step in? Where have you supposedly handed over authority, and yet people still look to you before acting?

Those questions tend to reveal the real pattern. A manager may carry responsibility for an outcome but still need approval for the decisions required to produce it. A role may look senior on the organization chart but have little room to act. Two departments may each assume the other owns an awkward issue. And sometimes the founder has genuinely stepped back, only to find that no one was ever quite clear about who was meant to step forward. That is a very different problem from poor delegation.

Part of something bigger

Founder Gravity rarely exists on its own. It is usually one sign of a wider condition, where a company has grown faster than its ability to carry that growth: more customers, more people, more revenue, and more complexity, while underneath, too much still depends on the same few people and the same informal ways of getting things done. That is what I call Heavy Growth: the company is getting bigger, but some of the load that growth creates is still being carried personally rather than built into how the business runs. The founder bottleneck is simply what Heavy Growth feels like from the inside, on an ordinary evening, when the phone starts.

Business Fitness looks beneath the symptom. It asks whether it is clear who owns what and who can decide, whether the parts of the business work together rather than pushing problems between them, whether work gets finished without unnecessary escalation, whether profit and cash improve as revenue grows, and whether normal problems can be handled without repeatedly dragging the founder and senior leaders back into the middle. Seen that way, Founder Gravity is not only a leadership issue. It is information about what the company can carry on its own, and what it still cannot.

The goal is not to remove the founder

The answer is not for the founder to disappear, or to care less, or to make yourself deliberately unavailable in the hope that everyone else figures it out. The founder's judgment still matters. The real question is where that judgment should be used: for direction, for the few decisions that genuinely belong at that level, and for the issues that could materially change the business; or simply to keep ordinary work moving? Those are very different roles.

A stronger company does not need the founder less because the founder has become less important. It needs the founder differently: more for direction and the decisions only he should make, and less for repeatedly solving what the organization should already know how to handle. That is what it means for a company to get stronger as it grows.

Stronger, not heavier.

If more still comes back to you than you would like, the useful place to begin is by seeing clearly where that dependence actually sits. The F.I.T. Check is a free, private check you complete on your own. It gives you an initial view of where the business looks strong and where growth may still be creating too much dependence on you or a small number of key people. It takes about ten minutes.