“I've grown to 10 people, but I can't get beyond this.”
This is a common point of frustration when a design business starts to grow.
You have done the obvious things. You have hired designers. You may have brought in people to handle accounts, administration, finance or project management. You have more people, more clients and more capability than when you started.
But the business seems to have hit a ceiling.
You are still involved in the important client conversations. People still come to you when there is a difficult decision. Clients still call you directly. You review work because you don't want quality to slip. You attend meetings because you want to know what is happening. And when something goes wrong, it somehow ends up back on your desk.
So you hire another person.
And somehow, you become even more involved.
This is where many design businesses get stuck. The next stage of growth isn't necessarily about adding more people. It is about changing the way the business operates so that it no longer depends on you to keep everything moving.
Giving up the illusion that being involved means being in control is one of the hardest transitions a leader has to make.
The problem isn't that you are doing too much work. The deeper problem is that the organisation has become dependent on your personal involvement to function.
“But I need to know what is going on.”
Of course you do. The mistake is thinking that knowing what is going on requires knowing everything that is going on.
Imagine a client changes the scope of a project. The change could affect the deadline. Your team discusses it during your regular weekly meeting. You hear about it, along with twenty other things.
Later, the deadline slips.
You ask why nobody raised the issue.
The answer is perfectly reasonable: “We told you about it in the meeting.”
And they did.
This is where many growing organisations get into trouble. They confuse communication with operational signalling.
You were informed, but the organisation never formally registered the issue as something requiring attention. It wasn't raised through the mechanism designed to identify risks. It wasn't on the dashboard or exception report. It wasn't visible as a change to the plan.
You heard the information, but the system didn't capture it.
When you are managing a small team, you can compensate for this with your own memory and attention. As the organisation grows, you cannot.
That is why processes matter.
A good process is not bureaucracy added to slow people down. It is a way of making important information visible without requiring the leader to personally remember everything they have heard.
Don't create a process and then bypass it
This is where another problem appears.
You create a process that says, for example, that anything which could affect scope, schedule, budget or quality must be flagged immediately.
Then you continue to attend every meeting, ask everyone what is happening and solve problems yourself.
It feels reassuring. You are staying close to the work.
But you are also sending a message to the team: the formal process isn't really necessary because the leader is already involved.
Eventually people stop raising flags properly.
Not because they are careless, but because they have been mentally trained to believe that telling you something is enough.
If you want people to use a process, you have to trust them to use it. And that sometimes means resisting the temptation to intervene.
There may even be occasions when you need to let a process fail in a relatively safe situation. Let the consequence become visible. Let the team experience why the step exists.
That doesn't mean allowing serious failures that could damage the business or a client. It means recognising that constantly rescuing people can prevent them from learning why the system matters.
“The client still calls me.”
This is another common sign that the organisation has not really transferred ownership.
You may have appointed someone to manage the client. The organisation chart says they own the relationship. But when the client has a problem, they still call you.
Sometimes the reason is obvious: you haven't developed people who are capable of taking over the relationship.
But sometimes the problem is you.
If you continue taking those calls, answering every question and stepping in whenever the client asks for you, you are teaching the client who the real authority is.
You have given someone responsibility without giving them authority.
The solution is not simply to tell the client to speak to someone else. The client has to experience that person as someone who can make decisions, resolve issues and represent the organisation.
That requires you to transfer authority, not just tasks.
“I hired good people, but they aren't expanding the business.”
This is perhaps one of the more frustrating stages of growth.
You hire capable people because you want them to take the organisation further. Then you tell them how you want things done.
You review their work constantly. You correct their decisions. You explain how you would have handled the client. You ask them to follow the methods that made the business successful when you were doing the work yourself.
Eventually you wonder why they aren't showing more initiative.
But what room have you actually given them to take initiative?
You cannot scale your way of doing things by hiring more people. You have to create an organisation capable of discovering better ways of doing things without you.
There is a significant difference between telling someone to execute your method and giving them responsibility for an outcome.
The first creates people who reproduce the founder's way of working.
The second creates people who can develop the organisation beyond the founder's way of working.
If everyone has to make decisions the way you would have made them, then you haven't really created a team of leaders. You have created a larger team of you.
“If I step back, the quality will drop.”
This is probably the hardest fear to overcome, particularly for people who built their reputation on the quality of their own work.
You know what good looks like. You know the history of the clients. You understand the decisions that were made. You can see problems that someone less experienced might miss.
So you stay involved.
But if you continue reviewing every decision because someone might make the wrong one, you eventually become the quality-control mechanism yourself.
That doesn't scale.
A growing organisation needs a process that ensures due diligence happens at the right points, that decisions are reviewed where necessary and that exceptions are raised early.
The leader's responsibility then changes.
You don't need to inspect every decision. You need to make sure that the system through which decisions are made is working.
Look at exceptions. Look at outcomes. Look for recurring failures. Ask where the process isn't working.
And when nothing has been flagged, resist the urge to go looking for something to fix simply because you are used to being involved.
What stepping back actually looks like
Stepping back does not mean disappearing.
Some of the best leaders I have observed are still very present. You know where to find them when something genuinely needs their attention. They are encouraging. They ask how things are going. They are available when there is an exception or a decision that genuinely requires their experience.
What they don't do is demand to know every detail.
They don't need to know what happened in every meeting. They don't need to review every decision. They don't need a running commentary on every project.
They trust the people responsible to get the job done.
That distinction is important.
They are available when you need them, not involved because they feel they should be.
That creates space for people to own their work. It also creates something that is much harder to build while the leader remains deeply involved: accountability.
Start by removing yourself from the system
If you recognise yourself in these problems, don't start by hiring more people.
Start by identifying where the organisation still depends on you.
Ask yourself:
- What decisions still come to me that someone else should own?
- Which meetings do I attend because I am genuinely needed, and which do I attend because I am used to being there?
- Where do people tell me things instead of using the process designed to raise an issue?
- Which clients still see me as the ultimate authority?
- Which people have responsibility without the authority to exercise it?
- Where am I asking people to work the way I worked rather than asking them to achieve an outcome?
- What would happen if I stopped checking this particular thing?
The answers will show you where the organisation has grown but your role hasn't changed with it.
Then make deliberate changes.
Give people clear ownership. Define the signals that require escalation. Make the important information visible. Transfer authority to the people who are supposed to own relationships and decisions. Stop bypassing the process you want the team to follow.
And then do something that can feel surprisingly difficult: let people get on with it.
The goal of scaling is not to make yourself capable of managing more things. It is to make fewer things dependent on you.
That is the real transition.
A small organisation can run on the founder's memory, judgement and personal involvement. A larger organisation cannot. Eventually, the leader has to stop being the organisation's memory, escalation mechanism, quality-control mechanism and decision-making mechanism.
The organisation needs mechanisms that can do those jobs without the leader sitting in the middle of everything.
And the leader needs the discipline to trust those mechanisms.
That is when growth starts to feel different. You are no longer trying to keep control of a bigger version of the business you built.
You are building an organisation that can operate, learn and improve without needing you to be at the centre of every decision.
