How Do I Build a Management Team That Doesn't Depend on Me?

Adam Fox • 29 September 2026

You build a management team that does not depend on you by giving managers real ownership of different parts of the business and making them responsible for running the company together, not merely reporting their individual problems back to you.

That requires more than job titles.

Your managers need:

Clear outcomes.

Real decision authority.

Useful management information.

Responsibility for solving problems.

Responsibility for managing people.

A regular operating rhythm.

The ability to challenge one another.

And an expectation that cross-functional issues get resolved between them wherever possible.

The owner still sets direction, makes genuinely owner-level decisions and holds the management team accountable.

But the owner stops being the person who connects everything.

Because if you employ:

An Operations Manager.

Sales Manager.

Finance Manager.

Office Manager.

Project Managers.

Team Leaders.

And every important disagreement, decision and problem still comes back to you?

You have managers.

You do not yet have much of a management team.

A management team should reduce the number of things the owner has to manage personally

This is the simplest test.

As management capability increases, do fewer operational decisions reach you?

Do employees increasingly use their managers rather than bypassing them?

Can departments resolve problems with one another?

Can somebody other than you chair a management meeting?

Can managers see when performance is off track and act before you point it out?

Can the company operate for several days without needing your judgement on ordinary business?

If not, investigate.

Because the entire purpose of building management capability is organisational leverage.

Skills England's current Operations Manager standard describes managers as responsible for leading their function, developing people, planning workloads and resources, solving problems, interpreting data, making decisions and working collaboratively across departments and stakeholders.

That is considerably more than supervising activity and keeping the owner informed.

The first mistake is building a collection of managers rather than a management team

This distinction matters.

A collection of managers looks like this.

Sales Manager runs Sales.

Operations Manager runs Operations.

Finance Manager runs Finance.

Each one speaks to the owner.

Then when Sales and Operations disagree:

Owner decides.

When Operations needs something from Finance:

Owner gets involved.

When Finance challenges Sales:

Owner referees.

The owner becomes the common point connecting all of them.

You created vertical management.

But not much horizontal management.

A genuine management team should gradually become capable of coordinating across functions.

The Sales Manager speaks to Operations.

Operations speaks to Finance.

Managers make trade-offs.

They surface decisions genuinely requiring ownership.

They do not use the owner as an internal postal service.

Your organisational chart can look grown-up while the operating model remains completely founder-led

This happens all the time.

The chart says:

Managing Director.

Operations Manager.

Sales Manager.

Finance Manager.

Project Managers.

Looks excellent.

But behaviour says:

Everybody waits for Adam.

That behaviour is the real organisation.

Ask:

Who settles priority disputes?

Who approves exceptions?

Who decides when departments disagree?

Who catches missed actions?

Who decides which customer matters most?

Who understands the whole company?

If nearly every answer is:

The owner.

then titles changed faster than authority.

Management teams are particularly important as complexity grows

Current ONS data shows larger UK firms report more structured management practices on average than smaller firms. In its 2023 Management and Expectations Survey, firms with 10 to 19 employees averaged 0.51 on the management-practice scale, compared with 0.58 among firms with 20 to 49 employees and 0.63 among firms with 50 to 99 employees. ONS also reports a significant association between stronger management practices and productivity.

That does not mean adding managers automatically makes companies more productive.

It does highlight something useful.

More organisational complexity usually creates greater need for deliberate management.

You cannot keep coordinating a fifty-person business in the same informal way you coordinated ten people.

Stage one: managers are really senior employees

Most management structures start here.

You promote your best people.

The strongest salesperson becomes Sales Manager.

Best supervisor becomes Operations Manager.

Experienced administrator becomes Office Manager.

They now have management titles.

But much of their week is still the work they previously did.

They continue:

Selling.

Producing.

Quoting.

Scheduling.

Fixing.

Serving customers.

They occasionally manage people around the edges.

This is normal.

It can be a useful first step.

It is not the finished management structure.

Stage two: managers genuinely own their functions

Now something changes.

Operations Manager owns operational performance.

Not merely the schedule.

Sales Manager owns sales performance.

Not merely personal sales.

Finance Manager owns financial control.

Not merely producing reports.

They have outcomes.

Measures.

People responsibility.

Decision authority.

The owner can ask:

"How is Operations performing?"

and speak to one accountable person.

That creates meaningful leverage.

Stage three: the managers begin operating as a team

This is the transition many SMEs never properly make.

The managers stop thinking only:

"My department."

They begin thinking:

"Our company."

Sales understands that winning poor-margin work with impossible lead times creates an Operations problem and eventually a company problem.

Operations understands that protecting every internal preference can destroy Sales.

Finance understands that refusing every investment protects cash today but may prevent capacity tomorrow.

Managers start considering trade-offs across the whole company.

That is when you begin to have a management team.

Stage four: the team can run the operating business without the owner coordinating it

Now the owner sets:

Direction.

Major priorities.

Strategic parameters.

Capital decisions.

Key leadership expectations.

Then the management team translates those into execution.

They run the weekly operation.

Resolve normal conflicts.

Monitor performance.

Allocate resources within agreed boundaries.

Develop people.

Escalate the genuinely important issues.

The owner remains accountable for the company.

They simply stop being responsible for personally operating every part of it.

That is the goal.

Start by deciding which management seats the business actually needs

Do not copy a corporate organisational chart.

You probably do not need twelve directors.

Ask:

What major outcomes in this business require ongoing management?

Perhaps:

Sales.

Operations.

Finance.

People.

Customer delivery.

Projects.

Different company.

Different answer.

A twenty-person engineering company may need three strong management seats.

A sixty-person service business might need seven.

Build around the work.

Not prestige.

Every management seat needs a reason to exist

If somebody is called a manager, what do they manage?

People?

Performance?

Budget?

Capacity?

Customers?

Projects?

Process?

Decisions?

If the answer is mostly:

"They help me with stuff."

you have not designed the role.

A manager should own something significant enough that the owner's responsibility materially reduces when the role works.

Define outcomes before responsibilities

Job descriptions often contain endless activities.

Attend meetings.

Support the team.

Help customers.

Assist with planning.

Liaise with departments.

Fine.

What result do they own?

For an Operations Manager perhaps:

On-time delivery.

Quality.

Labour performance.

Capacity.

Customer delivery issues.

Operational margin.

Team capability.

A Sales Manager might own:

Revenue.

Gross profit.

Pipeline.

Conversion.

Forecast accuracy.

Sales-team performance.

The exact measures will differ.

But management becomes substantially clearer when roles are connected to outcomes rather than vague activity.

Give every manager a small number of meaningful measures

Do not create a dashboard because dashboards look professional.

Create visibility.

A manager should know:

Are we on track?

If not, why?

Is it getting better or worse?

What needs action?

The ONS management framework specifically assesses how firms use KPIs, targets, continuous improvement and employment-management practices, and finds firms with stronger structured management scores are more likely to use analysis in decision-making.

This is not about drowning your business in KPIs.

It is about managers managing with evidence rather than instinct alone.

Build one company scorecard as well as departmental measures

This is where the team part becomes important.

If Sales only sees sales numbers, Finance only sees cash and Operations only sees delivery, each manager optimises their own world.

Give the management team a shared view.

Perhaps:

Revenue.

Gross margin.

Cash.

Pipeline.

On-time delivery.

Quality.

Capacity.

Overdue debt.

Customer issues.

Again, choose what matters.

Now everybody sees the same company.

That creates better conversations.

Managers should not be able to say "that's not my problem" about everything outside their function

Of course responsibilities have boundaries.

But a management team shares responsibility for business performance.

Imagine sales commitments are creating operational chaos.

The Sales Manager cannot say:

"I hit my target."

and walk away.

If Operations repeatedly damages strategic customers, Sales cannot treat it purely as an Operations issue.

If Finance is not producing information managers need, everybody suffers.

Management requires functional ownership and collective responsibility.

CIPD's evidence review on high-performing teams highlights shared thinking, information sharing, team reflection, cohesion and psychological safety among the factors leaders should pay attention to when building effective teams.

Your management team is a team too.

Treat it like one.

Make cross-functional problem solving the default

Imagine Sales promises something Operations cannot deliver.

Old model:

Sales complains to owner.

Operations complains to owner.

Owner mediates.

New model:

Sales Manager and Operations Manager meet.

They establish:

What was promised?

What capacity exists?

What matters commercially?

What are the options?

They either decide or bring one clearly framed exception upwards.

The owner should increasingly receive:

"We recommend this."

rather than:

"Tell us what to do."

That is management maturity.

The owner must stop being the referee

This is uncomfortable because refereeing feels important.

Two managers disagree.

You know the answer.

You decide.

Fast.

But what did they learn?

That disagreement travels upwards.

Next disagreement?

Owner.

Instead ask:

"What do you both recommend?"

If they disagree:

"What trade-off are we making?"

"What evidence supports each position?"

"Which company priority matters most here?"

Force the management team to do management work.

You can still decide where ownership genuinely requires it.

But make them exhaust their responsibility first.

Managers need actual decision rights

Article #36 covered this at employee level.

It matters even more with managers.

A manager without authority becomes an expensive coordinator.

Define:

What can they decide?

What can they spend?

What can they change?

Which people decisions can they make?

Which customer issues can they resolve?

Which commitments can they give?

Which situations must reach the owner?

Skills England's current Operations Manager standard specifically says operations managers operate within agreed budgets and resources, are responsible for decision-making and guide or influence the decisions of others.

Responsibility and authority have to meet.

Write an authority map

You do not need a massive governance manual.

Take recurring decisions.

Hiring.

Pay changes.

Overtime.

Customer refunds.

Discounting.

Purchasing.

Supplier changes.

Scheduling.

Capital expenditure.

Contract exceptions.

List who can decide at each level.

Then identify the decisions still unnecessarily sitting with you.

This often exposes why managers remain dependent.

Define escalation clearly

A mature manager should know both:

What I can decide.

And:

What must reach the owner.

Perhaps escalation includes:

Major safety or regulatory exposure.

Material legal risk.

Strategic customer loss.

Senior leadership issues.

Spend above agreed authority.

Large commercial commitments.

Decisions changing company direction.

Good.

Everything else should not automatically reach you.

Improve the quality of escalation

There is an enormous difference between:

"We've got a problem."

and:

"We have a problem. Here are the three options. We recommend option B because it protects margin and customer delivery. It needs your approval because the spend exceeds our authority by £25,000."

The second deserves owner time.

The management team already did the work.

That is exactly what you are building.

Give managers information before asking them to decide

Owners sometimes say:

"I want them to make decisions."

But the owner still holds:

Financial information.

Customer context.

Margin data.

Strategy.

Staff information.

How can they make good decisions?

Better information supports better delegation.

In Bloom and colleagues' management experiment, better information flow helped owners delegate more decisions to middle managers while productivity also improved in the treatment firms.

The setting was Indian textile plants, not UK SMEs.

The mechanism is still useful.

Visibility reduces the need for the owner to personally hold every decision.

Do not create information monopolies

Finance numbers only understood by Finance.

Sales pipeline only understood by Sales.

Operations plan only understood by Operations.

That weakens the team.

Managers should understand enough of each other's world to make sensible business decisions together.

Not become accountants, salespeople and production experts simultaneously.

Enough to understand consequences.

Create a weekly management meeting that actually manages

A useful management meeting should not be five managers presenting information to the owner.

That recreates owner dependency in meeting form.

Manager one reports.

Owner comments.

Manager two reports.

Owner decides.

Manager three reports.

Owner fixes.

You just ran five separate one-to-ones in front of an audience.

The team barely interacted.

The management meeting belongs to the management team

I would want it covering something like:

Where are we off track?

What changed?

What needs a decision?

What cross-functional issue needs resolving?

Which commitment from last week remains open?

What risk is emerging?

Who owns the next action?

The conversation should happen between managers.

Not only between each manager and you.

Consider rotating or eventually transferring the chair

Early on, you may chair.

Fine.

But can the meeting eventually run without you?

That is a useful test.

Perhaps the Operations Manager or General Manager chairs.

You attend parts.

Perhaps later you receive the outputs.

The right answer depends on your structure.

But if the weekly management meeting collapses whenever the owner is absent, the management system still depends on the owner.

Meetings should produce decisions and ownership, not merely shared awareness

"Good discussion."

Lovely.

What changed?

Who owns what?

What decision was made?

What date?

A management team should convert information into action.

Otherwise the meeting becomes organisational theatre.

Use a visible action log

Not the owner remembering everything.

Action.

Owner.

Deadline.

Next meeting:

Done?

Not done?

Blocked?

Changed?

This creates accountability between managers rather than owner-powered chasing.

Acas recommends clear objectives, regular check-ins and ongoing feedback as part of effective performance management.

The same principle belongs at management-team level.

Commitments need visibility.

Managers should hold each other accountable too

This is a sign the team is maturing.

Operations says:

"We still haven't received that forecast from Sales."

Sales Manager responds.

Not everything requires the owner saying:

"Come on, get this done."

Managers can challenge peers.

Respectfully.

Directly.

That creates a stronger organisation.

Psychological safety does not mean avoiding disagreement

A functioning management team will disagree.

That is useful.

Different roles see different risks.

Sales may want speed.

Operations wants deliverability.

Finance wants cash.

Good.

You want those tensions visible.

CIPD's review of high-performing teams highlights psychological safety as important partly because team members need to be able to speak up and take interpersonal risks.

The goal is not harmony at any cost.

It is productive disagreement without personal warfare.

Teach managers to disagree around evidence and priorities

Instead of:

"Operations always blocks everything."

Try:

"We currently have nine weeks of capacity committed. This opportunity requires delivery in six. Here are the available options."

Instead of:

"Finance never lets us spend anything."

Try:

"This investment costs £70,000. Here is the expected return and cash requirement."

Better management conversations.

Less personality.

More decision quality.

The owner must allow managers to challenge them too

This is difficult.

You want a management team.

But whenever a manager disagrees with you:

You shut it down.

Fine.

Soon you will have a group of people waiting to hear what you think.

That is not a management team.

It is an audience.

If you hired capable people, let them use their capability.

They will sometimes be wrong.

So will you.

A useful management team should improve the owner's decisions as well as reduce the owner's workload.

CMI explicitly includes collaborative leadership as a management capability

Its current professional standard describes stronger managers as working across departmental boundaries, building collaborative relationships and creating environments where teams have autonomy, clear accountabilities and shared responsibility for outcomes.

That is exactly the behaviour you need.

Managers cannot only be competent inside their departments.

They need to work across them.

Stop having separate secret conversations with every manager

This can accidentally destroy the team.

Sales Manager tells you Operations is the problem.

You agree sympathetically.

Operations Manager later tells you Sales is the problem.

You agree sympathetically again.

Now each manager believes the owner privately supports their position.

Bring appropriate conflicts into the management conversation.

Not every sensitive issue, obviously.

But cross-functional disagreements should usually involve the people involved.

No triangulation.

Do not become the information broker

Same problem.

Finance tells you something Sales needs.

You tell Sales.

Sales responds.

You tell Finance.

Stop.

Put the appropriate people together.

Every time you act as broker, you reinforce your centrality.

Managers need direct working relationships.

Build relationships between managers outside the formal meeting

The management team cannot only exist Tuesday from 9 until 10.

Encourage direct communication.

Sales and Operations planning.

Finance and Operations forecasting.

Sales and Finance around margin and payment terms.

The stronger those relationships become, the fewer ordinary coordination issues need you.

Make managers responsible for developing management underneath them

This is crucial for the next stage.

If your Operations Manager personally solves everything within Operations, you simply moved the bottleneck down one layer.

Their team should develop.

Supervisors.

Team Leaders.

Project Managers.

Future managers.

CMI's professional standard treats developing people, succession planning, empowerment and delegation as core management capabilities.

Management should reproduce capability.

Not hoard it.

Ask every manager: who can cover you?

This is a wonderful question.

If you disappear for two weeks, who runs the function?

If answer:

"Nobody."

you found a risk.

It does not mean every company needs duplicate managers.

It means knowledge, authority and capability may be too concentrated.

A strong management structure gradually builds depth.

Succession planning is not only about replacing the owner

It applies inside management too.

Who could become the next Operations Manager?

Who can lead Sales if the manager leaves?

Who can chair the weekly meeting?

Who understands Finance when the Finance Manager is away?

Resilience matters.

A company that no longer depends on the owner but completely depends on one Operations Manager has only moved the dependency.

Watch for superstar managers becoming new bottlenecks

Develop managers deliberately

Do not assume a promotion produces management skill.

Help them learn:

Performance management.

Delegation.

Coaching.

Decision-making.

Commercial understanding.

Conflict.

Financial basics.

Planning.

Capacity.

Leadership.

Skills England's current Team Leader and Operations Manager standards both place substantial emphasis on developing people, solving problems, managing workloads and using information rather than simply supervising tasks.

Management is work.

Develop it.

UK policy still treats SME management development as important for a reason

Help to Grow: Management remains a national programme aimed specifically at improving SME leadership, management skills and firm-level productivity through structured learning, mentoring and peer learning.

Skills England's 2026 conversations with more than 150 SME leaders found a repeated tension: leaders want to grow, invest, develop people and improve operations while simultaneously handling customers, teams and the daily running of the company.

That tension is exactly why management depth matters.

The owner cannot permanently be both the person building the next business and the operating system for the current one.

Give managers commercial context

A manager can make technically correct decisions that are commercially terrible if they do not understand the business.

Operations saves £5,000 by delaying something and loses a £200,000 customer.

Sales wins revenue at terrible margin.

Finance saves cash by delaying an investment that removes a much larger capacity constraint.

Managers need context.

What are we trying to achieve?

Where does profit come from?

Which customers matter?

What risks matter?

What are the priorities?

Then they can make better trade-offs without you.

Share enough financial information for them to understand consequences

You do not necessarily need to expose every owner remuneration detail.

But managers responsible for commercial outcomes should understand relevant numbers.

Revenue.

Gross margin.

Labour.

Capacity.

Cash implications.

Department budgets.

Whatever helps them manage.

You cannot expect commercial decisions from people who only see operational activity.

Give the team a shared annual direction

What are the three to five important company priorities?

Not thirty.

For example:

Improve gross margin.

Reduce owner dependency.

Develop second-line management.

Increase capacity.

Improve cash conversion.

Then managers can use those priorities when decisions compete.

Without common priorities, every department optimises itself.

Translate annual priorities into 90-day commitments

A year is too long for operating management.

What needs to materially move this quarter?

Who owns it?

What evidence will show progress?

This gives the management team something beyond keeping today's business alive.

Otherwise operational noise wins.

Protect management-team time for improvement

If every meeting deals only with today's fires, structural problems remain.

Include recurring improvement.

What keeps happening?

What process needs redesigning?

Which dependency should be removed?

Which measure is deteriorating?

The ONS management framework treats continuous improvement as one of its four core dimensions of structured management.

Management teams should improve the machine.

Not merely operate it.

Build a rule: solve the cause, not just the week's problem

Customer complaint dealt with.

Fine.

Why did it happen?

Overtime approved.

Fine.

Why is capacity repeatedly short?

Margin down.

Why?

Vacancy open six months.

Why?

Management meetings should progressively remove recurring issues.

If the same agenda item appears every week for six months, you are discussing a problem.

Not managing it.

Do not let the owner become permanent meeting chair, note taker and action chaser

This recreates the old architecture.

Owner:

Sets agenda.

Chairs.

Decides.

Records actions.

Reminds everyone.

Management team attends.

That is owner management with witnesses.

Transfer pieces.

Someone else prepares data.

Managers bring issues.

Action ownership is explicit.

The team becomes responsible for maintaining its own rhythm.

Give each manager a proper one-to-one as well

The management-team meeting cannot replace individual management.

Managers still need:

Feedback.

Development.

Challenge.

Support.

Performance conversations.

Your one-to-one with the Sales Manager should cover their leadership and performance.

Not be a duplicate sales meeting.

Manage your managers.

Do not manage their departments for them.

Ask different questions in manager one-to-ones

Not only:

"What is happening?"

Try:

What are you worried about?

What decision are you avoiding?

Who on your team needs developing?

What keeps reaching you that should not?

What keeps reaching me that should stay with you?

Where are you the bottleneck?

What will be stronger in your function three months from now?

Now you are developing management capability rather than extracting status updates.

Managers need permission to make mistakes inside sensible boundaries

If every bad decision leads to the owner removing authority, nobody will decide.

You want managers making:

Good decisions.

Learning from imperfect ones.

Escalating appropriately.

Review significant misses.

Ask what was learned.

Adjust boundaries where necessary.

But do not expect independent management while demanding perfect foresight.

Separate poor judgement from reasonable judgement with a bad outcome

Those are not the same.

Manager considered evidence.

Stayed within authority.

Made a reasonable call.

Outcome unfortunate.

Learn.

Different scenario:

Ignored available information.

Exceeded authority.

Repeated known mistake.

That may be performance.

If managers believe every negative result equals punishment, they will send decisions upwards.

Dependency returns.

Decide what still belongs to the owner

This is important.

A management team does not replace ownership.

I would normally expect the owner to remain materially involved in things like:

Company direction.

Capital allocation.

Ownership and shareholder issues.

Major strategic risk.

Key senior appointments.

Critical strategic relationships.

Culture.

Major structural decisions.

Exactly where the boundary sits depends on the company.

The objective is not owner irrelevance.

It is owner concentration.

Owner-level decisions should become fewer and more important

That is a useful direction.

Instead of forty routine decisions a day:

Perhaps three consequential decisions a week.

That does not mean you contribute less.

The leverage of the decisions changes.

Your capacity moves towards:

Thinking.

Leadership.

Opportunity.

Risk.

Future capability.

That is what the management structure is supposed to create.

Do not replace owner dependency with CEO dependency either

Suppose you appoint a General Manager.

Everything that used to come to you now goes to them.

You step back.

Great?

Maybe.

If the entire organisation now depends on one General Manager to connect, remember and decide everything, you moved the problem.

The aim is an operating system.

Not finding one heroic substitute for the founder.

Be careful hiring a General Manager to solve a management-team problem

Sometimes it is absolutely the right move.

But ask:

Do we need a senior integrator?

Or have we simply failed to make existing managers accountable?

If your managers have never been given:

Clear roles.

Shared measures.

Decision rights.

A management rhythm.

Cross-functional responsibility.

then hiring above them may merely add another layer.

Fix architecture before assuming another salary solves it.

Likewise, do not expect an Operations Manager to run the entire company unless that is actually the role

Operations should own Operations.

If you expect that person to resolve:

Sales.

Finance.

HR.

Marketing.

Every customer.

Every employee.

Everything the owner does not want.

you may have created an impossible job.

Clarify structure.

Keep the management team small enough to manage

Not everybody senior needs to sit in every management meeting.

Too many people can produce:

Slow decisions.

Status reporting.

Poor accountability.

Meetings dominated by information irrelevant to half the room.

Who needs to be part of the core operating management team?

Then bring specialists in where relevant.

The exact number depends on the business.

The principle is decision usefulness.

Avoid management titles as rewards

"She's been here ten years, we should make her a manager."

Why?

Does the business need the role?

Does she want to manage?

Can she?

Management is not simply the next pay grade for being technically excellent.

Article #38 explored what happens when somebody receives the title without the job or capability.

Build management roles because the organisation needs management outcomes.

Test the management team with controlled owner absence

This is one of the best diagnostics.

Do not disappear for six months.

Try:

Half a day.

One full day.

Two days.

Eventually a week.

Define what genuinely warrants contacting you.

Then observe.

What happened?

Which decisions waited?

Which problems were resolved?

What information was missing?

Which manager stepped up?

Where did managers fail to coordinate?

Absence shows you dependency more clearly than discussing dependency.

Debrief after the test

Ask the team:

What did you need from me?

Why?

Could that authority move?

Could information improve?

What decision were you unsure about?

Where did you work together well?

What needs fixing before the next test?

Then strengthen the system.

Do not simply return and resume everything.

Build towards a 30-day owner test

Eventually, for a mature established business, an interesting strategic question is:

Could ordinary operations continue if the owner were unavailable for thirty days?

Not:

Would nothing go wrong?

Things will go wrong.

The question is whether the management team can:

See problems.

Decide.

Coordinate.

Escalate appropriately.

Protect customers.

Manage people.

Keep the company moving.

If not, what would need to exist?

That answer becomes your management-development roadmap.

A 90-day management-team build

In the first 30 days, define the architecture. Decide the core management seats, clarify the outcomes each role owns, map decision rights and establish a shared company scorecard. Identify the routine issues still unnecessarily reaching the owner.

During days 31 to 60, build the operating rhythm. Run a weekly management meeting around exceptions, decisions, risks and actions rather than status reports. Start redirecting cross-functional issues back to the relevant managers. Require recommendations with escalations.

During days 61 to 90, test independence. Transfer more decisions inside agreed authority, let somebody else chair parts of the management rhythm, create short periods of owner absence and review where dependency remains.

Do not judge success by whether you attended fewer meetings.

Judge it by what the business became capable of doing without you.

Measure management-team maturity

I would look for evidence like this.

Routine decisions increasingly stay with managers.

Employees use the right management route.

Managers challenge each other directly.

Cross-functional issues are solved without owner mediation.

The scorecard highlights problems before the owner discovers them.

Managers bring recommendations rather than raw problems.

Actions happen without owner chasing.

Managers develop capability underneath themselves.

The business can operate during owner absence.

That is progress.

Watch for false independence

The owner goes away.

Nobody calls.

Fantastic.

Returns.

Discovers managers postponed every difficult decision until Monday.

That is not independence.

That is a queue.

You want the team to make decisions inside authority.

Not freeze politely until you come back.

Your behaviour still matters enormously

You can design a perfect management system and destroy it in ten minutes.

Walk into Operations.

Give direct instructions to employees.

Override the manager.

Approve something inside their authority.

Set a different priority.

Managers learn:

The owner is still the real authority.

Article #40 made this point around owner role.

If you want a management team, behave as though you have one.

Every time you bypass a manager, notice it

Sometimes justified.

But ask:

Why did I do that?

Emergency?

Manager unavailable?

Habit?

I did not trust them?

Customer contacted me?

Then fix the underlying issue where appropriate.

Management structure is maintained through thousands of small behaviours.

Not the organisation chart.

Stop answering questions managers should answer for each other

Operations asks:

"What does Sales want to do?"

Don't translate.

"Speak to Sales."

Finance asks:

"Why has Operations done this?"

"Ask Operations."

It sounds almost childish written down.

But owners do this all day.

Stop being the relay.

Stop making decisions the team can make collectively

You may still need to approve the final choice.

But let them think.

For example:

"We have £150,000 available for investment. Operations wants equipment. Sales wants another salesperson. Finance wants to preserve cash. Come back with the management team's recommendation."

Now they have to understand each other's priorities.

That creates better managers.

A strong management team should eventually make the owner better too

This matters.

The objective is not merely reducing your workload.

You should gain:

Better information.

Different perspectives.

Constructive challenge.

Stronger decisions.

More time.

Greater resilience.

A management team should add intelligence to the company.

Not merely administer your instructions.

If everybody agrees with you all the time, be slightly suspicious

Perhaps you are exceptionally correct.

Possible.

Or perhaps managers learned disagreement is pointless.

Build an environment where someone can say:

"I don't think we should do that."

Then explain why.

You still make owner-level calls.

But informed challenge improves judgement.

How Evolve approaches building management teams

If an owner says:

"I've got managers but everything still comes back to me."

I do not automatically recommend another manager.

First I want to see:

Who owns what?

Which outcomes?

Which numbers?

Which decisions?

How do managers interact?

What happens when they disagree?

What goes into the weekly management meeting?

Who chairs it?

Who follows up actions?

What gets escalated?

Which employees bypass managers?

Where does the owner interfere?

Which manager is developing people underneath them?

What happens when the owner is absent?

That usually tells us a lot.

Sometimes the conclusion is:

You need a senior hire.

Sometimes:

One manager is not capable.

Sometimes:

Your structure is wrong.

Sometimes:

The managers are perfectly capable and you still haven't actually given them the business.

Different diagnosis.

Different intervention.

The objective is not creating dependence on me either

This is fundamental to how I think coaching should work.

If every decision in your company currently comes back to you, and six months later every decision you make comes back to me, we have not solved dependency.

We moved it.

A good management system should increase agency inside your business.

Managers think.

Managers decide.

Managers learn.

The owner gets challenged.

Eventually the company needs less outside help too.

That is success.

So, how do you build a management team that doesn't depend on you?

Stop thinking of management as a collection of people who report to the owner.

Give each manager clear outcomes.

Give them meaningful authority.

Give them useful information.

Create one shared view of company performance.

Make managers responsible for solving cross-functional problems together.

Define what genuinely needs owner escalation.

Require recommendations rather than raw problems.

Build a management meeting that produces decisions and accountability instead of five separate reports to you.

Develop managers.

Let them disagree.

Let them make reasonable mistakes.

Make them develop the next layer underneath themselves.

Test the structure by removing yourself for short periods.

Then fix whatever still depends unnecessarily on you.

And perhaps most importantly:

Stop stepping back into roles you already gave away.

Because the management team will never genuinely run the business while everybody knows the final answer is still easier to get from the owner.

Your goal is not a business without you.

You are the owner.

Your goal is a business where your presence is used for ownership-level contribution rather than ordinary operating necessity.

That is when managers stop being another layer of people for you to manage.

And start becoming the team that helps you run the company.

< 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.