There's a stage of small business where keeping everything in your head genuinely works.
You know every client, remember every deadline, every processes consist of "I know how to do it," and the spreadsheet you threw together one afternoon is doing a surprisingly respectable job.
Then the business grows.
More clients, more tools, more people, more decisions, more things happening at the same time. The informal ways of working that helped you move quickly at the beginning start creating more work.
Outgrowing the way you work doesn't mean you've done something wrong. It means the business has changed, and the way you run it needs to catch up.
Here are seven signs that might already be happening.
Everything still needs to go through you
If every meaningful decision, approval, and piece of information comes back to the founder or director, growth gets difficult very quickly.
You become the place where work waits and people message you because they don't know where information lives. Suppliers need your approval and projects stop until you've reviewed something. Your team is capable, but they can't move confidently without checking what you think first.
This is the leadership bottleneck in action.
The answer isn't simply "delegate more." Delegation works when people have enough context, clarity, authority, and process to make decisions without creating new problems. If everything depends on you, the business may have outgrown founder memory as an operating system.
Important projects keep getting pushed to next month, or next year
There's always something that needs doing after the urgent work is finished. The problem is that urgent work is never finished.
The date you’ll finally strategise your next software rollout moves again, the staff event you’ve been thinking about for months sits untouched. The onboarding overhaul waits another quarter and the internal program you've talked about repeatedly still hasn't left the planning stage.
When strategic projects consistently lose to day-to-day work, you may not have an ideas problem. You have a capacity and ownership problem. Important projects need someone responsible for moving them while the rest of the business continues.
Your systems don't talk to each other
At some point, small businesses can end up with a collection of software rather than a system.
A tool gets added because one problem needs solving. Another platform appears six months later and somebody creates a spreadsheet to bridge the gap. Information gets copied manually from one place to another.
Before long, you're paying for plenty of technology while humans are still doing the connecting.
This is where operational thinking matters. The question isn't how many tools you have, it's whether the tools, processes, and people work together in a way that makes running the business easier. Sometimes you need new software. Sometimes you need to stop buying software and fix the process underneath it.
Nobody is quite sure who owns what
"We" is a dangerous project owner.
"We need to update the process." "We should get the event sorted." "We're implementing the new platform."
Who is we?
When responsibility is shared vaguely, work can look busy without actually progressing. As businesses grow, ownership needs to become more explicit. People need to know what they're responsible for, what decisions they can make, and when something needs escalating. This applies to everyday operations and projects. Clarity removes unnecessary chasing.
You're doing work you should have stopped doing months ago
Founders and directors are often the ones continuing to carry tasks simply because they've always carried them.
You might still be manually sending something that could be automated, approving a routine decision someone else could own, updating a spreadsheet nobody really needs, or completing admin that made perfect sense when you had five clients and considerably less sense now.
Growth adds work, but it should also trigger subtraction. As the business changes, it's worth asking what needs to stop, simplify, automate, delegate, or disappear entirely. Otherwise, growth becomes an exercise in piling new responsibilities on top of old ones.
Everyone is busy, but you're not sure what's moving forward
Busyness and progress are annoyingly easy to confuse.
Your calendar is full, Slack is pinging, there are plenty of meetings and everyone has a list. Yet the projects that are supposed to improve the business keep drifting.
This usually signals a prioritisation problem, an ownership problem, or both. A growing business needs a clearer distinction between running the business and changing the business. Both matter. If all available capacity is consumed maintaining today, there's very little left for building tomorrow.
You know something needs to change, but you can't see it clearly anymore
Sometimes you're simply too close to the business.
You've built the processes, lived through every workaround, and know why each odd little decision was made. That context is valuable, but it can also make it harder to see what no longer makes sense.
An external perspective can help separate symptoms from the actual problem. You might think you need new software when the real issue is a broken workflow. You might think you need another employee when a project actually needs temporary ownership. You might think your team isn't communicating when responsibilities were never clearly defined in the first place.
The first solution you identify isn't always the problem you need to solve.
What should you do when your business has outgrown the way it works?
Start by resisting the urge to fix everything at once.
Trying to overhaul systems, roles, software, processes, and every delayed project simultaneously is a fantastic way to create a new project called "why is everyone losing their minds."
Work out what's causing the most headaches or holding back the most important outcome. Then decide whether it's an operational issue, a defined project, or a combination of both.
Operations is the ongoing way the business works. Projects are temporary pieces of work designed to change, build, or deliver something. They interact constantly. If your client onboarding is broken, fixing it may become a project. Once the new onboarding process is implemented, it becomes part of your operations.
Your business isn't supposed to run exactly as it did at the beginning
The scrappy stage of building a business is useful. You learn quickly and make decisions without fourteen approval layers. You find cheap solutions and make things work.
The problem starts when temporary workarounds quietly become permanent infrastructure.
If you're working harder than ever but the business feels more difficult to run, don't automatically assume the answer is more hours, more people, or more software. The way you get shit done may simply need to change.
If you're not sure what needs fixing first, a free 20-minute Stand Up call is where we work out what deserves your attention and whether it needs an In-Haus Day or a full project. You don't have to diagnose your own business before asking for help.
Before you go, have a sticky beak at what we can work on together.
Yap again soon, Blair
