Everything in your business keeps coming back to you because, somewhere in the organisation, responsibility stops.

Then it travels uphill.

That might happen because nobody knows who owns the decision.

Because managers have responsibility but not enough authority.

Because employees have learned that asking you is safer than making a judgement call.

Because information is poor.

Because the management team discusses problems without genuinely owning outcomes.

Because the people around you are not capable enough yet.

Or because every time the business hesitates, you step in and solve the problem faster than anybody else.

Usually it is a mixture.

The important point is this:

If everything comes back to you, the problem is not simply that you have too much work.

The business has built an escalation system with you at the top.

And unless you change that system, becoming more productive will merely help you process the dependency faster.

This normally starts because asking you works

Imagine an employee has a problem.

They could spend twenty minutes working it out.

They could ask their manager.

They could look at the process.

They could make a judgement call.

Or they could ask you.

You know the answer.

Thirty seconds later, the problem disappears.

From the employee's perspective, that was sensible.

From your perspective, it was efficient.

Do that enough times and the business learns:

When uncertain, ask the owner.

Nothing malicious happened.

Nobody avoided responsibility deliberately.

The organisation simply found the quickest available route.

You.

The problem gets worse because capable owners are bloody useful

This is why established owners often struggle with this more than they expect.

You know the company.

The history.

Customers.

People.

Margins.

Suppliers.

What happened last time.

Which exception matters.

Which one doesn't.

You can often see the answer before somebody else has finished explaining the problem.

That capability helped you build the company.

But if every difficult problem gets resolved by your capability, nobody else needs to develop the same depth of judgement.

They get the straightforward work.

You get the awkward bits.

Years pass.

You become extraordinarily good at handling the awkward bits.

Then you look around and think:

"Why can't anyone make a bloody decision without me?"

Sometimes the answer is that you have spent years making most of the difficult decisions.

The first cause: nobody really knows who owns the outcome

Responsibilities often look clearer on organisational charts than they are in real life.

Imagine you have a Sales Manager.

What exactly do they own?

Sales?

Fine.

Does that mean:

Revenue?

Gross margin?

Conversion rate?

Pricing?

Pipeline?

Salespeople?

Discounts?

Customer selection?

Credit decisions?

Recruitment?

What happens if sales volume is strong but margin is terrible?

Who owns that?

When responsibilities are described mainly as activity, grey areas emerge quickly.

Grey areas travel upwards.

If nobody is clearly accountable for an outcome, the person with the greatest authority normally inherits it.

The owner.

"We all own it" is usually a warning sign

Some things genuinely require collaboration.

That does not mean ownership should disappear.

Imagine customer retention belongs to:

Sales.

Operations.

Customer service.

The directors.

Everyone.

Great.

Who is the person expected to notice retention deteriorating and initiate action?

If the answer is:

"We'd all notice."

I would be nervous.

Collective involvement and individual accountability are not opposites.

A dozen people can contribute.

Someone still needs to own the result.

Otherwise problems drift until they become important enough to reach you.

The second cause: managers have responsibility without authority

This may be the biggest one.

You tell a manager:

"You are responsible for your department."

But they need your permission to:

Recruit.

Spend.

Change a supplier.

Deal with an underperforming employee.

Offer a customer credit.

Adjust a process.

Approve overtime.

Change priorities.

Make an exception.

So what does "responsible" actually mean?

They are responsible for the outcome while you retain control of the decisions affecting it.

Eventually they learn:

When anything significant happens, ask the owner.

Then you complain that everything comes back.

Responsibility and authority need to travel together.

Not unlimited authority.

Appropriate authority.

Give people actual decision boundaries

Instead of saying:

"You're responsible for purchasing."

Define what that means.

Perhaps:

You choose suppliers within our approved criteria.

You can authorise expenditure up to £5,000 within the agreed budget.

You can negotiate commercial terms.

You can change supplier without director approval where annual exposure remains below an agreed threshold.

Anything outside those boundaries requires escalation.

Now there is somewhere for the decision to live.

Clear decision rights are far more useful than repeatedly asking people to "step up."

Research into management and decentralisation supports the broader principle that better information and clearer management systems make delegation easier. In a well-known field experiment involving large Indian textile firms, improved management practices increased information flow and were followed by greater delegation of decisions from owners to middle managers. The firms and setting differ substantially from British SMEs, so the study's numerical performance effects should not simply be applied to your business. The useful lesson is that owners were more able to decentralise when they had better information and management systems.

The third cause: nobody knows when they are supposed to escalate

Businesses often have no designed escalation system.

So employees use judgement.

Some bring you virtually everything.

Others tell you nothing until the building is metaphorically on fire.

Neither is particularly useful.

Define what actually deserves owner involvement.

For example:

Serious legal or regulatory exposure.

Significant safety concerns.

Major cash-flow risk.

A strategically important customer at genuine risk of leaving.

Expenditure outside agreed authority.

A serious senior-management issue.

Something outside established commercial limits.

Everything else should have somewhere else to go.

You are not trying to stop escalation.

You are trying to turn escalation into an exception rather than the normal operating model.

The fourth cause: managers escalate problems instead of recommendations

There is a huge difference between these two conversations.

Conversation one:

"We've got a problem with the Smith job. What do you want us to do?"

Conversation two:

"We've got a problem with the Smith job. We've looked at three options. I recommend we move the work to Thursday, absorb the additional £600 cost and speak to the client today. The alternative creates a bigger delivery risk. Are you comfortable with me proceeding?"

The second manager is still involving you.

But they are doing the thinking first.

That is progress.

Eventually, perhaps the decision fits entirely within their authority and they simply tell you what they decided afterwards.

Do not expect people to jump instantly from:

"Tell me what to do."

to:

"I've handled everything."

Move them through stages.

Problem.

Options.

Recommendation.

Decision.

Ownership.

Ask for the recommendation before giving the answer

This is one of the smallest changes an owner can make.

A manager brings you a problem.

Do not immediately solve it.

Ask:

"What do you recommend?"

You may discover they already know.

If they don't, ask:

"What options have you considered?"

You are not trying to make a five-minute conversation unnecessarily philosophical.

You are discovering whether the dependency is:

Knowledge.

Confidence.

Authority.

Or habit.

If they know what should happen and simply want you to bless it, continuing to make the decision for them reinforces the wrong behaviour.

The fifth cause: your organisation has weak management information

Owners often keep decisions because giving them away feels like losing control.

That feeling may be perfectly reasonable.

Suppose you personally monitor production because there is no useful production reporting.

Someone says:

"Stop interfering. Trust your team."

Fine.

Now you know less and have no reliable alternative source of information.

That is not good delegation.

It is blindness.

If you want decisions to move away from you, you need enough visibility to know whether outcomes remain healthy.

The latest ONS Management and Expectations Survey measures structured management through areas including continuous improvement, KPI use, targets and employment practices. Firms with more employees reported higher average management-practice scores, and stronger scores were statistically associated with higher productivity. The survey does not prove that adding KPIs causes productivity, but it does demonstrate the close relationship between structured management and how larger organisations operate.

The UK Government's current SME strategy makes a similar point, identifying strong leadership and structured management practices such as targets, KPIs and strategic financial planning as important drivers associated with SME productivity and growth.

You do not need fifty KPIs.

You need enough information to stop using personal involvement as your primary management-control system.

The sixth cause: your managers are coordinators rather than managers

Job titles can hide this for years.

You have:

An Office Manager.

Sales Manager.

Production Manager.

Contracts Manager.

Service Manager.

Everyone looks managed.

But what do they actually do?

Perhaps they:

Allocate work.

Answer questions.

Attend meetings.

Pass information around.

Update you.

Then whenever somebody:

Underperforms.

Needs challenging.

Makes a difficult decision.

Creates conflict.

Misses a target.

Needs prioritising.

Requires a commercial judgement.

The issue comes to you.

The manager coordinates normal activity.

You remain the manager whenever management becomes difficult.

That is why everything comes back.

Management means owning difficult things too

A manager should not need the owner every time:

Someone is unhappy.

An employee pushes back.

A deadline slips.

Two priorities conflict.

Performance drops.

A customer complains.

A decision carries some risk.

That is the job.

Obviously, managers need boundaries and support.

But if their role only works while everything is straightforward, they do not yet own the full responsibility.

You need to decide whether the cause is:

Role clarity.

Authority.

Training.

Confidence.

Experience.

Capability.

Or the wrong person.

Then address that cause.

The seventh cause: you keep bypassing your managers

This one belongs to the owner.

An employee comes directly to you.

You answer.

You have just created two problems.

First, you accepted responsibility for something that may not belong to you.

Second, you weakened their manager.

The employee has learned:

Going directly to the owner works.

The manager has learned:

Their team can bypass them.

Do that repeatedly and the actual organisation stops resembling the organisational chart.

If somebody brings you something that belongs with their manager, ask:

"What did Claire say?"

If the answer is:

"I haven't asked her."

send them back.

Not rudely.

Consistently.

Authority becomes real partly because the owner behaves as though it is real.

The eighth cause: people know you will rescue them

This is the Fixer Loop again.

Something does not happen.

You remind them.

Something is late.

You sort it.

Someone has not prepared.

You step in.

A manager avoids a conversation.

You eventually have it.

An employee makes a mess of something.

You clean it up.

The business learns:

Dropped responsibility eventually lands with the owner.

So why would responsibility feel truly heavy anywhere else?

If you want accountability, you have to stop catching everything.

That does not mean allowing serious commercial damage to prove a point.

It means making the original owner of the responsibility stay involved in resolving the consequence.

If they miss the deadline, they explain it.

If they create the customer problem, they help resolve it.

If they fail to prepare, they experience the uncomfortable meeting.

Accountability disappears when the owner quietly absorbs the consequences.

Your helpfulness can become a management problem

This is uncomfortable because helping people sounds like good leadership.

Often it is.

But help has different forms.

Someone says:

"I don't know how to handle this customer."

You can:

Take the customer call yourself.

Or help them prepare to take it.

Both help.

Only one develops capability.

Someone says:

"I don't know how to structure the management report."

You can create it.

Or help them build the first one.

Both solve today's problem.

Only one leaves ownership in the right place.

Good leadership is not refusing to help.

It is helping in ways that do not unnecessarily transfer responsibility back to you.

The ninth cause: every mistake causes centralisation

This destroys delegation incredibly quickly.

You finally give somebody authority.

They make the wrong call.

The owner thinks:

"I knew this would happen."

Authority removed.

From now on, that decision comes back to you.

What has the organisation learned?

Making a mistake costs autonomy.

The safest future strategy becomes:

Ask first.

That is not to say people should repeatedly make expensive mistakes without consequences.

But distinguish:

A reasonable judgement call that produced the wrong outcome.

A capability problem.

Negligence.

Lack of information.

An unclear rule.

A broken process.

The solution depends upon the cause.

Do not make permanent centralisation the automatic response to every imperfect decision.

You make imperfect decisions too.

You still let yourself decide things tomorrow.

The tenth cause: standards exist only in your head

Someone completes a piece of work.

You look at it.

"It's not right."

What isn't?

"You know... it just isn't how we do it."

Do they know?

Founders accumulate standards intuitively.

You recognise a good quote.

A good customer email.

A well-planned job.

A sensible purchase.

A credible recruit.

Someone else may not see the same things.

If the standard matters, make some part of it visible.

Examples.

Checklists.

Rules.

Templates.

Decision principles.

Training.

Review criteria.

Not everything needs an SOP.

But people cannot consistently meet expectations that exist only as a feeling inside the owner's head.

The eleventh cause: you have trained people to optimise for your approval

This is a cultural problem.

Employees begin thinking:

"What will Adam want?"

instead of:

"What outcome does the business need?"

That may sound similar.

It isn't.

The first creates dependency.

The second creates judgement.

If people are constantly trying to predict your personal preference, every ambiguous situation naturally comes back to you.

You want principles and outcomes strong enough that people can decide without psychologically simulating the owner.

That requires clarity about:

Commercial priorities.

Values.

Risk tolerance.

Standards.

Customer expectations.

Decision boundaries.

The more predictable those are, the less the business needs to consult the person who created them.

The twelfth cause: sometimes your people genuinely aren't ready

Not everything is a leadership lesson for the owner.

Some managers are not capable enough for the roles they occupy.

Some people avoid responsibility.

Some lack judgement.

Some do not want more authority.

Some were promoted because they were loyal or technically strong rather than because they could manage.

If you give a person clear responsibility, sensible authority, useful information, development and repeated opportunities to perform and everything still comes back, deal with that honestly.

Train them.

Move the responsibility.

Change the role.

Recruit above them.

Replace them if necessary.

You cannot build an independent company around people who are fundamentally unwilling or unable to make appropriate decisions.

The thirteenth cause: the company has outgrown informal management

This is enormously common.

When the business was small, everyone knew everything.

Somebody shouted across the room.

The owner decided.

Done.

Brilliantly efficient.

Then you grew.

Ten employees.

Twenty.

Forty.

Several locations.

Departments.

More customers.

More managers.

But the operating model still assumes information eventually reaches the founder.

Informality stops scaling.

The Government's current small-business strategy explicitly notes that smaller firms are less likely than larger organisations to use structured management practices and identifies building leadership and management capability as a priority for SME growth.

You do not need to become corporate.

You do need enough structure for twenty people to make sensible decisions without continuously recreating conversations that were easy when there were five.

The four questions to ask every time something comes back to you

When a problem lands on your desk, ask:

Why did this reach me?

Who should normally own it?

What prevented them from owning it this time?

What needs to change so the next one doesn't reach me?

That final question is the important one.

You can solve the current problem.

Then solve the system that produced the escalation.

That is the difference between working harder and creating agency.

The first empties your inbox today.

The second changes what enters it tomorrow.

Do not solve recurring problems one at a time

Imagine approving overtime becomes a constant interruption.

You could continue deciding each request.

Five minutes here.

Three minutes there.

Or you could define:

Who owns labour planning?

What budget do they control?

At what level does overtime need approval?

What conditions justify it?

What reporting shows whether the system is working?

Now you solve the category.

Owners stay overloaded partly because they repeatedly solve individual instances of problems that could be redesigned once.

Look for repeated questions

Repeated questions are gold.

Someone asks once:

Fair enough.

They ask five times:

You may have a system problem.

If the same type of issue keeps returning, something is missing.

A rule.

A decision right.

Information.

Training.

A process.

Clear ownership.

Do not become annoyed that people keep asking.

Use the repetition as evidence.

The business is showing you exactly where dependency lives.

Introduce a recommendation rule for managers

One simple change can dramatically improve the quality of escalation.

No manager brings an ordinary problem without a recommendation.

Not:

"Here's the issue. What do you want?"

Instead:

"Here's the issue. Here are the relevant facts. This is what I recommend and why."

You may disagree.

Good.

Now you have something to coach.

You can ask:

What did you consider?

What risk did you weigh?

Why this option?

Over time, judgement develops.

If you simply provide the answer each time, your judgement develops instead.

You already have plenty.

Build management meetings that move responsibility down rather than problems up

A bad management meeting can become an escalation factory.

Each manager brings problems.

Owner solves them.

Everyone leaves with actions.

Owner has seventeen.

The meeting appears productive.

It is actually centralisation.

A stronger meeting asks:

What outcome is off track?

Who owns it?

What do they propose?

What decision do they need from the group?

What specifically requires director input?

The owner should not automatically become the action owner because they are the most senior person in the room.

If your action list grows after every management meeting while everyone else's shrinks, inspect the meeting.

Stop letting "can you just..." run your company

Can you just check this?

Can you just call them?

Can you just approve it?

Can you just look at this?

Can you just deal with Steve?

Can you just come into the meeting?

Individually, tiny.

Collectively, a business model.

Each "just" removes a little responsibility from somewhere else and moves it towards the owner.

Start noticing them.

The size of the request is not the important part.

The direction of responsibility is.

Create an escalation budget for yourself

This does not need to be formal.

Set a target.

Perhaps you currently receive fifty operational decisions or approval requests each week.

Aim for forty.

Then thirty.

Not by ignoring them.

By removing categories from the escalation route.

Maybe purchasing below £2,500 no longer requires you.

That removes ten.

Routine customer credits move to the Commercial Manager.

Another five.

Recruitment within approved headcount moves to managers with HR support.

Another four.

The aim is not escaping responsibility overnight.

It is deliberately reducing the volume of work that requires owner-level attention.

Measure decisions, not only tasks

Most owners know what tasks they have delegated.

Very few know how many decisions still reach them.

Start measuring.

For one week:

How many times did someone need your decision before they could continue?

Which categories dominated?

How many genuinely required owner authority?

This can be extremely revealing.

You may discover you barely perform operational tasks anymore.

Yet the company still requires you to make sixty operational decisions every week.

You have delegated labour.

Not control.

When should things still come back to the owner?

Plenty of things.

You should not become impossible to reach because an article told you to delegate.

Your involvement may remain sensible for:

Major strategic changes.

Large capital commitments.

Ownership decisions.

Serious legal or regulatory matters.

Significant safety issues.

Major financial risk.

Senior leadership appointments or exits.

Acquisitions.

Potentially critical customer relationships.

Anything genuinely outside management authority.

Good management does not eliminate escalation.

It improves its quality.

You want fewer things reaching you.

But the things that do reach you should increasingly deserve your attention.

What if everything comes back because I am still the best person?

You probably are the best person at some of it.

That is not the test.

The question is:

Should the business permanently require its most senior and scarce resource for this decision?

You might be the best person in the company at writing a customer proposal.

Should you write every proposal forever?

You might be the best problem solver.

Should every problem therefore reach you?

You might conduct the best management meeting.

Should no one else learn to run one?

If your personal superiority becomes the reason nobody else gets ownership, the gap never closes.

There comes a point where the owner needs to stop optimising purely for today's quality and start building tomorrow's capacity.

How do you know whether to coach, train or replace a manager?

Start with four questions.

Do they understand the expected outcome?

Do they have the authority required to achieve it?

Do they have the information and resources?

Do they have the capability and willingness?

If the first three are missing, fix the environment before blaming the person.

If all four are present and performance remains poor, you have a different conversation.

Too many businesses jump from:

"This keeps coming back to me."

straight to:

"My managers are useless."

Maybe.

Prove it.

When does this become an organisational-structure problem?

Sometimes there is simply nobody for responsibility to land with.

Perhaps five department heads all report directly to you.

Cross-departmental problems naturally come to you because nobody else sits across the organisation.

That may mean you need:

An Operations Manager.

General Manager.

Operations Director.

Fractional COO.

Different leadership structure.

Articles #14 and #15 explore those choices in detail.

Delegation requires a destination.

Do not criticise responsibility for travelling upwards if there is literally nowhere else for it to go.

When is the owner the main thing that needs to change?

When you already have:

Capable managers.

Clear roles.

Reasonable systems.

Useful information.

Enough resources.

Yet you still insert yourself.

People make decisions and you change them.

Managers handle issues and you reopen them.

Employees bypass managers and you answer them.

You say you want ownership but struggle whenever somebody owns something differently.

Then the organisational work may largely be done.

The leadership work is yours.

That can be harder.

You cannot buy software to solve it.

Why owners struggle to change this even when they know exactly what is happening

Because the current system rewards you too.

You feel useful.

Competent.

Needed.

In control.

Problems disappear quickly.

Changing the system creates short-term discomfort.

Decisions take longer.

People make mistakes.

You know less detail.

Someone else handles a conversation differently.

The company initially feels less efficient.

That discomfort tempts the owner to step back in.

Then things become fast again.

Which appears to prove:

"See? They need me."

No.

It proves you remain very good at doing the old job.

The goal is not to stop people coming to you

This matters.

You do not want a culture where the owner becomes inaccessible and managers hide problems because they are terrified of escalating.

That is equally unhealthy.

You want better conversations.

Instead of:

"What should I do?"

you increasingly hear:

"Here's what I've decided."

Or:

"Here's what I recommend."

Or:

"I need your input because this is outside my authority for these specific reasons."

That is what progress sounds like.

A 30-day plan to stop everything coming back to you

Week 1: Capture the traffic

Record every question, decision, approval and problem that reaches you.

Do nothing clever.

Just capture it.

Week 2: Find the patterns

Group them.

Pricing.

People.

Purchasing.

Customers.

Quality.

Scheduling.

Finance.

Whatever appears.

Identify the three biggest categories.

Week 3: Remove one route

Choose a frequent, relatively manageable category.

Define:

Who owns it.

What authority they have.

What information they need.

What should still be escalated.

Tell everyone affected.

Week 4: Change your behaviour

When the category comes back to you anyway, do not automatically answer.

Route it to its new owner.

At the end of the month, review what worked and what failed.

Then repeat.

This will not transform a heavily owner-dependent company in thirty days.

It will prove that responsibility can move.

How Evolve approaches the problem

When an owner tells me:

"Everything comes back to me."

I do not automatically tell them to delegate more.

I want to know why.

What comes back?

Through whom?

What decisions?

What happens if you don't answer?

What authority exists?

What do managers genuinely own?

What do you keep taking back?

What information can you see?

How are people held accountable?

Where are the capability gaps?

Is there actually a missing role?

That diagnosis matters because the intervention changes completely.

You may need:

Better managers.

Clearer responsibilities.

Decision rights.

A scorecard.

An Operations Manager.

A different management meeting.

Training.

Recruitment.

Or simply a new rule that says:

Stop answering questions that no longer belong to you.

This is where capable owners get trapped.

They see a problem.

They can fix it.

So they do.

Again.

And again.

And again.

Eventually they become the system.

My job is not to make you less capable.

It is to help you stop using your capability in ways that prevent the organisation developing its own.

So, why does everything in your business come back to you?

Because responsibility currently has nowhere else reliable enough to stay.

Maybe ownership is unclear.

Maybe authority is too restricted.

Maybe managers are not strong enough.

Maybe information is weak.

Maybe escalation rules do not exist.

Maybe you bypass management.

Maybe you keep rescuing people.

Maybe everyone has learned that asking you is simply the easiest option.

Find which of those is happening.

Then change the route.

Clarify what each person owns.

Give them the authority required to own it.

Improve information so you can delegate without becoming blind.

Require recommendations rather than raw problems.

Strengthen managers where they need development.

Deal honestly with managers who cannot perform.

Create clear escalation boundaries.

And most importantly, stop automatically accepting every piece of responsibility the business offers back to you.

Because every time you say:

"Fine, I'll sort it."

you are not merely solving today's problem.

You are teaching the company where tomorrow's problem should go.