When something isn't working in a business, the first instinct is usually to look at the people.
The wrong hire. The underperforming manager. The team that isn't stepping up. It's a natural diagnosis — and sometimes it's correct.
But in founder-led businesses, the more common cause is structural. The systems haven't been redesigned to match where the business is now. The processes that worked at £200k are still running at £1.5m. The ways of doing things that made sense when the founder was doing everything haven't been updated now that there's a team.
The people aren't the problem. The design is.
The difference between a people problem and a systems problem
A people problem resolves when you change the person. A new hire, a performance conversation, a restructure of the team.
A systems problem persists regardless of who's in the role. You hire someone new and within three months they're exhibiting the same behaviours as the person before them — escalating the same decisions, making the same mistakes, needing the same level of involvement from you.
That's not a coincidence. That's a system producing the result it was designed to produce.
If the same problems keep appearing with different people, the system is the problem.
Signs the structure needs redesigning
The same decisions keep coming back to you If your team is regularly escalating decisions that feel like they shouldn't need you, the issue isn't their confidence or capability. It's that they don't have a clear framework for what they're authorised to decide. That's a design problem — and it stays until the decision structure is made explicit.
New people take months to become effective If every new hire has a long ramp period where they're heavily dependent on you or senior team members, the knowledge isn't in the systems. It's in the people who've been there longest. That's a Knowledge Chain problem — and it creates fragility every time someone leaves.
Quality depends on who does the work If the output varies significantly depending on which team member handles it, the process isn't defined well enough to produce consistent results. The quality is in the people, not the system. That works until the good people leave.
Growth means more of your time, not less If every step up in revenue requires more of your personal involvement rather than less, the business hasn't been designed to scale. You've built something that gets more demanding as it gets bigger — which is the opposite of what a scalable model does.
Your absence causes problems If being unavailable for a week — on holiday, ill, or simply unreachable — creates a noticeable dip in output or a queue of decisions, the business is running on your availability. That's not a team problem. That's a structural dependency.
Clients expect to deal with you personally If clients regularly ask for you specifically — not the business, not the team — the relationship has been built on a person rather than an institution. That's fine when you're starting out. At scale, it creates a ceiling on how many clients you can serve and a risk when you eventually step back.
The Optional Founder Newsletter
Enjoyed this? Get more in your inbox.
Practical frameworks for removing yourself as the bottleneck — straight to your inbox, no fluff.
Why systems don't get redesigned
The reason most business systems go unredesigned isn't laziness or oversight. It's that they still work.
A process that produces acceptable results doesn't trigger the alarm. It just keeps running. Nobody questions a system that's delivering — even if it's delivering below what it could, or keeping the founder more involved than they need to be.
"They just work" is the most expensive phrase in business.
The redecorating analogy is useful here. We update our offices, our branding, our websites — physical and visible things that can look dated. But the processes running the business are invisible. They don't look dated even when they are. So they don't get touched.
Until something breaks — or until someone looks at the business from the outside and asks why it works the way it does.
What a redesign actually involves
Redesigning business systems isn't a process of starting from scratch. It's a structured review of what exists, what it's producing, and whether it matches where the business needs to go.
In practice that means:
- Mapping which processes exist and where the decision points are
- Identifying which steps require the founder and whether they need to
- Moving institutional knowledge out of people's heads and into documented systems
- Using AI to handle the routine operational loops that currently consume human time
- Building explicit decision authority at every level so the team can act without escalating
The goal isn't perfection. It's removing the founder from the parts of the business that don't need them — so their time and attention goes to the parts that do.
Start with a diagnostic
Before redesigning anything, it helps to understand which systems are creating the most dependency and costing you most.
The 12 Chains Audit maps your business across twelve specific structural dependencies, shows you which are most active, and gives you a prioritised starting point. It takes less than five minutes and it's free.