Time to review your support structure?

Growth is generally talked about as though every part of it is wonderful.

More clients, more income, more enquiries and more opportunities are usually exactly what we've been working towards. They're the things we celebrate, post about and use as evidence that the business is moving in the right direction.

And of course, they are good things.

But growth has another side.

As the business grows, everything around it becomes more complex too.

More customers mean more communication. More services create more processes. More people require more coordination. More money brings more financial management. More activity creates more decisions.

Yet while all of that is changing, the infrastructure behind a business often doesn't change at the same speed.

I've seen businesses grow significantly while still relying on one person's inbox, a spreadsheet somebody created years ago, processes nobody has ever documented and a founder who is somehow expected to remember absolutely everything.

For a while, that can work surprisingly well.

People create workarounds. Somebody remembers what needs doing. Another column gets added to the spreadsheet. The founder answers another question because it's quicker than explaining where the information lives.

Nothing feels sufficiently broken to warrant changing it.

Until suddenly it does.

Your business may not have become harder

Sometimes, the infrastructure simply hasn't caught up.

I think that's an important distinction because when a growing organisation starts feeling stretched, one of the most common reactions is:

"We need another person."

Maybe you do.

There absolutely comes a point when a business needs more capacity.

But before adding another person, I'd want to understand what's actually causing the pressure.

Is there genuinely too much work for the people available?

Or is the right work sitting with the wrong people?

Are responsibilities clear?

Is a poor process creating unnecessary administration?

Are two people accidentally doing different parts of the same job?

Is important information sitting in somebody's head or inbox?

Could something repetitive be automated?

Is there work being done simply because nobody has stopped to ask whether it still needs doing?

Those are very different problems.

And they don't all require another employee.

More people don't automatically create more capacity

This is something growing organisations can learn the hard way.

If you add another person to a business without understanding the underlying problem, you can simply add another layer of complexity.

That person needs information. They need access to systems. They need to understand processes, responsibilities and expectations. They need to know what decisions they can make and when something needs escalating.

If the structure around them isn't clear, questions inevitably start flowing back towards the owner or leadership team.

Suddenly you've employed or outsourced to somebody because you wanted more capacity, but you've created another person you need to manage.

That's why I don't think the starting point should be:

"Who do we need?"

I think it should be:

"What does the business need to be able to do?"

The difference sounds small, but it completely changes the conversation.

Think capability, not just headcount

Let's say marketing isn't happening consistently.

Your immediate response might be to recruit a marketing person.

But first I'd want to understand what you actually need.

Do you need somebody to create a marketing strategy?

Do you already have the strategy but need somebody to implement it?

Do you need copywriting?

Social media?

Email marketing?

Website support?

Campaign management?

Reporting and analysis?

Those are different capabilities and they don't necessarily need to sit with one full-time person.

The same applies elsewhere in the business.

"We need help with operations" could mean better systems, project management, administration, CRM support, process improvement or somebody taking responsibility for coordinating several moving parts.

"We need more admin support" might actually reveal that a broken process is creating three times as much administration as it should.

That's why diagnosis should come before resourcing.

Understand the requirement first.

Then decide the most sensible way to create the capability.

Growing businesses have more options than ever

This is where things have changed enormously for SMEs.

The answer no longer has to be another permanent employee.

You might employ someone.

You might use a freelancer for a specific piece of specialist work.

You might outsource an ongoing function.

You might use fractional support to access expertise you need regularly but don't need full-time.

You might bring in a consultant to help diagnose a problem or provide strategic direction.

You might automate a repetitive process.

AI might allow an existing team member to complete certain work much more efficiently.

Or, increasingly, the right answer might be a carefully designed combination of several of those.

That's not about avoiding employment. Employees can provide continuity, knowledge and capability that are enormously valuable to an organisation.

It's about not assuming employment is the only way to create capacity or access expertise.

This is where strategic outsourcing looks different

I think outsourcing is still sometimes misunderstood as simply finding somebody else to do the jobs you don't have time for.

There is absolutely value in handing over tasks. But good outsourcing can be much more strategic than that.

Used properly, outsourcing can give an organisation access to skills it couldn't justify employing full-time. It can provide additional capacity during a busy period, bring specialist expertise into a project or strengthen an existing internal team.

It can also give a growing organisation flexibility.

Perhaps you need regular administration every week, marketing expertise around particular campaigns and project management for three months while something significant is being delivered.

You don't necessarily have three jobs there.

You have three capability requirements.

And they may be best solved in three different ways.

That's why at Ducks In A Row, we don't begin by trying to fit every client into a predetermined service.

We start by looking at the organisation.

What's happening?

Where is the pressure?

What's getting stuck?

Where is expertise missing?

What's taking up too much senior time?

What could work better?

Only then can you have a useful conversation about the support required.

Your most expensive people shouldn't be doing the cheapest work

There's another thing I'd look at when a growing business tells me it needs more people.

What is everybody currently spending their time doing?

It's surprisingly common to find highly skilled people carrying out work that absolutely needs doing but doesn't require their expertise.

A founder spends hours updating systems.

A senior manager is manually pulling together information that could be automated.

A specialist is organising diaries or chasing routine paperwork.

It's happened because they know how to do it and they're there.

Ten minutes here and twenty minutes there doesn't feel significant.

But multiply it across a week, a month and an entire organisation and suddenly a large amount of expensive capacity is being used in the wrong place.

Before adding more people, make sure you're using the capability you already have properly.

Sometimes the capacity you're looking for already exists.

It's simply buried underneath the wrong work.

Don't automate a bad process either

Technology deserves a mention here because automation and AI are increasingly part of the resourcing conversation.

If somebody is manually completing the same predictable task every week, there may well be a smarter way to do it.

But the same rule applies.

Understand the problem before choosing the solution.

Automating an inefficient process simply allows you to do the wrong thing faster.

Similarly, outsourcing a broken process means somebody else is now responsible for navigating the same broken process.

Sometimes the best thing you can do is stop and redesign how the work happens before deciding who — or what — should do it.

Would you build your business this way today?

Businesses rarely become inefficient overnight.

They evolve.

A temporary workaround becomes permanent. A spreadsheet gains another tab. Somebody takes responsibility for something because they happened to be available. A process designed for twenty customers is still being used for two hundred.

Nobody deliberately designed it that way.

It simply grew.

That's why one of the most useful questions you can periodically ask is:

If we were designing the support structure for this business from scratch today, would we build it this way?

Would the same people be doing the same work?

Would you use the same systems?

Would responsibilities sit in the same places?

Would every task still exist?

Would you employ the same roles?

What would you outsource?

What would you automate?

And where would you deliberately retain human expertise?

You don't need to tear the business apart every six months.

But growth changes what an organisation needs.

Your support structure should be allowed to change with it.

Before you add another person, do this

If your business currently feels stretched and you're thinking about recruiting or outsourcing, take an hour before you start looking for people.

Write down the areas where the business is struggling.

Then, for each one, ask:

What is actually causing this?

Is it capacity?

Expertise?

A poor process?

Unclear ownership?

A system that no longer works?

Work sitting with the wrong person?

Something repetitive that could be automated?

Then ask:

What capability would solve it?

Only after that should you decide how to resource it.

Employee.

Freelancer.

Outsourced support.

Fractional expertise.

Consultancy.

Technology.

Or a combination.

That's how growing organisations can start building support strategically rather than continually adding people to solve the latest problem.

Your business may have grown brilliantly.

Just make sure the structure supporting it hasn't been left three years behind.