There is a point in a growing business where the founder can become the person everyone is waiting for. A customer issue needs a decision, a supplier has done something unexpected, someone wants to make an exception for a client, a new hire has a question about how something works, or a project has gone slightly off track. The question eventually makes its way back to the founder because that's where the answer has always been.
In a small business, that can work extremely well. The founder usually has more context than anyone else, decisions can be made quickly, and there aren't many layers between identifying a problem and doing something about it. If you've built the company yourself, it also makes sense that you're the person people turn to. You've been involved in most of the important decisions and you probably know the history behind a lot of things that other people don't.
The difficulty is that this way of working can continue long after the business has become too large for it.
I've seen this happen in different forms, and I don't think it is usually a case of a founder refusing to delegate or wanting to control everything. More often, they've simply become very good at solving problems. When you've spent years making things work, it's natural to step in when something isn't working. If someone asks you a question and you know the answer immediately, giving them the answer feels far more efficient than explaining how they could find it themselves.
The problem is what happens when that becomes the normal way the organisation operates. One question isn't an issue. Hundreds of questions are.
The business starts depending on the person who knows everything
A founder can accumulate an enormous amount of operational knowledge without ever consciously deciding to do so. They remember why a particular customer was given an exception. They know which supplier needs chasing. They remember the conversation that led to a change in pricing. They know which problems have happened before and which ones are genuinely unusual.
That knowledge is valuable. In the early stages of a company, it is often one of its biggest advantages.
But as the team grows, there is a point where having all of that knowledge concentrated in one person starts to slow everyone else down. People don't necessarily lack the ability to make decisions. They lack the context to know whether they're making the right one.
This is where delegation can become frustrating on both sides.
A founder might feel that they've already delegated something because they've handed the responsibility to a manager. The manager, however, may still be coming back to the founder whenever a situation falls outside the most straightforward version of the job. From the founder's perspective, it can look like the manager isn't taking enough ownership. From the manager's perspective, they're being held accountable for something they don't have complete authority to control.
Neither person is necessarily doing anything wrong. The operating structure just hasn't caught up with the responsibility.
Delegation is more than handing someone a task
I think the word delegation gets used too casually in business.
You can give someone a list of tasks without actually giving them ownership of anything. If they have to come back to you every time they encounter something outside the exact scenario you described, you've transferred the work but kept the decision-making.
That becomes particularly obvious in customer support.
If an agent is responsible for responding to customers but needs approval every time a customer asks for something slightly unusual, the agent isn't really empowered to manage the customer experience. The same thing happens in project management when a project manager is responsible for delivery but can't make decisions about priorities, timelines or scope without going back to someone else.
This was something I had to think about while scaling the customer support operation at Feline Skinscience. As the team grew from one person to eight, it wasn't practical for everyone to rely on one person to know how every situation should be handled. We needed clearer workflows and escalation processes, but we also needed people to understand what they could decide themselves and when something genuinely needed to be escalated.
That distinction matters because the purpose of a process isn't to eliminate judgement. It is to give people enough context and boundaries that they can use their judgement confidently.
You don't want eight people asking the same question. You want eight people who understand the principles behind the answer well enough to handle the next variation themselves.
Founders don't need to become less involved. They need to become involved differently.
I think this is where some discussions about founder dependency go wrong. The objective shouldn't be to remove the founder from the business.
There are decisions where the founder's involvement is exactly what the business needs. They may have relationships that nobody else has, a deeper understanding of the product or market, or a particular perspective on where the company should go next. Those things are difficult to delegate because they are part of what the founder brings to the business.
The problem is when the same person is also spending their day approving routine refunds, answering questions about internal processes, checking whether someone followed up with a supplier or resolving issues that should have an owner elsewhere in the organisation.
Those decisions aren't necessarily beneath the founder. They're simply not the best use of their time.
As an operator, that's one of the things I find useful about looking at a business from the middle. You can see where the founder's attention is being pulled and start separating the decisions that genuinely require them from the ones that have ended up there because the organisation hasn't developed enough clarity around ownership.
Sometimes the answer is documentation. Sometimes it's training. Sometimes someone needs more authority. Sometimes two roles have overlapping responsibilities and nobody is quite sure where one ends and the other begins. And sometimes the founder has to make a conscious decision to stop being the person who always steps in.
That last one can be difficult, particularly when stepping in has worked for them for a long time.
The goal is to make the knowledge transferable
One of the biggest shifts a growing business has to make is moving from individual knowledge to organisational knowledge.
That doesn't mean documenting every decision or creating an SOP for every possible scenario. In fact, trying to document everything can create its own problems. People stop thinking and start searching for the correct paragraph.
The more useful question is what the team needs to know in order to make good decisions without constantly going back to one person.
Sometimes that's a process. Sometimes it's a set of guidelines. Sometimes it's better reporting or a regular meeting where decisions are discussed. Sometimes it's simply giving someone enough exposure to a particular part of the business that they develop the judgement themselves.
At Melewi, where I worked with a distributed team across seven countries while managing complex international projects, a lot of this came down to making sure people had enough visibility and ownership to keep projects moving without everyone needing to be in the same room. The business grew from a three-person startup into a nine-person global team, and the way we communicated and managed work had to evolve with it.
That doesn't happen through one big delegation exercise. It's gradual. You build the structure, people grow into their responsibilities, and eventually the business has more people who understand how things work rather than one person who knows everything.
Sometimes the hardest part is recognising that the business has changed
Founders often continue operating the way they did when the business was smaller because, for a long time, that way of working was exactly what made sense.
Five people can communicate informally. Ten people might still manage it. At some point, though, the number of conversations, decisions and dependencies becomes too large for the same approach to work comfortably.
That doesn't mean the business needs to become corporate. It means it needs to acknowledge that it is no longer the same organisation it was a few years ago.
For me, that's one of the more interesting parts of operations work. You're constantly trying to find the point between too little structure and too much of it. Too little and everything depends on individuals. Too much and people spend their time maintaining the system instead of doing the work.
The right answer changes as the business changes.
A founder becoming a bottleneck isn't necessarily evidence that they've done something wrong. In many cases, it's evidence that they've built something that has grown beyond the way they originally ran it.
The job then is to help the organisation catch up.
That might mean taking some decisions away from the founder, but it might just as importantly mean making sure the people receiving those decisions have the information, authority and support to handle them well.
When that happens, the founder doesn't disappear from the operation. They get the opportunity to spend more of their time on the parts of the business where their involvement actually makes the biggest difference.
And the rest of the organisation becomes capable of carrying more of the weight.