Outgrowing your structure

What worked at 12 people stopped working at 25.

The informal habits that run a 12-person business – everyone does everything, decisions happen in passing and the founder holds it all together – quietly break somewhere around 25 people. You didn’t get worse at running the business. The business got bigger than the way you run it, and the fix is design, not more effort or more hires.

By Simon Wakeman, Principal Consultant & Fractional COO
· 5 minute read

The team is bigger and better than it has ever been. The work is harder to get done than it has ever been. Meetings multiply, the same questions keep coming back to you and things you thought were handled turn out not to be. Nothing dramatic went wrong. It just stopped being easy.

That pattern is predictable, and it’s fixable. It’s not a talent problem or an effort problem. It’s a business operating system problem.

Why does a business that ran fine at 12 people start creaking at 25?

Because at 12 people, you had a system. It just wasn’t written down.

Everyone sat within earshot. Context travelled by overhearing. Roles were blurry, but it didn’t matter, because whoever noticed a gap filled it. And the founder was in almost every conversation, so decisions were quick and the joins between people were invisible.

That system runs on proximity and the founder’s attention, and both run out. The arithmetic alone is brutal. Twelve people can form 66 different pairs. Twenty-five people can form 300. Every extra person adds conversations you’re not in, handoffs nobody designed and assumptions that never get checked.

The way you run things was simply never designed to carry this many people. Andrew McBarnett, group financial director at Lucid Group, makes the point on The Handbook operations podcast. Growth itself is rarely what trips a business up. Failing to absorb it is.

Why didn’t anyone notice it happening?

Because growth arrives one hire and one client at a time. There’s no single day when it breaks. Each new starter is absorbed, each new client is squeezed in, and the strain builds so gradually that it feels normal.

What usually hides it is heroics. A few capable people step in, again and again, to catch what’s falling. They keep the business running, and in doing so they mask how much the structure has stopped working. Meanwhile resentment quietly builds among everyone who isn’t a hero.

What are the signs you’ve crossed the line?

Founders tend to describe the same handful of frustrations:

  • Work gets done twice, or not at all, because two people each assumed the other had it.
  • Things fall through the cracks that everyone thought someone else owned.
  • Capable people won’t decide. They’ve been told they own things, but nobody said where their authority starts and stops.
  • Everyone communicates constantly, yet nobody seems to know what’s going on.
  • New starters take months to be useful, because how things work lives in a few people’s heads. (More on that in when your best person leaves, so does the process.)
  • Everything still ends up with you. You’re the connective tissue between teams that don’t quite connect.

These look like separate problems, but they’re usually one condition: the business has outgrown its design. Treat them one at a time and you’ll be firefighting for years.

Won’t hiring more people fix it?

It’s the most common response, and it rarely works. If the real issue is unclear ownership, missing rhythms or scattered information, a new hire walks straight into the same confusion. You’ve added capacity, but you’ve also added more handoffs, more meetings and more people who need context they can’t get.

Founders often read a structure problem as a capacity problem. The tell is that everyone is busy, yet the work that matters most still sits in the gaps between teams.

It isn’t an attitude problem either. When you hear yourself say “nobody takes ownership”, the cause is far more often a lack of clarity about who owns what than a lack of drive.

What actually needs to change between 12 and 25?

Three things, and they need to change together: your people, practices and technology.

People: from implied roles to explicit ownership. At 12, roles are a loose agreement. At 25, the workflows that matter – winning work, delivering it, getting paid – each need a named owner who is accountable for the whole thing, end to end. And everyone needs to know which decisions are theirs to make without asking.

Practices: from ambient chat to a deliberate rhythm. Overhearing no longer spreads context, so you need a drumbeat that does it on purpose. That means a weekly leadership meeting that looks at the same few numbers, a monthly look at priorities and a habit of writing decisions down. It should feel slightly boring, because predictability is the job it’s doing.

Technology: from “ask the person who knows” to one place to look. The spreadsheet everyone understood at 12 people becomes five tools with five versions of the truth at 25. What helps is fewer, connected tools and agreement on which one holds the answer. We cover this in five tools, five versions of the truth.

What can you test in the next month?

Four small checks will show you where the design has slipped, without touching the org chart:

  1. Map one workflow. Pick the process that wins or delivers most of your work and trace how it actually moves. Mark every handoff, every wait and every point where it comes back to you.
  2. Ask three people who owns it. Pick something that keeps going wrong and ask three people, separately, who is responsible. If you get three different answers, you’ve found your first fix.
  3. List the decisions you made this week that someone else could have made. Hand three of them over properly, with clear boundaries on what’s in and out of bounds.
  4. Name your heroes. Write down the two or three people who keep stepping in to catch what’s falling. Then ask them what they’re catching. Each answer points to a gap in the design.

Where should you go from here?

Resist the urge to build everything at once. The goal is the minimum structure that lets people know what’s expected of them and get on with it, not a rulebook. Our guide on how to build a business operating system walks through what to put in place first, and in what order.

If you’d rather see exactly where your business has outgrown itself before changing anything, that’s what the Find diagnostic is for. In 14 days it looks at 262 operational data points across your people, practices and technology and gives you a prioritised roadmap of what to fix first.

Some commonly asked questions from founders…

Why does my business feel harder to run now than when we were smaller?

Usually because the business has outgrown the informal way it was designed to run. At a dozen people, context travels by overhearing and the founder fills every gap. At 25 or more, that stops working, so work duplicates, decisions stall and everything drifts back to the founder. It’s a design problem, not a sign you’ve lost your touch.

At what headcount do founder-led businesses outgrow their structure?

There’s no fixed number, but the strain often shows somewhere between 20 and 30 people and becomes hard to ignore by 50. The exact point depends on how many handoffs your work involves and how much still runs through the founder. The warning signs matter more than the headcount.

Will hiring more people fix it?

Rarely. If the problem is unclear ownership, missing rhythms or scattered information, new hires walk into the same confusion and add more handoffs to it. Capacity is the easy thing to see, so it tends to get the blame. Fix the design first, then hire into roles that are clear.

Do we need a full restructure to fix this?

Not usually. Most businesses need a handful of targeted changes: clear owners for the workflows that matter most, a regular leadership rhythm and one trusted place for key information. Smaller, more frequent adjustments tend to land better than one big reorganisation that everyone dreads.

What’s the first thing to change when we’ve outgrown how we work?

Start with people: make ownership and decision rights explicit for one critical workflow, end to end. Once someone clearly owns the outcome, it becomes obvious which meetings, processes and tools need to change around them. Starting with tools tends to bake in whatever confusion is already there.

How does Mallard help a business that’s outgrown its structure?

Mallard usually starts with the Find diagnostic: 14 days, 262 operational data points across people, practices and technology, ending in a prioritised roadmap. From there, an Improve sprint puts a senior Mallard operator inside the business for three months to fix the biggest bottleneck alongside your team.

Stop being a bottleneck in your own business

Book your free 30 minute
founder review call