Can My Business Afford to Hire Another Employee

Adam Fox • 29 September 2026

Your business can afford to hire another employee when the full cost of employing them can be carried comfortably through the period before they become productive, and the capacity, margin, management leverage or risk reduction they create is worth more than that cost.

That is the useful answer.

Not:

"Do we have £35,000 for a £35,000 salary?"

Because a £35,000 employee does not cost the business £35,000.

And not:

"We've got loads of work, so surely we need someone."

Because being busy does not automatically mean another employee is commercially sensible.

Before hiring, I would want to know:

What problem is this person solving?

What is their real annual employment cost?

What other costs arrive with the role?

How long before they become genuinely productive?

What additional capacity will they create?

What gross profit will that capacity generate or protect?

What happens to cash before the return arrives?

What happens if demand is 20% lower than expected?

And what does it cost the business not to hire them?

Only then can you answer the affordability question properly.

Salary is only the beginning

Suppose you are considering a £35,000 employee.

The obvious calculation is:

Salary: £35,000.

Done.

Except in the 2026/27 tax year, most employers pay Class 1 employer National Insurance at 15% on earnings above the £5,000 annual Secondary Threshold. Eligible employers may be able to reduce their overall employer NIC bill through the £10,500 Employment Allowance, but you should not automatically assume every pound of employer NI attached to a new employee disappears.

For a straightforward £35,000 salary, ignoring special NI categories:

Employer NI is approximately:

£35,000 minus £5,000 = £30,000.

15% of £30,000 = £4,500.

Already:

£39,500.

Then there is pension

Under the standard automatic-enrolment minimum, employers generally contribute at least 3% of qualifying earnings for eligible employees. For 2026/27, the qualifying-earnings band remains £6,240 to £50,270 under the usual qualifying-earnings basis.

For that same £35,000 employee:

£35,000 minus £6,240 = £28,760.

3% = approximately £863.

So our £35,000 salary is already approximately:

£40,363 a year

before we have considered anything else.

That is around £3,364 a month in salary, employer NI and minimum employer pension contributions alone.

And that is an illustration, not payroll advice. Your pension scheme, NI category, Employment Allowance position and employee circumstances can change the actual figure.

A £35,000 employee might therefore start at more like £40,000 before they have a laptop

Then potentially add:

Recruitment.

Laptop.

Phone.

Software licences.

Vehicle.

Tools.

Uniform or PPE.

Insurance implications.

Training.

Professional memberships.

Workspace.

Travel.

Management time.

Payroll administration.

Equipment.

Whatever the role actually requires.

For some jobs that addition is tiny.

For others it is enormous.

A salesperson needing a laptop and phone is different from an engineer needing:

A van.

Tools.

Test equipment.

Training.

Certification.

Fuel.

Storage.

The salary tells you very little by itself.

Do not double-count holiday, though

This is a common mistake in rough employment-cost calculations.

Most workers are legally entitled to 5.6 weeks of paid annual leave each year, equivalent to 28 days for somebody working five days a week.

But if you are modelling a salaried employee, their paid holiday is already inside the annual salary.

Do not calculate:

£35,000 salary

plus another 5.6 weeks' salary for holiday.

You would be counting the same pay twice.

The important commercial issue is different:

You pay for 52 weeks but you do not receive 52 weeks of productive working time.

That matters when estimating the employee's real capacity.

Productive capacity is not 365 days

Obviously.

Take out:

Weekends.

Annual leave.

Bank holidays where applicable within the leave arrangements.

Training.

Internal meetings.

Administration.

Potential sickness.

Onboarding.

Other non-productive time.

The exact number varies hugely by role.

The point is that a full-time employee should not be modelled as:

37.5 hours × 52 weeks = all billable or productive capacity.

That is fantasy.

Sick-pay rules changed in April 2026 too

From 6 April 2026, Statutory Sick Pay became payable from the first full day of sickness rather than after the previous waiting period, and the lower earnings threshold for eligibility was removed. For 2026/27, the statutory amount is the lower of £123.25 per week or 80% of average weekly earnings.

Again, I would not attempt to build an imaginary sickness number into every hiring decision.

I would simply recognise:

Employees cost money during periods when output is not available.

That is part of employing people.

So what does the employee really cost?

I would split the answer into four buckets.

1. Direct employment cost

Salary.

Employer NI.

Employer pension.

Any guaranteed commission, allowance or contractual benefit.

2. Role infrastructure

Laptop.

Vehicle.

Tools.

Software.

Phone.

Workspace.

Equipment.

Insurance.

Professional requirements.

3. Acquisition and development

Recruitment.

Onboarding.

Training.

Manager time.

Reduced productivity while learning.

4. Ongoing operating cost

Travel.

Fuel.

Expenses.

Additional administration.

Consumables.

Whatever the role creates.

Now you have something closer to reality.

But cost is only half of the question

Imagine the fully loaded role costs:

£50,000.

Can you afford it?

I still have no idea.

If that employee creates £150,000 of additional gross profit?

Probably a very different answer from a £50,000 employee whose work creates £20,000 of additional value.

Affordability depends on what happens because the employee exists.

Revenue is not the right comparison

This is critical.

New employee costs £50,000.

They allow you to generate £60,000 more revenue.

Brilliant?

Maybe terrible.

What does that £60,000 of revenue cost to deliver?

Materials.

Subcontractors.

Other labour.

Freight.

Commission.

Direct project costs.

If only £18,000 remains after variable delivery costs, the employee has not paid for themselves.

Compare employment cost to gross profit or contribution generated, not simply turnover.

A simple example

Suppose a new technician costs you approximately:

£48,000 fully loaded.

They make it possible to deliver:

£110,000 of additional annual revenue.

That work has a 50% gross margin before the technician's employment cost.

So the additional contribution available is approximately:

£55,000.

Employee cost:

£48,000.

Potential surplus:

£7,000.

Suddenly that hire looks much less spectacular than:

"One employee creates £110,000 revenue."

And we have not yet allowed for:

Ramp-up.

Downtime.

Demand variation.

Additional management.

Potential working-capital requirements.

That does not mean don't hire them.

It means understand the economics.

Now imagine the same employee unlocks £180,000 at a 50% gross margin

Additional contribution:

£90,000.

Employment cost:

£48,000.

Much more interesting.

Same employee.

Same salary.

Completely different business case.

Not every employee directly generates revenue

This is where simplistic calculations break down.

What revenue does your:

Finance Manager generate?

Operations Manager?

Administrator?

HR Manager?

Perhaps none directly.

Still might be incredibly valuable.

You have to calculate capacity released or value protected.

Consider an administrator

Suppose the administrator costs £36,000 fully loaded.

They do not generate sales.

But they remove:

Eight hours a week from the owner.

Five hours from the Operations Manager.

Four hours from Project Managers.

Now what happens with those seventeen hours?

If everyone simply drinks more coffee?

Bad investment.

If that capacity goes into:

Sales.

Customer work.

Management.

Project delivery.

Credit control.

Strategic work.

then the administrator may create significant leverage.

The value sits in the work they release.

Consider an Operations Manager

£70,000 employment cost.

No direct revenue.

But perhaps they:

Release twenty owner hours each week.

Improve utilisation across fifteen people.

Reduce overtime.

Reduce rework.

Improve scheduling.

Develop supervisors.

Allow another £1 million of work to be handled.

The economics may be exceptional.

Or they might do none of those things.

Then they are simply expensive.

Role value has to be connected to actual organisational outcomes.

Ask what the hire unlocks

This is one of the best questions available.

Not:

"What will they do?"

Ask:

What becomes possible because they are here?

More jobs delivered?

More customers served?

Owner leaves delivery?

Manager gets management time back?

Quotes issued faster?

Debtors reduced?

Capacity increases?

Customer retention improves?

Quality problems fall?

Someone needs to be able to articulate the commercial mechanism.

Hire against a constraint

Article #45 covered capacity planning.

This makes the affordability question much easier.

Where is the constraint?

Sales?

Estimating?

Production?

Installation?

Project management?

Administration?

Management?

If the business is constrained by sales, adding another production employee may simply create spare production capacity.

If the business is constrained by delivery, another salesperson could make the problem worse.

Find the pipe that is already full.

Then determine whether another person is the best way to widen it.

Do not employ somebody to solve work you should eliminate

Before approving another salary, ask:

Could we stop the work?

Simplify it?

Automate it?

Fix the process?

Outsource it?

Train somebody?

Reallocate responsibility?

Increase price?

Remove an unprofitable customer?

You do not want to build permanent headcount around preventable inefficiency.

A person is an expensive workaround for a broken process

Imagine Finance needs another employee because somebody spends twenty hours every week manually reconciling data between three systems.

Perhaps the answer is another employee.

Perhaps it is fixing the information flow.

Do that diagnosis before recruiting.

Otherwise growth turns inefficiency into payroll.

Affordability is also about cash, not only profit

This catches growing businesses constantly.

The annual P&L says the employee makes sense.

Great.

But wages are due every month.

When does the extra revenue arrive?

Perhaps you:

Hire in October.

Pay salary October.

November.

December.

January.

Employee is learning.

First significant additional customer work completes in February.

Customer pays sixty days later.

Cash arrives in April.

The business case may be profitable over twelve months and still create a serious six-month cash squeeze.

Article #42 covered this distinction.

Model the cash trough

Before hiring, ask:

When does cash go out?

When does the employee become productive?

When do they generate or release capacity?

When does additional work get invoiced?

When does the customer actually pay?

That sequence matters.

Build a six-month hiring cash forecast

You do not need investment-bank modelling.

Month by month:

Salary.

Employer costs.

Recruitment.

Equipment.

Training.

Expected productive capacity.

Expected additional invoicing.

Expected cash collection.

Then find:

The lowest cash point created by the hire.

Can the business comfortably carry it?

That is a better affordability test than checking today's bank balance.

Never hire because the bank balance looks healthy

£180,000 in bank.

Great.

VAT due.

Corporation tax due.

Supplier payments due.

Project deposits belonging economically to work not yet delivered.

Now perhaps only £40,000 is genuinely free.

The bank balance is not available capital by default.

Use the cash-flow forecast.

Likewise, do not reject a good hire because one month's bank balance looks low

Maybe the business generates strong recurring cash.

Has sufficient facilities.

Healthy margin.

Contracted demand.

The employee will create clear additional capacity.

Affordability is forward-looking.

Not:

"How much cash is there this morning?"

The role needs a runway

A hire should not have to pay for themselves on day one.

That would make almost all recruitment impossible.

Think:

How long can we reasonably invest before expected value appears?

Three months?

Six?

Twelve?

Depends on role.

A senior salesperson may have a long commercial cycle.

An experienced technician may become productive relatively quickly.

A management hire may take months to improve organisational performance.

Know what you are funding.

Ramp-up time is part of the investment

New employee arrives.

Someone must:

Show them systems.

Explain customers.

Train process.

Review early work.

Answer questions.

Correct mistakes.

This means the hire can initially reduce existing team capacity.

Completely normal.

But plan for it.

This is particularly important when the team is already overloaded

You wait until everybody is drowning.

Then hire.

Excellent.

Who trains them?

The same overloaded people.

Onboarding becomes rushed.

New employee struggles.

Existing team becomes busier.

Owner says:

"Hiring them has actually made things worse."

For a while, yes.

That is why Article #45 argued for recruiting before desperation where forward demand justifies it.

What if the hire replaces subcontracting?

That gives you a useful comparison.

Suppose subcontractors currently cost:

£100,000 a year.

Permanent employee costs:

£55,000.

Obvious?

Not necessarily.

The subcontractor might include:

Their own equipment.

Vehicle.

Insurance.

Training.

Holiday cover.

Management independence.

And perhaps you only need them nine months a year.

Compare total models.

But recurring subcontractor expenditure can absolutely reveal that permanent internal capacity deserves investigation.

What if the hire replaces owner labour?

This is often badly modelled because owner time is treated as free.

Suppose you personally perform fifteen hours of technical work every week.

Hire someone.

They absorb it.

Company now has additional salary cost.

What did it gain?

Fifteen owner hours.

What is that worth?

Depends entirely on what you do with them.

If those hours produce:

Higher-value sales.

Management.

Business improvement.

Strategic work.

Or a more sustainable life that allows you to lead better?

Real value.

If you immediately fill them with another fifteen hours of low-level work?

Less useful.

Your own unpaid overtime can hide an unaffordable operating model

The company appears profitable because you supply:

Twenty extra hours a week.

No additional payroll.

That is owner subsidy.

Ask what the P&L would look like if the business had to employ people to perform all the work currently supplied by the owner.

Interesting exercise.

Sometimes:

"We can't afford another employee."

really means:

"The business only works financially while I provide a large amount of free labour."

That is a different problem.

Another employee should not merely preserve an unprofitable model

Suppose you need another technician because work is booming.

But margins are so weak that adding the technician makes no money.

You may not have a staffing problem.

You may have a pricing problem.

Do not hire faster to deliver more unprofitable work.

That is an impressive way to become poorer at scale.

Calculate the break-even contribution

A simple management calculation:

Fully loaded annual employee cost

divided by

gross contribution percentage from the additional work

equals

roughly how much additional revenue is required to cover the employment cost.

Example:

Fully loaded employee cost:

£50,000.

Additional work contributes 40p from every £1 of revenue after relevant variable costs.

£50,000 ÷ 40% = £125,000 additional revenue required just to cover that employment cost.

That is much more useful than saying:

"We only need them to generate £50,000."

No.

You need enough contribution to cover £50,000.

Add a margin of safety

Do not build the business case so tightly that everything has to go perfectly.

Employee must reach 100% expected productivity.

Pipeline must convert exactly as forecast.

Nobody can be sick.

No customer can delay.

No costs can rise.

That is not a plan.

That is hope with a spreadsheet.

Ask what the economics look like if:

Demand is 20% lower.

Employee takes longer to ramp.

Margin is slightly weaker.

Start date changes.

Customer payment is delayed.

Can the company still carry the role?

Use three scenarios

Downside

Demand weaker than expected.

Ramp slower.

Expected

Realistic central forecast.

Strong

Demand converts well.

Then look at:

Profit.

Cash.

Capacity.

Under all three.

You do not need a Monte Carlo simulation.

You need to stop pretending only one future exists.

Ask: how reversible is the decision?

Employment is not a casual monthly subscription.

You are hiring a human being.

There are:

Contractual responsibilities.

Employment rights.

Management obligations.

Potential redundancy or dismissal implications later.

That does not mean be terrified of recruiting.

It means treat permanent employment as a genuine commitment.

Probation helps assess fit, but it is not a risk-free trial

Acas describes probation as an opportunity for both employer and employee to assess performance, skills and organisational fit. There is no legal requirement to use a probation period, but where you do, expectations, reviews and fair processes should be clear.

Do not think:

"We'll hire them and if revenue disappears we'll just fail probation."

Probation should assess the person.

It is not a substitute for a viable workforce plan.

Minimum wage matters to the entire pay structure too

From 1 April 2026, the National Living Wage for workers aged 21 and over is £12.71 an hour. The 18-to-20 rate is £10.85, while the 16-to-17 and apprentice rates are £8.00 subject to the relevant rules.

For many established SMEs, proposed salaries will sit well above minimum wage.

But rises at the bottom can create wider wage compression.

If an entry-level rate rises, more experienced employees may expect the differential above it to be maintained.

The cost of one new hire can therefore occasionally have implications beyond that single salary.

Do not calculate affordability using salary alone when comparing candidates either

Candidate A:

£35,000.

Candidate B:

£40,000.

Owner chooses A because:

£5,000 cheaper.

But Candidate B may:

Reach productivity faster.

Require less management.

Generate better output.

Develop others.

Handle customers independently.

The cheapest employee can be considerably more expensive.

Look at value.

Equally, do not use "quality costs money" to justify any salary

Higher salary does not guarantee better performance.

Build the role.

Define the outcomes.

Recruit against evidence.

Know what excellent performance is worth.

Then establish a sensible remuneration range.

What if the hire is a salesperson?

Do not use revenue target alone.

Model:

Expected ramp period.

Pipeline creation.

Conversion.

Gross margin.

Commission.

Sales cycle.

Customer acquisition cost where relevant.

Delivery capacity.

Working capital.

A salesperson who wins £1 million of terrible work can hurt the business.

Sales hiring should be linked to profitable, deliverable revenue.

What if the hire is operational?

Model capacity.

How many additional:

Jobs?

Hours?

Units?

Projects?

Can the rest of the business absorb them?

If production adds 25% capacity but Project Management is already full, the theoretical extra output may never become revenue.

Capacity has to work end to end.

What if the hire is administrative?

Measure capacity released.

Who currently does the work?

How many hours?

What higher-value work becomes possible?

You may discover the role is one of the best investments available.

Or that you are proposing a full-time employee for fifteen hours of genuine work.

Then consider part-time or outsourcing.

What if the hire is management?

Measure organisational leverage.

Number of people affected.

Owner hours transferred.

Decision load transferred.

Performance improvement.

Capacity planning.

Reduction in rework.

Manager development.

Customer impact.

Management hires often need a more thoughtful business case because their value appears across the system rather than on one invoice.

Could the role be part-time?

Sometimes that is the right answer.

If you have:

Twenty hours of stable recurring work,

why immediately create a forty-hour role?

Part-time can be useful where:

Workload genuinely supports it.

Suitable talent is available.

Role design remains coherent.

Do not automatically assume every organisational gap requires one full-time person.

Could you outsource it?

Bookkeeping.

Marketing.

IT.

Specialist HR.

Design.

Certain administration.

Technical specialists.

Sometimes external provision creates access to capability without permanent headcount.

Other times outsourcing becomes expensive, fragmented and weakly integrated.

Compare.

The question is:

Which model best fits the required capability and demand pattern?

Could you recruit an apprentice or develop internally?

Possibly.

But do not treat apprentice as:

Cheap employee.

Apprentices require:

Training.

Support.

Development.

Time.

They can create excellent long-term capability where the role and organisation support it.

The economics are different from hiring an experienced employee ready to deliver quickly.

Can the manager actually absorb another employee?

This gets forgotten.

Team Manager already has:

Twelve direct reports.

Two vacancies.

No one-to-ones.

Constant firefighting.

Owner says:

"We're giving you another three people."

Great.

Did labour capacity increase?

Yes.

Did management capacity?

No.

Every hire creates some management requirement.

Model that too.

Recruitment can expose another constraint

You think you need:

Employee.

During the business case you discover:

No manager.

No process.

No workspace.

No training capacity.

No clear role.

Excellent.

Better to discover before the person arrives.

What does "afford" actually mean?

I would use five tests.

Test 1: Payroll affordability

Can the business pay the full employment cost?

Not just salary.

Test 2: Cash affordability

Can it carry the role before the return arrives?

Test 3: Commercial affordability

Does the role generate or protect sufficient gross profit or organisational value?

Test 4: Operational affordability

Can you onboard, manage and use the person effectively?

Test 5: Downside affordability

Can the business survive if the forecast is wrong?

Pass all five and the case becomes much stronger.

The sixth question is whether you can afford not to hire

This deserves equal weight.

Perhaps not hiring means:

£70,000 annual overtime.

£100,000 subcontractor spend.

Turning away £500,000 of profitable work.

Owner permanently overloaded.

Existing employees leave.

Customers wait too long.

Manager cannot manage.

Growth stops.

Then not hiring has a cost too.

The cost of vacancy is easy to ignore because nobody sends you an invoice for it

Nobody invoices:

Lost opportunity: £42,000.

Owner bottleneck: £18,000.

Burned-out manager: £25,000.

Customer lost due to lead time: £60,000.

Those costs still exist.

The fact that they are difficult to see does not make zero the correct number.

Compare Hire versus Don't Hire

I would literally put the two options side by side.

Hire

Salary.

Employer costs.

Equipment.

Recruitment.

Training.

Cash trough.

Expected additional contribution.

Capacity created.

Risks.

Don't Hire

Overtime.

Subcontracting.

Lost sales.

Owner hours.

Lead-time impact.

Customer risk.

Staff retention risk.

Growth constraint.

Alternative solutions.

Now you are choosing between two commercial scenarios.

Not between:

Spend money

and

spend nothing.

Build a one-page hiring business case

You do not need bureaucracy.

For any meaningful hire, answer:

Why do we need the role?

What constraint does it solve?

What will it cost fully loaded?

What one-off costs exist?

When does the employee become productive?

What capacity or value does it create?

What gross profit does that generate or protect?

When does the cash return arrive?

What happens in the downside case?

What is the alternative to hiring?

What happens if we wait six months?

That is enough for a serious decision.

Then get your accountant or FD to challenge the assumptions

Particularly for a material hire.

Not:

"Can I afford someone?"

with no context.

Give them:

Salary.

Expected costs.

Revenue assumptions.

Gross margin.

Cash forecast.

Ramp period.

Ask them to challenge it.

The business owner owns the decision.

Good financial information improves it.

An illustrative £35,000 hire

Let's pull the earlier example together.

Salary:

£35,000.

Illustrative employer NI at current standard 2026/27 rate:

Approximately £4,500.

Illustrative minimum employer pension on the standard qualifying-earnings basis:

Approximately £863.

Direct employment cost:

Approximately £40,363.

Then add your actual:

Recruitment.

Equipment.

Software.

Vehicle.

Training.

Insurance.

Other role-specific costs.

If those add £4,000 in year one:

Year-one cost:

Roughly £44,363.

Now perhaps the employee creates:

£90,000 additional annual gross contribution once fully productive.

Strong-looking case.

But if they take six months to ramp?

Year-one value might be much lower.

Cash timing matters.

This is why one salary figure cannot answer the question.

Employment Allowance can change the employer-NI cash picture

For 2026/27, eligible employers can reduce their employer Class 1 National Insurance liability by up to £10,500 through Employment Allowance. Eligibility rules apply, and connected companies can only claim the allowance through one company in the group.

If your business qualifies and still has allowance available, the marginal NI cash impact of a hire may therefore be different from the simple calculation above.

Ask your accountant or payroll provider.

Do not just delete employer NI from every future hiring model because you once heard Employment Allowance exists.

Employer NI remains a meaningful cost above the allowance

The standard employer Class 1 rate for 2026/27 is 15% above the £5,000 Secondary Threshold.

This is one reason salary budgets built several years ago can badly understate current employment costs.

Keep your models current.

Build a 12-month forecast, not only an annual figure

Annual totals hide timing.

Month 1:

Recruitment and equipment.

Month 2:

Salary, low output.

Month 3:

Salary, more training.

Month 4:

Useful output begins.

Month 5:

Invoice.

Month 7:

Cash arrives.

That hire can look highly profitable over two years and still need significant funding in the first six months.

Know the bridge.

Consider a 24-month case for senior hires

Operations Manager.

Senior salesperson.

Commercial Manager.

These roles may require substantial ramp time.

Year one alone can make a good hire look weak.

But do not use:

"They'll pay off eventually."

as an excuse for vague economics either.

Define expected milestones.

What should change by:

90 days?

Six months?

Twelve months?

Use trigger points before committing

Perhaps your financial model says another employee becomes sensible when:

Backlog exceeds six weeks.

Contracted workload reaches a threshold.

Pipeline converts.

Subcontractor spend reaches a certain level.

Utilisation remains above an agreed level.

Then set the trigger.

Do not continually revisit the decision emotionally every Friday.

Be careful waiting for absolute certainty

Article #45 matters again.

If recruitment plus notice plus onboarding takes four months, waiting until the business is already short of one full person means overload will continue for at least four more months.

Affordability and timing need considering together.

The financially safest-looking moment to hire can be operationally far too late.

There is a difference between affordable and comfortable

Perhaps the business can technically pay the salary.

But cash buffer becomes tiny.

One late-paying customer creates stress.

Any downturn causes trouble.

I would want to know:

How much headroom remains after the hire?

You do not need zero risk.

Business has risk.

You need to understand what you are accepting.

Growth often consumes cash before producing it

New employee.

More jobs.

More materials.

More work in progress.

More debtor balance.

Turnover increases.

Bank balance falls.

Perfectly possible.

This is why staffing plans should sit alongside cash-flow planning.

Not separately.

Do not make the employee carry an impossible payback expectation

Another mistake.

"We hired you for £45,000 so you need to bring in £45,000."

Wrong measure.

Or:

"You need to pay for yourself within four weeks."

Perhaps impossible.

Set targets appropriate to what the role controls.

A technician controls productive output and quality.

A manager controls operational outcomes.

An administrator controls process and support capacity.

Build sensible accountability.

Hiring someone should change the organisation

This is particularly true when the reason is owner workload.

If you hire another person and keep:

The same decisions.

The same tasks.

The same customers.

The same approvals.

The same problems.

then where exactly is your capacity coming from?

Write the transfer.

What moves?

Do not refill the capacity immediately

Employee takes fifteen hours from you.

Within two weeks you accept:

Three new committees.

Two pointless meetings.

Another operational project.

Owner back to fifty-five hours.

The hire still helped the business.

But you destroyed the personal leverage.

If reducing owner dependency was part of the case, protect the released time.

Sometimes the correct answer is: no, you cannot afford them yet

That is okay.

Then ask:

What would have to become true?

More margin?

More contracted revenue?

Better cash buffer?

Higher prices?

Reduced overhead?

Less debt?

Customer deposit?

Different working-capital model?

Part-time first?

Outsource temporarily?

Now:

"We can't afford another employee."

becomes a planning problem.

Not a dead end.

Sometimes the correct answer is: you cannot afford not to

Also possible.

The owner is doing two jobs.

Profitable work is being refused.

Lead times are damaging customers.

Existing staff are exhausted.

The business case works.

Cash forecast supports it.

Yet the owner delays because adding a £50,000 salary feels frightening.

That fear is understandable.

But delay can be more expensive than the salary.

Use evidence.

Do not use courage as a substitute for evidence either

"You've got to invest to grow."

True sometimes.

Also an excellent phrase for bankrupting yourself.

Investment should have:

Reason.

Model.

Assumptions.

Downside.

Runway.

Then make a commercial judgement.

A 30-minute first-pass affordability test

You could assess a proposed hire surprisingly quickly.

Write:

Salary.

Employer NI.

Pension.

Role-specific annual cost.

One-off setup cost.

Expected ramp period.

Expected additional gross profit or capacity released.

Cash available.

Monthly cash forecast.

Worst credible downside.

Cost of doing nothing.

If the numbers look obviously terrible?

Stop.

If obviously compelling?

Investigate properly.

If close?

Improve the assumptions.

A stronger 90-day approach if the decision is less urgent

Month 1: Measure the constraint

Track:

Workload.

Overtime.

Subcontractors.

Backlog.

Lost work.

Owner time.

Management load.

Month 2: Build the economics

Role.

Full cost.

Capacity.

Gross contribution.

Cash.

Downside.

Alternatives.

Month 3: Prepare

Define outcomes.

Recruitment route.

Onboarding.

Handover.

Decision authority.

Trigger.

Then move when the evidence supports it.

That produces a far better hire than:

"Everyone's drowning. Put something on Indeed tonight."

How Evolve approaches hiring affordability

If an owner asks me:

"Can I afford another employee?"

my first answer is normally:

"Let's work out what you mean by afford."

Salary?

No.

We need:

True employment cost.

Cash timing.

Expected return.

Capacity released.

Alternative cost.

Then we need to understand the business problem.

Why this employee?

Why now?

What happens if we don't?

Could something cheaper solve it?

Will you genuinely transfer the work?

That is the commercial conversation.

Your accountant can help validate the numbers.

Your HR adviser can help with employment structure and obligations.

I am interested in whether the business case itself makes sense.

The best hiring decisions solve more than today's pain

A strong hire can create:

Capacity.

Capability.

Management depth.

Resilience.

Customer improvement.

Owner freedom.

Future growth.

That is why the answer cannot be reduced to:

Salary divided by expected revenue.

People change systems.

Good ones create leverage.

Poorly designed roles create cost.

So, can your business afford to hire another employee?

Start with the full cost.

Not salary.

Include employer NI, pension and role-specific costs.

Understand paid time that does not create productive capacity.

Estimate recruitment and onboarding.

Model ramp-up.

Then identify what this person creates.

Additional contribution?

Management leverage?

Owner capacity?

Reduced subcontracting?

Improved customer delivery?

Risk reduction?

Compare that value with the cost.

Then model cash timing.

Not just annual profitability.

Stress-test the assumptions.

Compare hiring with doing nothing.

And make sure the business can survive the downside if the forecast is weaker than expected.

A £50,000 employee is not expensive if they create £120,000 of sustainable additional value.

A £30,000 employee is extremely expensive if the business never really needed the role.

The question is not:

"Can we pay another salary?"

It is:

"Will committing this cash to this person create a stronger business than the other things we could do with it?"

That is the hiring decision.

< Older Post

Newer Post >

Something in your business needs to change?

You probably already know more than enough to keep reading about it.

If you want an experienced outside perspective to help you work out what’s really getting in the way — and what to do about it — let’s have a conversation.

Talk About My Business

Learn more

Specialist ground crews performing distinct roles around one aircraft in bright daylight.

Role Clarity in a Growing Small Business, Who Actually Owns What?

by Adam Fox • 29 September 2026

Role clarity in a growing business means every important outcome has a clear answer to three questions: Who owns the result? What are they allowed to decide? Where does their responsibility stop and somebody else's begin? That sounds simple. Then the company grows. Sales says Operations owns it. Operations says Project Management owns it. Project Management says they were waiting for Finance. Finance says nobody sent the information. Three managers attended the meeting. Six people were copied into the email. The owner eventually sorts it. And somehow the business concludes: "We need better communication." Maybe. But often the real problem is much simpler. Nobody genuinely knew who owned what. Growing businesses do not usually lose role clarity overnight It happens gradually. At the beginning: Owner does almost everything. Then you hire someone. "Can you help with this?" Another person. "They'll take care of that." Then: Supervisor. Administrator. Salesperson. Project Manager. Operations Manager. Finance Manager. Roles accumulate around the work that already exists. Nobody stops to redesign the whole picture. Eventually one person's job overlaps another's. Responsibilities migrate informally. Managers inherit tasks without authority. Employees still ask the founder because they remember when the founder owned everything. And the owner retains a collection of responsibilities they supposedly delegated years ago. That is how a perfectly normal growing SME ends up with: More people. More managers. More meetings. And less certainty about who actually owns the result. Role clarity is not the same as having job descriptions You can have twenty beautifully formatted job descriptions and still have terrible role clarity. Because most job descriptions describe: Activities. Responsibilities. General duties. They often do not explain: Which outcomes the person actually owns. What they can decide. Which numbers they are accountable for. What belongs to somebody else. How two overlapping functions should work together. When something should escalate. Acas's current job-description template guidance includes the role's main duties and who the employee reports to, while current government recruitment guidance recommends defining tasks and responsibilities before recruiting. Useful foundations, certainly. But as a business becomes more complex, management normally needs more than a list of duties. A job description tells me: What you do. Role clarity should also tell me: What happens because you do it. Start with outcomes rather than activities Consider a Sales Manager. Activity-based description: Attend sales meetings. Manage CRM. Support sales team. Review proposals. Meet customers. Fine. Outcome-based version: Own qualified pipeline. Own sales conversion. Own performance of the sales team. Own sales forecasting accuracy. Ensure commercial commitments entering Operations are complete and achievable. Now we understand the job much better. The activities may change. The outcomes remain clearer. Activities are useful. Ownership is more useful. Someone might: Prepare a report. But who owns whether the information is accurate? Someone might: Schedule a job. But who owns whether delivery capacity is sufficient? Someone might: Send the invoice. But who owns ensuring completed work becomes invoiceable promptly? Several people may touch an outcome. One person should usually be clearly identifiable as the person responsible for seeing that outcome through. That distinction removes enormous amounts of ambiguity. "Everyone owns it" is usually dangerous Imagine: "Customer satisfaction is everyone's responsibility." Nice sentiment. Operationally? Who investigates complaints? Who tracks the trend? Who changes the process? Who reports performance? Who makes sure an unresolved complaint does not quietly disappear? Everyone can contribute to customer satisfaction. That does not mean accountability needs to be vague. Shared contribution is normal. Undefined ownership is different. This is where accountability gets muddled Four concepts are often collapsed into one. Responsibility Work you are expected to perform. Accountability The outcome you are expected to answer for. Authority What you are allowed to decide or change. Contribution Work you provide towards an outcome owned elsewhere. You need all four. Responsibility without authority creates frustration "You own customer delivery." Excellent. Can I change the schedule? "No." Approve overtime? "No." Prioritise jobs? "Ask me." Resolve ordinary customer issues? "Check first." Then you do not own customer delivery in any meaningful operational sense. You report on it. The owner still owns it. This is one reason Article #36 connected accountability with authority. Authority without accountability creates different problems Manager can: Spend. Recruit. Change priorities. Agree customer solutions. But nobody reviews the outcomes. Now discretion exists without enough consequence. You want the pair: Appropriate authority. Clear accountability. HSE treats role clarity as a genuine work-design issue The Health and Safety Executive includes Role as one of its six Management Standards for work-related stress. Its standard says employees should understand their role and responsibilities, requirements should be as clear and compatible as possible, and people should have routes for raising concerns about uncertainty or conflicting responsibilities. That is worth paying attention to. Role confusion is not merely annoying administration. Conflicting expectations create actual organisational strain. Imagine reporting to three unofficial bosses Operations Manager says: "Do A first." Sales Director says: "No, customer B is urgent." Owner walks through: "Forget both. Sort C." Employee fails A. Operations Manager asks: "Why didn't you do it?" What exactly was the role expectation? You can call that poor prioritisation from the employee. Or recognise that the organisation issued incompatible instructions. HSE's guidance explicitly says organisations should, as far as possible, ensure requirements placed on employees are compatible. That seems extremely sensible. Owner-managed businesses create this problem particularly easily Because everybody knows: The owner can override anything. Employee has manager. Owner asks employee directly: "Can you quickly do this?" Of course they say yes. Manager's priority gets displaced. Now the organisational chart says one thing. Real authority says another. Do that often enough and the owner becomes everybody's unofficial second manager. Your behaviour teaches people who really owns the decision You can write: "Operations Manager owns scheduling." Then personally change tomorrow's schedule three times. What did everyone learn? Owner owns scheduling. You can write: "Sales Manager owns commercial decisions." Then negotiate every important deal. Everyone learns: Owner owns commercial decisions. Structure is created through behaviour. Not PowerPoint. One of the first tests is simple Ask ten employees: "Who owns this?" Choose something important. Customer complaints. Recruitment. Pricing. Capacity. Quality. Debtors. Scheduling. Marketing. If you get six different answers? Useful finding. Then ask the supposed owner "What decisions can you make without Adam?" This is often even more revealing. Answer: "Not totally sure." There is your role-clarity problem. Role clarity becomes more important as the business grows ONS's latest published Management and Expectations Survey found that larger UK businesses reported more structured management practices on average. Firms with 10 to 19 employees scored 0.51 on its structured-management scale in 2023, rising to 0.58 among firms with 20 to 49 employees, 0.63 among firms with 50 to 99 employees and higher again among larger firms. The measure covers continuous improvement, KPIs, targets and employment practices rather than role clarity specifically, so it should not be interpreted as proof that organisational charts create productivity. But it does illustrate the wider shift towards more deliberate management as organisational scale increases. Informal coordination has limits. Eventually: "Everyone sort of knows what they do." stops being enough. The first growth stage: everybody does everything Often perfectly reasonable. Five-person business. Customer calls. Whoever is free answers. Problem arrives. Someone sorts it. Founder involved everywhere. Flexibility matters more than beautifully defined roles. Do not bureaucratise a tiny company unnecessarily. The second stage: specialists appear Someone mainly sells. Someone manages administration. Someone delivers. Someone handles finance. Still plenty of overlap. Usually manageable. But responsibilities begin becoming repeatable enough to name. The third stage: managers appear This is where clarity becomes far more important. Because now the company has: People. And people responsible for other people. Who handles performance? Who approves holiday? Who sets priorities? Who recruits? Who manages capacity? Who deals with customer escalation? If the answer remains: "Usually the owner." then the management layer exists mostly in title. The fourth stage: functions become interdependent Sales. Operations. Finance. Marketing. Customer Service. Projects. Now the biggest problems often exist between roles rather than inside them. Sales owns winning customer. Operations owns delivering. Who owns the handover? Finance owns invoicing. Project Manager owns completion. Who ensures completion information reaches Finance? The interfaces matter. Most role problems live in the gaps This is important. Often everybody performs their individual job reasonably well. The failure occurs here: Sales → Operations. Operations → Finance. Finance → Customer. Marketing → Sales. Manager → Manager. The handover has no clear owner. Then information drops. Map outcomes first Take the business's important recurring outcomes. For example: Qualified enquiries generated. Sales converted. Customer scope agreed. Work scheduled. Work delivered. Quality confirmed. Customer issue resolved. Invoice raised. Payment collected. Employee recruited. Employee performance managed. Capacity planned. Now ask: Who owns each outcome? Not who touches it. Who answers for it? You should be able to complete this sentence "If this outcome repeatedly fails, the first person accountable for understanding why is ______." That is extremely useful. It does not mean every failure is automatically their fault. It means: They own visibility. Diagnosis. Response. Escalation where required. Avoid building a blame map This exercise is not: Who gets bollocked? Ownership should answer: Who makes sure this works? Not: Who receives punishment when anything goes wrong? If role mapping becomes a blame exercise, managers will resist ownership. Understandably. Create an Ownership Map I prefer something simple. Columns: Outcome Primary owner Key contributors Decisions they can make When it escalates Measure For example: Customer onboarding. Owner: Customer Success Manager. Contributors: Sales, Finance, Operations. Authority: can set onboarding schedule and chase missing information. Escalation: contractual discrepancy or strategic account issue. Measure: onboarding completed by agreed date. That is vastly more useful than three pages of generic duties. Do not create a spreadsheet containing 400 activities You can. Please don't. You will spend three weeks deciding who owns: "Ordering printer toner." Then nobody will update it. Focus on meaningful outcomes and recurring decisions. The detail beneath them can sit in processes. Roles and processes are different Role answers: Who owns the outcome? Process answers: How does the work happen? Do not confuse them. You might completely redesign the invoicing process. Finance Manager still owns cash collection. Process evolves. Ownership remains. Define role purpose in one sentence For every significant role: Why does this job exist? Example: Operations Manager: "Ensure customer commitments are delivered safely, profitably and reliably through effective management of people, capacity and operational resources." That helps filter everything below it. Then define five to seven primary outcomes Not forty-seven tasks. For an Operations Manager: On-time delivery. Operational capacity. Team performance. Quality. Operational cost. Continuous improvement. Cross-functional coordination. Now we have a role. Skills England's current standards take exactly this kind of outcome-and-accountability view Its Operations Manager standard describes the role as accountable for developing team members, managing projects, planning and reviewing workloads and resources, delivering operational plans and resolving problems. It explicitly expects Operations Managers to take ownership of their own and their team's tasks and workload. The current Team Leader standard similarly expects first-line leaders to set and manage objectives, manage resources, interpret performance data and take accountability for their own workload. Those are clearer expectations than: "Help run the team." Define what the role does not own This can be equally powerful. Sales Manager does not own: Final operational scheduling. Finance approval. Technical quality. They may influence them. But no. Operations Manager does not own: Sales commission structure. Company strategy. Tax advice. Marketing campaigns. Again: Contribution is different from ownership. Boundaries reduce conflict Without boundaries: Sales says: "Operations is blocking growth." Operations says: "Sales keeps overpromising." Both might be right. Clarify: Sales owns commercial opportunity. Operations owns delivery capacity. Neither unilaterally commits something requiring the other's capacity beyond agreed parameters. Then define the decision process when they conflict. Now disagreement has architecture. Decision rights deserve their own conversation For every manager, list recurring decisions. Who decides: Price? Discount? Hiring? Overtime? Supplier? Customer remedy? Schedule? Purchasing? Capital expenditure? Priority? Marketing spend? Then assign levels. For example: Manager decides independently. Manager decides and informs. Manager recommends, owner approves. Owner decides. Do not leave this to habit. A lot of "poor communication" is actually decision ambiguity People keep discussing the same issue. Meeting after meeting. Why? Nobody knows who can decide. Once authority is clear: Discussion ends. Decision happens. This can remove enormous amounts of management noise. Do not require consensus for everything Collaborative management does not mean every decision needs six people to agree. Consult widely where useful. Then somebody decides. Otherwise: Meeting. Follow-up meeting. Email chain. Owner intervention. Consensus can become responsibility avoidance. RACI can be useful, but do not turn your entire company into one RACI typically distinguishes: Responsible. Accountable. Consulted. Informed. Useful for: Projects. Complex processes. Cross-functional implementation. But if every recurring business activity requires a forty-column RACI matrix, you may be designing complexity rather than solving it. Use the simplest tool that creates clarity. For everyday operations, named ownership is often enough Outcome: Monthly management accounts issued by working day ten. Owner: Finance Manager. Contributors: Bookkeeper, department managers. Done. You do not necessarily need a methodology acronym around everything. Clarify handovers explicitly A role can be crystal clear. Handover still broken. Sales hands work to Operations. What must exist before Operations accepts it? Signed scope? Customer contact? Programme? Margin? Special requirements? Purchase order? Deposit? Define the handover. Now: "I thought they knew." reduces. The receiving function should define what good handover looks like This is an excellent approach. Ask Operations: "What do you need from Sales before you can deliver this properly?" Ask Finance: "What do you need before you can invoice?" Ask Sales: "What information do you need back from Operations?" Interfaces become agreements between functions. Not assumptions. Ownership should follow the work through Project Manager says: "I sent Finance the information." Invoice still not raised. Do they own invoicing? Perhaps not. But if their outcome is: Project commercially closed, they may need to ensure the handover completed successfully. Passing an email is not necessarily completion. This is why outcome definitions matter. Avoid the phrase "I did my bit" That is task thinking. The customer does not care that: Sales did their bit. Operations did their bit. Finance did their bit. They care whether the overall result happened. Strong organisations preserve functional ownership while designing clean connections between functions. Meetings can expose role ambiguity Listen. Who continually says: "Who is doing that?" Useful. Who leaves meetings with: "I thought you were doing it." Useful. Who owns every action? Owner? Very useful. Your meetings are showing where the structure is unclear. End decisions with owner and date Decision: Change supplier. Owner: Sarah. Date: Friday. Not: "We should probably look at suppliers." That sentence owns nothing. Scorecards should map to ownership too Article #54 matters here. KPI: On-time delivery. Who owns it? Operations Manager. Pipeline. Sales Manager. Overdue debt. Finance Manager. If a number has no clear owner, ask why it exists on the scorecard. Performance visibility without accountability creates interesting meetings. Not necessarily better management. Give managers outcomes they can influence Do not tell Operations Manager: "You own company profit." They influence it. But maybe they directly own: Labour utilisation. Operational gross-margin drivers. Overtime. Rework. Delivery. Those connect to profit. Make ownership specific enough to be fair. Acas recommends the same basic connection between objectives and role Current Acas performance-management guidance says objectives should be specific, measurable, achievable and relevant to the employee's job and responsibilities, and regular reviews should allow performance and support needs to be discussed. Again: Clarity before accountability. If the objective has little relationship to what somebody can actually control, the management system is weak. Do not make two people equally accountable for the same result without good reason "James and Sarah both own it." Who has final say? Who notices if it fails? Who reports? Sometimes joint accountability is genuinely appropriate. Often it simply avoids choosing. Better: Sarah owns outcome. James owns a clearly defined contribution. Now both know. Be particularly careful with co-founders Two directors. Both involved everywhere. Employees shop for answers. Ask Director A. Don't like answer. Ask Director B. Different answer. Chaos. Co-founders need clear domains too. One company. Shared ownership of the business. Distinct operational authority. Founder relationships do not magically remove the need for governance Who owns: Commercial? Operations? Finance? People? Brand? Strategic decisions? Major disagreements? Define it. Particularly when the company becomes larger than the founders' ability to coordinate informally all day. Role clarity should include escalation Manager owns customer issues. Until what? Potential legal exposure? Safety issue? Compensation above £5,000? Strategic customer threat? Good. Write it. Ownership should not mean: "Never ask." It means: Know when the issue remains yours and when senior judgement is appropriate. Escalation should not automatically transfer the whole problem Manager escalates: "This requires your approval because it exceeds my £5,000 limit. I recommend option B and will implement it once approved." Good. Different from: "Customer's angry. Can you deal with it?" The manager still owns the process. Clarify priorities when two outcomes conflict Sales wants: Fast delivery. Operations wants: Stable schedule. Finance wants: Margin. Customer wants: Everything immediately. Someone needs rules for trade-offs. Otherwise role clarity fails the moment priorities collide. For example: Safety cannot be traded. Contractual commitments take precedence over speculative work. Strategic-customer exceptions require specific approval. Your rules will differ. But define enough to prevent constant owner refereeing. The owner should not be the default arbitration mechanism forever Early on? Probably unavoidable. Later? Managers should resolve many conflicts directly. Sales Manager and Operations Manager sit together. Understand issue. Make decision inside agreed authority. Owner does not need to mediate every disagreement between competent adults. Managers should manage across functions, not only downward The current Skills England Operations Manager standard explicitly describes working across functions such as finance, HR, IT, sales and marketing, as well as managing relationships with external stakeholders. That is important. Management is not only: Tell team what to do. It is also: Coordinate horizontally. Beware the heroic employee Every company has one. "Ask Emma." What does Emma own? "Everything really." Danger. Emma knows every process. Fixes every mistake. Helps every department. Nobody knows where role starts and stops. Emma is invaluable. And possibly becoming another bottleneck. Capability should not require unlimited role ambiguity. The same applies to the owner Founder: Floats everywhere. Fixes everything. Because: "I just fill the gaps." Exactly. Which gaps? Why do they still exist? Every recurring owner gap-fill is potential evidence of unclear organisational ownership. Map the owner's role too Do not only clarify employees. What does ownership retain? Perhaps: Strategy. Capital allocation. Management-team performance. Major commercial relationships. Significant risk. Senior recruitment. Culture. Then list what the owner no longer owns . Daily scheduling. Routine customer issues. Normal purchasing. First-line employee performance. Whatever applies. This is critical. You cannot create clarity below while remaining deliberately vague at the top If the owner reserves the right to enter every role whenever they fancy, all lower-level ownership remains conditional. Managers notice. Employees notice. Eventually everyone waits. An owner can still intervene Of course. Emergency. Major risk. Something genuinely failing. Ownership rights do not mean: Founder banned. But intervention should be exceptional enough that the normal structure remains credible. Temporary involvement should have an exit Owner steps into Operations because manager left. Fine. Temporary. Write: What am I covering? Until when? Who eventually receives it? Otherwise temporary responsibility quietly becomes permanent. Five years later: "Why am I still doing this?" Because nobody deliberately moved it back out. Role creep happens constantly Good employee. "Can you also handle this?" They do. Then: Another thing. Two years later their actual job bears almost no resemblance to the title. Review significant roles periodically. What are they really doing? Should they? Does title still fit? Does salary? Does authority? Does workload? Role clarity does not mean rigidity People worry: "We're small. Everyone needs to muck in." Agreed. You can have: Flexible execution. Clear ownership. Those are completely compatible. Sarah can help Operations during a crisis. That does not mean nobody knows who owns Operations. "That's not my job" culture is not the objective The goal is not employees refusing to help across imaginary departmental borders. It is: I know what I own. I know where I contribute. I know when another person owns the outcome. And I will collaborate without losing accountability. That is different. A mature business needs both flexibility and clarity Too little clarity: Chaos. Too much rigid bureaucracy: Slow. The target sits between them. Clear enough that outcomes have owners. Flexible enough that humans still help each other. The HSE language is useful here Its Role standard does not demand inflexible jobs. It asks organisations to provide enough information for employees to understand their role and responsibilities, keep requirements reasonably clear and compatible, and provide ways for people to raise concerns where responsibilities conflict. That is a sensible standard for almost any growing business. Role clarity is particularly important during change New manager. Acquisition. Restructure. Promotion. New department. System implementation. Someone leaves. These are moments when responsibility moves. Do not assume everyone sees the new map automatically. Say it. When you promote someone, explicitly transfer authority "You're now Operations Manager." Great. Which decisions changed? Who reports to them? What previously came to owner that now goes to them? Which meetings do they lead? Which KPIs? Without that transfer, promotion can be mostly salary and title. Communicate the change to everybody affected Do not tell Sarah privately: "You own this now." Then leave employees asking you. Explain: "From Monday, scheduling and resource allocation sit with Sarah. If you have a scheduling issue, take it to Sarah. These are the situations that still come to me." Now structure becomes real. Support the new owner publicly Employee bypasses Sarah and asks you. Do not answer reflexively. "This sits with Sarah." Redirect. Otherwise you undermine the transfer in thirty seconds. Do not allow managers to redirect everything back upwards either Manager says: "I wasn't sure, so I asked Adam." Question: Was it inside your authority? If yes: Make the decision. Role clarity is partly about knowing where responsibility ends. Then having the courage to operate inside it. What if people disagree about who should own something? Good. Discuss it. Ask: Who has the information? Who controls the resources? Who is closest to the outcome? Who can reasonably be accountable? Which role has the appropriate authority? Design it. Do not let responsibilities simply fall to the most conscientious person because: "They'll make sure it gets done." That is how great employees become overloaded. Ownership should follow capability and position, not personality The loudest person should not automatically own. The founder's favourite should not automatically own. Person who always volunteers should not own everything. Put responsibility where the organisational logic says it belongs. Make workload visible during role design You map Sarah's outcomes. Seven major areas. Then discover each one is a full-time job. Role clarity exposed a capacity problem. Excellent. Better than pretending Sarah owns all seven and blaming her when four fail. Clarity can reveal organisational gaps You map everything. One major outcome remains: Nobody sensible can own it. Perhaps you discovered a missing role. That can support: Recruitment. Restructure. Promotion. Process redesign. This is why role mapping is commercially useful. It can also reveal duplicated management Outcome: Supplier performance. Owned by: Operations Manager. Procurement Manager. Commercial Director. Owner. Four owners. Perhaps one is enough. Role clarity can remove work as well as allocate it. The best ownership map usually makes the organisation simpler Fewer: Approvals. Duplicates. Meetings. Escalations. Questions. Not more. If role clarification creates additional bureaucracy everywhere, redesign it. A simple role charter For each important role, one page. Purpose Why does this role exist? Primary outcomes Five to seven things it must make happen. Measures How do we know? Decision authority What can the person decide? Key interfaces Who do they depend on? Who depends on them? Escalation What should move upwards? Does not own Useful boundary. That is enough for many SMEs. Review role charters in one-to-ones Ask: Is this still accurate? What are you doing that is not here? What do you think you own that I think someone else owns? Where are decisions unclear? What continually gets bounced between departments? Those conversations reveal reality. Ask managers to write their own first This is useful. Without showing them your answer: "What do you believe you own?" Then compare. Manager says: "I own sales." Owner's expectation: "You own sales, marketing, forecasting and key accounts." Interesting. Or opposite. You thought they owned pricing. They thought you did. Better to discover in a conversation than through a lost customer. Run the same exercise between functions Sales writes: What we own. What we need from Operations. Operations writes: What we own. What we need from Sales. Compare. The mismatches become your improvement list. Watch for three classic gaps The invisible gap Nobody thinks they own it. The overlap Several people think they own it. The shadow owner Job officially belongs elsewhere but owner still controls it. Those three patterns explain enormous amounts of SME friction. Another classic: responsibility without final decision Project Manager owns project. But customer variations require owner approval. Purchasing requires owner. Resource changes require owner. Price requires owner. Fine if risk requires those controls. But if most normal project decisions travel upwards, Project Manager's role is narrower than you think. Be accurate about it. Authority should increase with competence New manager: More review. Experienced manager: Greater discretion. That is normal. Role clarity does not require identical authority forever. Document current boundaries and deliberately expand them. The role can evolve as the person develops This is much better than vague encouragement to: "Step up." Perhaps today: Manager can approve £1,000. Six months of strong judgement: £5,000. Now development has an observable form. Performance management becomes easier when ownership is clear Employee misses outcome. You can ask: Did they know it was theirs? Did they have authority? Resources? Capability? Acas recommends objectives that are clearly connected to a person's role and responsibilities and reviewed through regular performance conversations. That makes accountability considerably fairer. Without role clarity, poor performance conversations become arguments Manager: "You didn't do this." Employee: "I thought James was doing it." Manager: "Well, you should have known." Weak. Clear ownership removes some of that ambiguity. Not every performance issue. But a lot. Recruitment improves too Government guidance for employers says defining the role and what good looks like should happen before writing a job advert, including responsibilities, hours and required skills or experience. Exactly. Do not recruit: "General Manager to take stuff off me." Define: Which stuff. Which outcomes. Which authority. Then find the person. Organisational risk needs clear ownership as well Although written for public-sector organisations, the UK government's Orange Book states a broadly useful governance principle: roles and accountabilities for managing risks and controls should be clearly defined and assigned to people with appropriate seniority, skills and experience. The context is different from a typical owner-managed SME. The principle still travels well. Important risks should have owners. Think particularly carefully about: Health and safety. Cybersecurity. Data protection. Cash. Regulatory compliance. Key customer concentration. Quality. Business continuity. Someone should know: "I own making sure this risk is managed." Not: "I assumed IT dealt with it." Do not confuse ownership with technical expertise Finance Director may own ensuring tax obligations are properly managed. They may still use: Accountant. Tax specialist. Payroll. Ownership means ensuring the outcome is handled. Not personally possessing every specialist skill. This allows organisations to remain clear without expecting impossible breadth. The same applies to the owner You remain ultimately responsible for the company. That does not mean you personally perform every responsibility inside it. Ownership of the company is not the same as operational ownership of every task. That distinction is the whole game. A 30-day role-clarity reset Week 1: Find ambiguity For one week, record moments involving: "Who owns this?" "I thought they were doing it." "Can you decide?" "Adam needs to approve." "That's not my department." Those are your clues. Week 2: Map important outcomes List the twenty or thirty recurring outcomes that matter most. Assign: Primary owner. Contributors. Decision authority. Escalation. Week 3: Map management roles For every manager: Purpose. Primary outcomes. KPIs. Authority. Interfaces. What they do not own. Week 4: Communicate and test Tell the organisation. Redirect questions. Run meetings using the new ownership. Notice where reality does not fit the map. Adjust. Then test the structure through absence Owner unavailable for a day. Do people know who decides? Sales Manager unavailable. Who covers? Operations Manager on holiday. Which decisions have delegation? Role clarity includes resilience. One named owner with no backup creates key-person dependency. Primary owner does not mean only capable person You still need: Deputies. Cross-training. Succession. The distinction is: One person is clearly accountable today. Others can step in when required. Article #46's knowledge-transfer principles matter here. Build deputies deliberately For each critical role: Who acts when they are unavailable? Which decisions can deputy make? What information do they need? Now ownership does not disappear when someone goes to Tenerife. Role clarity should eventually reduce meetings Fewer meetings required to decide who decides. Fewer people invited "just in case." Fewer update meetings because ownership and KPIs already create visibility. That is a useful success measure. If role clarification leads to twelve new recurring meetings, something may have gone wrong. It should also reduce owner interruptions Employee knows: Who to ask. Manager knows: What they can decide. Functions know: How handovers work. Owner becomes less necessary as human routing software. That is Dependency Removal. It should improve speed Clear authority: Decision. Unclear authority: Discussion. Email. Manager. Owner. Back to manager. Clarification. Decision. Days disappear inside ambiguity. Role clarity can improve speed without asking anybody to work faster. It should improve accountability without creating micromanagement Because the owner no longer needs to watch: How everything happens. They can review: Outcome. Measure. Exceptions. That is the connection between role clarity and good delegation. It should make growth easier New employee arrives. Where do they sit? Who manages them? What outcome do they contribute to? Who decides? The organisational architecture becomes teachable. That matters as headcount rises. How Evolve approaches role clarity If an owner tells me: "My team needs to communicate better." I want examples. Because communication may not be the problem. Maybe: Nobody owns the outcome. Two people own the same decision. Manager has responsibility but no authority. Functions have no defined handover. Employees can bypass managers. Owner keeps changing priorities. Everything eventually escalates upwards. Then another communication workshop is unlikely to solve much. We need to redesign who owns what. I normally want to see where the work actually goes Not just the organisational chart. Customer enquiry enters. Where? Then what? Who decides? Who receives it? Who knows whether it happened? Where does the owner reappear? Trace reality. That tells us far more than job titles. The objective is not creating an organisation where nobody helps anybody Quite the opposite. Good role clarity makes collaboration easier. Because I can help you without worrying that: Nobody owns my work. I accidentally took responsibility permanently. Two managers will give contradictory instructions. The owner will reverse the decision tomorrow. Clarity gives collaboration structure. Nor is the objective making managers territorial "This is mine." "This is yours." Wrong interpretation. Functional boundaries exist to improve outcomes. Not build kingdoms. A strong management team cares about company performance while retaining clear individual accountability. Owners need to tolerate the loss of operational ownership This is the uncomfortable bit. Once Sarah genuinely owns Operations, you are no longer the person who automatically decides every operational question. You still own the company. But you transferred part of the operating responsibility. If you cannot tolerate that transfer, role clarity will remain theoretical. The test is not what the chart says The test is: When something happens on Thursday afternoon, who does everybody instinctively look at? If the answer is still: Owner. Then the real role map has not changed. So, who should actually own what in a growing small business? Start with outcomes. Not job titles. Not historic habits. Not whoever happens to be most reliable. Identify what the business needs to happen repeatedly. Assign one clear primary owner where practical. Define the contribution required from others. Give the owner enough authority to influence the result. Clarify the decisions they can make. Define where escalation begins. Build clean handovers between functions. Attach meaningful measures. Communicate changes. Then make your behaviour match the structure. And include yourself. Because a growing company does not need the owner involved everywhere. It needs the owner to make sure everything important has somewhere sensible to live . That is role clarity. Not bureaucracy. Not endless documentation. Just a company where, when something matters, people no longer need to ask: "Whose job is this?" They already know.

Two very different handmade ceramic pieces displayed with the same price.