There is a point in the growth of some businesses where the owner is no longer trapped because the company needs them.

They are trapped because part of them still needs to be needed.

That is a very different problem.

The business may now have capable managers.

Good employees.

Systems.

Enough experience.

Enough information.

Enough people to make decisions.

Yet everything still comes back to the owner.

Quotes.

Problems.

Customers.

Hiring decisions.

Purchases.

Complaints.

Technical questions.

Approvals.

Not always because nobody else could handle them.

Sometimes because the owner has spent so many years being the person who handles everything that stepping away begins to threaten something deeper than their workload.

Their role.

Their status.

Their sense of usefulness.

Their identity.

This is what I call Fixer Identity.

It develops when being the person who solves the problem stops being merely something you do and quietly becomes part of who you believe you are.

And if you do not recognise it, you can spend years trying to build a business that depends less on you while unconsciously recreating reasons for it to keep pulling you back in.

Being needed is not automatically a problem

Let's start here.

New businesses frequently do need the owner.

Of course they do.

You may be:

The salesperson.

Technical expert.

Estimator.

Customer service department.

Operations manager.

Finance director.

Recruiter.

Marketing department.

Tea maker.

Occasional unqualified IT technician.

That is completely normal.

Early-stage businesses often depend heavily on founder knowledge, relationships, energy and decision-making.

The problem begins when the company grows but the owner's role does not evolve with it.

The business has 5 people.

Everything comes through you.

Then 15.

Everything still comes through you.

Then 30.

Still you.

Then you employ managers to reduce your workload but require them to check every meaningful decision with you.

You have technically built a management team.

Functionally, you have built a more expensive notification system.

The business may once genuinely have needed you

This is what makes the problem difficult to spot.

You aren't imagining your importance.

For years, being involved in everything may have been precisely what made the company successful.

You knew every customer.

You understood every job.

You spotted problems early.

You could price from experience.

You knew which employee could handle what.

You remembered why a particular process existed.

When something went wrong, you could solve it quickly.

Being the fixer was useful.

It was probably rewarded.

Customers asked for you.

Employees came to you.

Suppliers knew you.

Problems disappeared when you got involved.

Revenue grew.

People thanked you.

You received continuous evidence that your involvement improved outcomes.

Why would you stop?

Because eventually the behaviour that helped build the business can become the behaviour stopping it growing beyond you.

Capability can become a trap

Some owners become bottlenecks because they are poor leaders.

Others become bottlenecks because they are exceptionally capable.

The second group is more interesting.

You see the problem quickly.

You already know the answer.

You can probably solve it in ten minutes.

Teaching somebody else might take an hour.

So you solve it.

Perfectly rational.

Tomorrow another problem appears.

Same calculation.

You solve that too.

After a few years, everyone has learned something.

Adam knows.

Or Sarah.

Or James.

Or whoever the owner happens to be.

So questions naturally travel towards the person most likely to provide the answer.

The owner then concludes:

“See? They still need me.”

But that isn't necessarily evidence of dependency.

It may be evidence of conditioning.

You trained the organisation where to take uncertainty.

What is Fixer Identity?

Fixer Identity is not a clinical diagnosis.

It isn't a personality disorder.

And I am not using the phrase to suggest there is something psychologically wrong with business owners who experience it.

It is a practical way of describing a pattern I have seen in business, coaching and myself.

The pattern looks roughly like this:

I am valuable because I solve problems.

Then:

People rely on me because I solve problems.

Then:

Being relied upon becomes evidence that I am valuable.

At that point, removing dependency can feel surprisingly uncomfortable.

Logically, you want fewer interruptions.

Emotionally, being excluded from decisions can feel strange.

Logically, you want managers to take ownership.

Emotionally, you may feel irritated when they make a decision without asking.

Logically, you want a business that can operate without you.

Then you take a week off and check your phone every twenty minutes to make sure it hasn't.

That contradiction is more common than owners like admitting.

Founder identity is real

There is a serious research base behind the broader idea that entrepreneurship can become intertwined with identity.

Entrepreneurship researchers have long examined founder role identity, meaning the extent to which being a founder becomes integrated into someone's wider sense of self. Research has explored how the centrality of that identity influences founder behaviour, persistence and role transitions.

More recent research continues to treat founder identity as something dynamic rather than fixed. A 2026 Journal of Business Venturing study, for example, examined how founders can actively renegotiate their relationship with entrepreneurial identity over time. It was a qualitative study in a particular entrepreneurial context, so it should not be treated as evidence that every business owner follows the same path, but it reinforces an important point: founder identity can evolve.

That matters because you do not need to stop caring about your company.

You do not need to become detached from the thing you spent years building.

You need to allow your role inside it to change.

Ownership and control become intertwined

There is another useful body of research around psychological ownership.

This is the feeling that something is psychologically “mine”, beyond simply owning it legally.

That is hardly surprising for founders.

You conceived the business.

Built it.

Risked money.

Lost sleep.

Won the customers.

Employed the people.

Survived the awful months.

Perhaps put your house or personal finances at risk.

The company can understandably feel like an extension of you.

A qualitative study published in Applied Psychology, based on interviews with 30 founders and 14 professional managers, specifically examined what happens when growing founders delegate decision rights. The researchers found that successful delegation involved founders recalibrating their sense of psychological ownership and undertaking what they described as identity work as control moved towards professional managers.

That language is useful.

Recalibrating ownership.

Not abandoning it.

Not ceasing to care.

Not disappearing.

Changing what ownership means as the company grows.

The problem is not that you care too much

I dislike the simplistic advice that founders should simply:

“Let go.”

Let go of what?

Responsibility?

Standards?

Interest?

Commercial judgement?

The business they own?

Of course not.

The owner should care.

The question is what caring looks like at the current stage of the company.

When you employed three people, caring might have meant personally checking every important job.

With fifty people, caring might mean building managers capable of creating quality without your inspection.

At £500,000 turnover, personally knowing every customer's situation might have been a strength.

At £8 million, insisting that significant customers still come directly to you might prevent anybody else building those relationships.

The behaviour changes.

The responsibility doesn't disappear.

Ask yourself how you react when nobody needs you

This is one of the easiest ways to spot Fixer Identity.

Imagine you take Friday off.

Nobody calls.

Nobody messages.

No crisis.

Your managers make several decisions.

A difficult customer problem gets resolved without you.

Monday arrives and everything is fine.

What do you feel?

Relief?

Pride?

Or a tiny, uncomfortable feeling that perhaps you weren't particularly necessary?

That reaction is worth noticing.

Not judging.

Not dramatising.

Just noticing.

Because many owners say they want independence while measuring their personal importance by how often the business asks for them.

You cannot optimise for both.

Another test: how do you feel when someone decides differently?

Your manager makes a perfectly reasonable decision.

It is not the decision you would have made.

But the outcome is good.

Do you leave it alone?

Or immediately explain how you would have done it?

This sounds minor.

It isn't.

Every time a manager makes a reasonable decision and receives a lesson in why your decision would have been better, they learn:

Next time, ask first.

You then complain that nobody takes ownership.

This is how dependency gets recreated.

People do not need freedom only to make the decisions you would have made.

That is not authority.

That is delegated mind-reading.

There is a difference between wrong and different

This matters enormously.

If an employee's decision exposes the company to serious risk, creates unacceptable cost or breaks an important standard, intervene.

But if their approach is simply different?

Let it be different.

Perhaps they choose Supplier B.

You would have chosen Supplier A.

Both are acceptable.

Perhaps they resolve a customer complaint with a credit rather than replacement.

Both fall inside sensible authority.

Perhaps they schedule the project differently.

The project still works.

Managers cannot develop while every decision is compared against an invisible answer sheet stored inside the owner's head.

If you want people capable of running the business, they need room to develop judgement.

Judgement requires decisions.

Signs the business might not need you as much as you think

None of these proves anything individually.

But several together deserve attention.

You regularly answer questions before the responsible manager can respond.

You are copied into emails that do not require you.

You insist on approving spending well below any meaningful risk threshold.

Important customers know to bypass everyone and contact you directly.

Employees ask your permission for routine decisions.

Managers have responsibility but narrow authority.

You regularly rewrite work somebody else has already completed.

You take tasks back when someone struggles rather than coaching them through the difficulty.

You struggle to stay away from the business while on holiday.

You feel nervous when sales conversations or key meetings happen without you.

People say:

“I'd better check with the owner.”

far too frequently.

You complain that employees lack initiative but frequently overturn their decisions.

You recruit experienced managers and then keep performing large parts of their role.

You remain the holder of important information that could easily exist somewhere else.

You solve recurring problems personally rather than changing the system that repeatedly creates them.

You are exhausted by being needed.

And strangely uncomfortable when you're not.

That final combination is the interesting one.

Beware of becoming the hero in your own business

Firefighting can be incredibly rewarding.

Problem appears.

Everyone worries.

You intervene.

Problem disappears.

Immediate feedback.

Visible usefulness.

That is psychologically much cleaner than long-term leadership.

Building management capability can take months.

Redesigning a process may produce no applause.

Training somebody can initially take longer than doing the work yourself.

Removing yourself from a decision creates no heroic moment.

The company simply works.

Good systems are often boring.

Which is exactly why the fixer can accidentally prefer the fire.

Not consciously.

Nobody deliberately thinks:

I hope something goes wrong today so everybody remembers how useful I am.

But if urgent problem-solving has provided status, certainty and satisfaction for years, quiet competence can feel oddly flat by comparison.

I recognise this because I lived a version of it

For years, I would have described one of my greatest strengths as work ethic.

And it was.

I worked ridiculous hours.

Solved problems.

Made myself available.

Took responsibility.

If something needed dealing with, I dealt with it.

That capability helped me progress very quickly and eventually run a substantial company.

But there is a darker side to becoming the person who always fixes things.

Eventually everything can start finding its way towards you.

And because you can deal with it, you do.

Again.

And again.

And again.

Until being indispensable stops feeling like a compliment and starts feeling like captivity.

I eventually found myself working 60 to 65-plus hour weeks, waking at 2am thinking about problems and living with a level of permanent availability that I had gradually accepted as normal.

The lesson I eventually learned was not that working hard was wrong.

I still believe enormously in work ethic.

The lesson was that being capable enough to carry everything does not mean carrying everything is good leadership.

Work ethic works hard inside the system.

Agency asks whether there is a better system.

That distinction changed a lot for me.

You may be protecting your identity rather than your quality standards

This is another uncomfortable possibility.

Owners often explain excessive involvement using quality.

“Nobody cares as much as I do.”

Probably true.

They don't own it.

That does not mean they cannot produce excellent work.

“Nobody will do it exactly like me.”

Definitely true.

They are not you.

That is not automatically a problem.

“It's quicker if I do it.”

Today, probably.

Across the next five years, almost certainly not.

Ask:

What standard am I genuinely protecting?

Then:

Could that standard be defined, taught, measured or reviewed without requiring me personally?

If yes, the problem is not quality.

It is system design.

The owner often becomes the quality-control system

This is common in businesses that grew through founder expertise.

The founder carries an enormous invisible database.

They just know.

They know what looks right.

What margin is acceptable.

Which customers are risky.

Which employees can handle something.

Which quote seems wrong.

Which supplier needs checking.

That experience is valuable.

But if the experience remains entirely inside the owner, the company never truly owns it.

Turn your judgement into:

Criteria.

Thresholds.

Checklists.

Decision rules.

Training.

Examples.

Management information.

Escalation triggers.

You are not trying to convert twenty years' experience into a 12-page procedure manual.

Some judgement will always remain human.

You are trying to stop every ordinary decision requiring access to one particular human.

Give people boundaries, not unlimited freedom

Reducing dependency does not mean:

“Everyone can do whatever they want.”

Good delegation needs boundaries.

A manager might have authority to:

Approve expenditure below £5,000.

Resolve customer credits below a defined level.

Recruit within an agreed salary band.

Select from approved suppliers.

Change schedules provided customer deadlines remain protected.

Escalation occurs when:

The financial exposure exceeds X.

The safety risk changes.

A legal issue appears.

A key customer relationship is threatened.

The decision affects another department materially.

Now the manager has something useful.

Not:

Use your initiative, but check with me first.

Watch what you do when delegation goes wrong

Eventually somebody will make a mistake.

This is unavoidable.

Your reaction matters enormously.

If the first imperfect delegated decision causes you to reclaim authority, you will prove to yourself that delegation doesn't work.

You will also prove to everyone else that authority was temporary.

Ask:

Was the mistake reasonable?

Was the boundary clear?

Did they have enough information?

Were they properly trained?

Was the decision negligent, or simply wrong in hindsight?

What needs changing so they can make a better decision next time?

Sometimes the answer is performance management.

Sometimes somebody genuinely isn't capable.

But do not treat every error as evidence that only you can be trusted.

You made plenty of mistakes learning to run the business.

Other people need some room to learn too.

Psychological ownership can make delegation genuinely difficult

Recent research gives this challenge useful context.

A 2026 study involving 186 entrepreneurs and 47 matched co-founders examined factors influencing delegation of decision-making authority. Among the factors studied were founders' psychological ownership, their perceptions of employee capability and responsibility, workload and perceived business risk. The sample involved startup entrepreneurs in Pakistan, so it should not be treated as directly representative of established British SMEs, but it reinforces the broader point that delegation is not simply a mechanical question of workload. Ownership, trust, perceived capability and risk all influence whether founders hand over authority.

That is why another delegation template rarely solves the deepest version of the problem.

Sometimes the business systems are ready.

The owner isn't.

Ask what your managers are actually allowed to own

Look at every manager in the business.

What outcomes do they own?

What decisions can they make without you?

What spending authority do they have?

What mistakes are they allowed to make?

Which people decisions belong to them?

Which customers can they deal with independently?

What information do they receive?

What decisions still come to you?

Then ask the uncomfortable question:

Are they genuinely managing, or administrating decisions for me?

There is a huge difference.

A management team cannot become capable of running the business if the owner retains every meaningful decision.

The dependency may feel reassuring to both sides

This is worth acknowledging.

Owner dependency is not always imposed.

Employees can like it too.

Taking a difficult decision carries risk.

Asking the owner transfers that risk upwards.

The owner gets to feel useful.

The employee gets protection.

Everyone receives a short-term benefit.

The company pays the long-term cost.

That is how dependency becomes stable.

Removing it means both sides must change.

The owner has to tolerate not controlling every answer.

The employee has to tolerate becoming accountable for decisions.

That can initially feel less comfortable for everybody.

Do it anyway.

What does owner dependency cost?

Quite a lot.

It slows decisions

Everything waits until you are available.

It limits scale

The capacity of the organisation becomes linked to your personal capacity.

It weakens managers

Why develop judgement if meaningful decisions ultimately move upwards?

It makes recruitment harder

Experienced managers do not remain enthusiastic forever if they discover they were recruited to carry responsibility without authority.

It increases key-person risk

Illness, holidays or unexpected events become operational threats.

It damages succession

There is no obvious route towards a management-led company if management never receives enough authority to lead.

It affects enterprise value

A buyer is purchasing a business.

If the customers, knowledge, decisions and relationships disappear when you do, they may reasonably question exactly what they are buying.

It consumes your attention

Every minor decision occupies space that could have been used for something only the owner really can do.

That last one matters.

You can spend the day being incredibly useful while doing almost nothing that genuinely required the owner of the company.

There is a difference between being important and being involved

Owners sometimes equate stepping back with becoming irrelevant.

You can be enormously important without touching everything.

A great owner may determine:

Direction.

Capital allocation.

Leadership standards.

Major risk decisions.

Management appointments.

Strategic relationships.

Culture.

Long-term commercial choices.

They do not therefore need to approve replacement office chairs.

Your importance should increasingly come from the quality of the system you built, not the volume of tasks still travelling through you.

That is a very different definition of usefulness.

What should replace Fixer Identity?

Not detachment.

Not laziness.

Not indifference.

I would replace it with something closer to architect identity.

The fixer asks:

How do I solve this problem?

The architect asks:

Why did this problem need me?

The fixer resolves the customer complaint.

The architect notices that the fifth similar complaint probably indicates a process issue.

The fixer answers the manager's question.

The architect creates clearer decision boundaries so the next question never needs asking.

The fixer makes the company work today.

The architect makes tomorrow require less fixing.

You still solve things.

You just become more selective about which level of problem deserves you.

Run the “What breaks without me?” test

Imagine you disappear from day-to-day operations for four weeks.

Not dead.

Not abducted.

Just completely unavailable.

What genuinely breaks?

List it.

Perhaps:

Major quotes cannot be approved.

Payroll still requires your authorisation.

Three customers only deal with you.

Nobody can recruit managers.

Purchases above £2,000 stop.

Technical exceptions require your knowledge.

Certain supplier negotiations stall.

Good.

That is useful information.

Now separate the list into three categories.

Things that should genuinely remain owner-level

Fine.

Keep them.

Things somebody else could own with authority or training

Build the capability.

Things that only require you because the system is badly designed

Redesign them.

That list becomes a dependency-removal plan.

Then ask the harder question

What doesn't break without you?

This can be surprisingly revealing.

Your team manages customers.

Schedules work.

Solves normal issues.

Processes invoices.

Runs meetings.

Deals with suppliers.

Perhaps the business functions perfectly well for most of the day.

If so, stop inserting yourself into things merely because you can.

There is no prize for becoming an unnecessary dependency.

Remove yourself gradually

You do not need to disappear for six months to prove a point.

Start deliberately.

Choose one area.

Perhaps purchasing.

Or scheduling.

Or routine customer escalation.

Or quotations below a particular value.

Then:

Define the outcome.

Define authority.

Define boundaries.

Identify the person who owns it.

Give them the required information.

Agree escalation conditions.

Step back.

Measure how often it returns to you.

If 80 decisions a month become 35, then 12, then 4, dependency is visibly reducing.

That is progress.

Do not keep a secret back door

This ruins delegation beautifully.

You tell the operations manager:

“This is yours now.”

Then an employee comes directly to you.

You answer them.

You have just taken it back.

Instead:

“What did Sarah say?”

If they haven't asked Sarah:

“Speak to Sarah. She owns this.”

Simple.

Perhaps slightly uncomfortable.

Essential.

If employees know the owner's door still provides a faster answer, they will use it.

Support the structure you created.

Customer relationships need transferring too

This is particularly difficult.

The customer has dealt with you for twelve years.

They trust you.

You understand them.

They call you.

Lovely.

But if every important customer relationship remains personal to the owner, the business never fully owns the customer base.

Bring managers into meetings.

Let them respond.

Deliberately redirect communication.

Allow somebody else to become trusted.

Remain available for the genuinely strategic conversation.

You are not abandoning the relationship.

You are widening it.

Your identity needs somewhere else to go

This may be the least discussed part.

Suppose you successfully reduce your operational involvement by 50 per cent.

What do you do with yourself?

If the answer is:

Nothing,

you may unconsciously drift straight back in.

The owner needs a useful next role.

Perhaps:

Strategy.

Acquisitions.

New markets.

Key relationships.

Product development.

Writing.

Speaking.

Mentoring leaders.

Another business.

More family time.

Walking the bloody dog.

There needs to be somewhere psychologically meaningful for the released time to go.

Otherwise operations provides an easy answer.

This is why owner independence is not only a delegation project.

It is partly a role-design project.

Recovery from work is difficult for entrepreneurs too

There is some useful recent evidence around this wider issue.

A study published in Small Business Economics, using four surveys of French entrepreneurs, found that the entrepreneurs in the sample reported fewer daily recovery experiences than previous employee samples, with psychological detachment from work particularly low. Better recovery experiences were associated with greater well-being and lower burnout in the analyses. This is one population and observational research cannot establish every causal relationship implied by everyday discussion of burnout, but it reinforces the value of a business owner being able to psychologically leave work occasionally rather than remaining permanently connected to it.

A business that can only function while occupying your attention is not giving you much ownership.

In some ways, it owns you.

Whole-Life Profit matters here

A business can produce excellent financial accounts while being badly designed for the person who owns it.

Profit matters enormously.

So do:

Time.

Health.

Relationships.

Presence.

Attention.

Freedom.

Agency.

That does not mean working 25 hours a week from the beach.

It means recognising that money is not the only return a business produces.

If the company generates £1 million of profit while requiring permanent psychological availability from you, that is part of the cost structure too.

I think of this as Whole-Life Profit.

Not because financial profit becomes less important.

Because success should improve your life rather than consume every other part of it.

The real objective is optionality

I do not believe every owner needs to step away from their company.

Some people love the day-to-day work.

Brilliant.

Stay involved.

The issue is whether involvement is a choice.

Could you step away?

Could somebody else decide?

Could you take three weeks off?

Could you spend Thursday writing instead of solving operations problems?

Could you sell the business?

Could you keep it and appoint somebody else to run it?

Could you change your role?

Agency comes from options.

If the business collapses the moment you stop answering your phone, you have fewer options than the turnover figure suggests.

A practical Fixer Identity reset

Start with one week.

Every time somebody brings you a problem, do not immediately answer it.

Ask:

Who should own this?

Then:

Why has it reached me?

Then:

Is this an exception or a recurring pattern?

Then:

What would need to exist for this not to require me next time?

Track the answers.

At the end of the week, group the interruptions.

You may discover that 40 per cent came from one manager.

Or one customer.

Or unclear pricing authority.

Or purchase approvals.

Or scheduling.

Or your own habit of staying copied into everything.

That is useful.

Now you have something to redesign.

Measure dependency instead of merely complaining about it

Choose a few simple indicators.

Perhaps:

Number of owner approvals.

Number of customer escalations reaching the owner.

Number of operational decisions made by the owner.

Hours spent in routine operations.

Number of direct reports.

Percentage of significant customer relationships with another senior contact.

Number of decisions returned to managers rather than answered.

Again, the exact measures depend on the business.

The point is to make dependency visible.

If you want the business to need you less, you should be able to see whether it actually does.

The final test

Ask yourself this:

If my business became capable of running exceptionally well without me, would I experience that entirely as success?

Or would part of me feel slightly displaced?

There is no morally correct answer.

But there is useful information in the reaction.

Because building a company that depends less on you requires more than better processes.

Sometimes it requires redefining what being a successful owner means.

Your job is not to remain the most useful employee in the business forever.

Your job is to create a business capable of producing good outcomes.

At first, that may require you everywhere.

Later, it should require you differently.

Being needed can feel rewarding.

Being optional is more powerful.