THE DEFAULT LIFE: The Fixer Trap
For years, one of the things I was most proud of professionally was being the person people came to when something had gone wrong.
Difficult client?
I'll speak to them.
Problem on site?
Call me.
Someone hasn't done what they were supposed to?
I'll sort it.
Deadline slipping?
Leave it with me.
Staff member needs help?
I'll deal with it.
Something complicated, awkward or high pressure?
Fine.
I genuinely liked being useful.
And it worked.
People trusted me.
I got opportunities.
More responsibility.
More senior roles.
Eventually, I became Managing Director.
Being the person who could fix things had been extremely good for my career.
Until being the person who fixed things became the reason everything kept finding me.
That's the trap.
It starts as competence.
Then becomes reputation.
Then expectation.
Then dependency.
Eventually you can end up in the bizarre position where being indispensable feels like proof that you're doing an incredible job, while the fact that the system cannot function properly without you is actually evidence that something has gone badly wrong.
I didn't understand that for a long time.
I thought being indispensable meant I was valuable.
Sometimes it does.
But there is another possibility.
Sometimes being indispensable means you have accidentally become a single point of failure.
Fixers are incredibly useful
Let's not pretend otherwise.
Every organisation needs them.
The person who doesn't stand there saying:
“Well technically that's not my responsibility.”
The person who sees a problem and moves towards it.
The one willing to help a colleague.
Calm the customer.
Stay another half hour when something genuinely matters.
Take ownership.
Make a decision.
Find a way through.
Those people keep organisations functioning.
Organisational psychology has spent decades studying behaviours that go beyond formal job descriptions under terms such as organisational citizenship behaviour.
Helping colleagues, voluntarily taking responsibility, supporting the organisation and doing things beyond strict contractual requirements are generally associated with useful organisational outcomes.
Nobody sensible wants a workplace full of people who refuse to lift a finger outside their exact written duties.
But researchers have increasingly pointed out that supposedly positive extra-role behaviour has a darker side when it becomes excessive, expected or pressured.
Mark Bolino and colleagues describe how citizenship behaviour can carry personal and organisational costs, particularly when voluntary contribution begins consuming substantial time and energy or creates expectations that continued extra effort is normal.
That's where the fixer begins getting trapped.
Helpful becomes reliable
At first, someone asks you for help because you're good.
You solve it.
Next time, they remember.
Adam sorted that last time.
Ask Adam.
Still perfectly reasonable.
Then another person learns.
Then another.
You become the person who knows how.
That brings status.
Trust.
Responsibility.
And often genuine satisfaction.
The problem is that every successful rescue contains information.
The system learns:
This person can absorb this problem.
And systems tend to route work towards places where work gets completed.
That's rational.
If Sarah always sorts the difficult customer, give difficult customers to Sarah.
If Dave understands the old software, ask Dave.
If Emma knows exactly which supplier to call, use Emma.
If Adam never lets the deadline fail, involve Adam.
The more reliable the person becomes, the more attractive they become as the solution to uncertainty.
Reliability creates demand for reliability.
Then reliability becomes infrastructure
This is the point nobody notices.
The capable employee stops being merely an employee.
They become part of the operating system.
There may be no process saying:
All unusual problems must go through Adam.
It doesn't need one.
Everybody simply knows.
Something strange?
Ask Adam.
Need approval?
Adam.
Not sure?
Adam.
Customer annoyed?
Adam.
Person missing?
Adam.
That arrangement may work beautifully.
Until Adam is unavailable.
Now the organisation discovers something uncomfortable.
It did not have a system for dealing with unusual problems.
It had Adam.
Those are not the same thing.
There is an actual organisational risk here
The technology world has a wonderfully brutal phrase for this:
bus factor.
How many people would need to suddenly disappear before a project became seriously impaired because essential knowledge or capability disappeared with them?
A 2026 paper examining the formal modelling of bus factor describes the core problem as concentrated knowledge and workload: many projects distribute critical responsibilities unevenly, meaning the unavailability of only a small number of contributors can seriously disrupt progress.
The language is slightly grim.
But the principle is useful far beyond software.
If one person's absence stops:
payroll,
quoting,
customer relationships,
compliance,
technical decisions,
approvals,
production,
IT,
access to systems,
or key operational processes,
the organisation does not merely have an excellent employee.
It has concentration risk.
The compliment and the vulnerability can exist simultaneously.
This becomes especially dangerous in small businesses
Small businesses naturally concentrate knowledge.
There may simply not be enough people to create redundancy everywhere.
The founder knows the customers.
One person knows the accounts.
One surveyor knows the odd sites.
One administrator knows how the ancient spreadsheet actually works.
That's normal.
But a fascinating 2026 study of smaller voluntary sport organisations identified what the researchers called the key people paradox.
The same commitment, knowledge and drive that allowed these organisations to function also concentrated workload, tacit knowledge and emotional responsibility in a small number of people.
Those people then became difficult to replace.
Because they were overloaded, they lacked time to develop successors.
Because they possessed so much tacit knowledge, delegation felt risky.
And because they were emotionally invested in the organisation, stepping back became difficult.
The researchers argue that key-person dependency in those organisations was not simply an individual failure to delegate. It had become structurally embedded in how the organisations functioned.
Different sector.
Small sample.
Not something we should generalise to every workplace.
But fuck me, the pattern is recognisable.
The Fixer Trap contains a feedback loop
It goes something like this.
You solve something.
People trust you.
Because they trust you, they bring you harder things.
Because you handle harder things, you accumulate experience other people don't have.
Because you have more experience, it becomes rational to keep giving difficult things to you.
Because difficult things keep coming to you, other people get fewer opportunities to develop the same judgement.
Because they develop less judgement, delegating to them becomes riskier.
Because delegation feels risky, you keep the work.
Because you keep the work, you become even more experienced.
And they don't.
Round again.
At some point you say:
“There's nobody I can delegate this to.”
Correct.
But there may be a reason nobody exists.
You've been doing all the delegatable learning on their behalf.
Helping can accidentally create dependence
There is some research that gets surprisingly close to this mechanism.
Christopher Barnes and colleagues studied backing-up behaviour in teams, where one team member helps another with their workload.
As you'd expect, help can benefit the person receiving it.
But their experiments also found potential costs.
People providing backup sometimes neglected their own tasks, and under particular conditions, recipients who had received substantial backup contributed less taskwork later.
The authors' conclusion was not that helping is bad.
It was that help has consequences for the whole team's workload and future behaviour, and those consequences depend on when and how backup occurs.
That feels important.
If somebody is drowning, help them.
Obviously.
But if you continuously rescue someone before they experience enough responsibility to build capability, the rescue may become part of the problem.
The immediate outcome improves.
The long-term system may not.
The fixer makes today's problem disappear
That is exactly why fixing is so seductive.
It works.
Immediately.
Someone asks you.
You know the answer.
You could spend twenty minutes explaining the logic, letting them think it through, watching them make a slightly imperfect decision and helping them afterwards.
Or you could say:
“Just give it here.”
Done in three minutes.
Today wins.
Tomorrow loses.
Multiply that across months and years.
You become incredibly efficient.
Everyone else becomes incredibly efficient at finding you.
Teaching is slower than doing
Anyone who has ever delegated knows this.
The first time you give something away, delegation is often less efficient than doing it yourself.
You have to explain.
Give context.
Answer questions.
Check.
Correct.
Sometimes watch someone make a mistake you would never have made.
Painful.
You sit there thinking:
I could have done this in twenty minutes.
Yes.
That's not the comparison.
The comparison is:
Twenty minutes every time for the next five years.
Versus:
Two hours now so eventually somebody else can do it without you.
Fixers repeatedly choose the first option because today's workload makes the second feel unaffordable.
Then wonder why tomorrow looks exactly like today.
“It's quicker if I do it myself” is one of the most expensive sentences in business
Sometimes it is genuinely true.
You're in a crisis.
The deadline matters.
Not training time.
Fine.
Do it.
But if the sentence appears every week, it has become an operating philosophy.
And operating philosophies compound.
Do it yourself once.
You save fifteen minutes.
Do it yourself fifty times.
You've bought yourself a permanent responsibility.
Tacit knowledge makes this harder
Not everything can simply be turned into a procedure.
Some expertise is difficult to articulate.
Judgement.
Pattern recognition.
Relationships.
The weird noise a machine makes before something fails.
Knowing that a particular client says they want one thing but usually means another.
Understanding why an apparently harmless technical detail matters.
Knowing who to call.
Organisations depend heavily on this kind of experiential and tacit knowledge.
A 2024 Annual Review of Psychology article on organisational knowledge transfer emphasises that transferring knowledge between people and units can improve organisational performance, but successful transfer depends on the nature of the knowledge, the mechanisms available and people's motivation to share and absorb it.
A systematic review published in 2024 examining procedures for transferring organisational knowledge similarly found organisations use combinations of communication, digitalisation and collective approaches to retain and transmit tacit and explicit knowledge.
That matters because reducing dependency isn't as simple as:
“Write down everything Dave knows.”
Dave may not know what Dave knows.
Expertise often becomes automatic.
The fixer becomes a knowledge warehouse
Over years, odd pieces accumulate.
Passwords.
Contacts.
Histories.
Exceptions.
Why that process exists.
Who needs convincing.
Which customer hates email.
Where the original certificate is.
What happened last time.
Which workaround actually works.
Individually trivial.
Collectively enormous.
The organisation then starts treating memory as a system.
It isn't.
It's a bloke called Dave.
Knowledge-loss research consistently identifies particular vulnerability around tacit and experiential knowledge because it is harder to formalise and transfer than explicit information. Reviews of employee turnover and organisational knowledge loss show that the departure of experienced people can remove knowledge, relationships and networks that organisations struggle to reconstruct afterwards.
A person can be excellent and still represent an organisational design problem.
Again, both statements can be true.
The Fixer Trap is flattering
That's what makes it dangerous.
People need you.
You know things.
You have authority.
You become central.
Someone says:
“I don't know what we'd do without you.”
That feels good.
It certainly did to me.
There is status in indispensability.
You matter.
But somewhere inside that compliment is another sentence:
We have failed to build sufficient capability around you.
Less flattering.
Managers can mistake dependence for leadership
Imagine two managers.
Manager A is involved in everything.
Team constantly asks questions.
Customers want them.
Every tricky decision gets escalated.
They work long hours.
When they're away, things slow down.
Everyone says:
“They're unbelievable. They know everything.”
Manager B's team solves most ordinary problems without them.
Several people understand key processes.
Decisions are made at appropriate levels.
Customers trust the wider team.
Manager B can disappear for a week and remarkably little changes.
Who looks more important?
Probably Manager A.
Who may have built the healthier system?
Quite possibly Manager B.
We often judge leadership by how necessary the leader appears.
Perhaps we should sometimes judge it by how much capability continues when the leader isn't there.
Empowerment is not abdication
This needs saying.
Good leadership does not mean:
“I'm proving I'm not a fixer, so you're on your own.”
That's just neglect.
People need support.
Context.
Authority.
Training.
Feedback.
Resources.
Research on empowering leadership generally finds positive relationships with employee motivation, attitudes and performance, although effects vary and empowerment works through multiple mechanisms rather than delegation alone.
A meta-analysis covering 55 independent samples found empowering leadership positively related to employee motivation, resources, attitudes and behavioural/performance outcomes.
An earlier meta-analysis of psychological and team empowerment also found empowerment associated with job satisfaction, organisational commitment, task and contextual performance, while being negatively associated with employee strain and turnover intentions.
The aim isn't to abandon people.
It's to build their capacity to act.
The hardest moment is allowing someone else to do it differently
Fixers love standards.
That's part of why they're good.
They know exactly how something should be done.
Then they delegate.
The other person does it differently.
Immediate reaction:
Wrong.
But is it wrong?
Or merely not yours?
This distinction matters.
If the outcome is unsafe, non-compliant, poor quality or unacceptable:
Intervene.
Obviously.
But if the outcome is perfectly adequate and the route was simply different?
Leave it alone.
Otherwise delegation becomes theatre.
“You own this.”
Followed by:
“Provided you make every decision exactly as I would.”
That's not ownership.
That's remote-controlled fixing.
Perfection can preserve dependence
If I can do something to 100 per cent and somebody else can currently do it to 80, what happens?
Fixer instinct:
I'll keep doing it.
Development instinct:
Can 80 safely become 85, then 90, then 95?
Not every task permits this.
Safety-critical work has thresholds.
Professional competence matters.
But lots of business decisions are not brain surgery.
Somebody else can send the email.
Speak to the customer.
Chair the meeting.
Make the call.
It may not sound exactly like you.
Good.
That's how a second capable person gets created.
I created parts of my own trap
This is probably the hardest part to admit.
It would be easy to tell my old story purely as:
The business demanded too much from me.
There is truth in that.
But it isn't the whole truth.
I trained people to use me.
I answered.
I fixed.
I absorbed.
I made myself available.
I took pride in being the person who could sort things others couldn't.
Every successful rescue increased confidence that I would rescue the next thing.
My usefulness became part of the architecture.
The trap wasn't entirely done to me.
I helped build it.
That matters because it changes where agency exists.
If my behaviour helped construct the dependency, my behaviour can help dismantle it.
Compulsory helpfulness is different from voluntary helpfulness
This is where organisational citizenship research becomes particularly relevant.
Helping a colleague because you choose to can be satisfying.
Helping because everyone now assumes you will is different.
Researchers use the term compulsory citizenship behaviour for extra-role actions that appear voluntary on paper but are experienced as pressured or expected.
A 2023 systematic review and meta-analysis synthesising 53 publications describes compulsory citizenship behaviour as the darker side of extra-role contribution and links it with a network of negative workplace outcomes and pressures.
A 2024 study of 265 frontline employees and supervisors found compulsory citizenship pressure associated with role overload, which in turn undermined some voluntary service behaviours and creativity, particularly among the younger employee group in that sample.
The research isn't literally about “fixers”.
But the transition is familiar.
At first:
Could you help?
Eventually:
Of course you'll help.
One feels like generosity.
The other feels like obligation.
Citizenship fatigue has a name for a reason
Bolino and colleagues studied what they called citizenship fatigue: feeling worn out, tired or on edge as a result of repeatedly engaging in discretionary extra-role behaviour.
Their multi-wave study of 273 employees found that the relationship between citizenship behaviour and fatigue depended heavily on context.
Fatigue was greater where organisational support was lower and citizenship pressure higher, while strong team relationships could change the experience significantly.
Citizenship fatigue was also associated with less future citizenship behaviour.
This is important.
Helping itself isn't the problem.
A healthy team contains lots of helping.
The danger comes when extra becomes normal, pressure rises and resources are continually consumed.
Eventually the person who always went above and beyond becomes exhausted by the expectation that beyond is now their minimum.
Recent research finds the same tension
A 2026 study involving 499 nurses found compulsory citizenship behaviour positively associated with citizenship fatigue and negatively associated with work-life balance, with fatigue partially mediating the relationship in that sample.
The researchers interpret the pattern through resource-loss processes: repeatedly being expected to contribute beyond normal roles can consume time and psychological resources.
That study is cross-sectional and nursing is an unusually demanding context.
It doesn't prove every helpful employee eventually burns out.
But it reinforces an increasingly well-established distinction.
Voluntary contribution and permanent expectation are not psychologically identical.
A fixer can accidentally stop other people becoming fixers
This is the cruel irony.
You want to help.
So you step in.
The other person never deals with the whole problem.
They learn:
When this happens, ask you.
Next time, they ask earlier.
You respond more quickly because you've seen it before.
Now they're even less involved.
Soon you say:
“Why does nobody ever use their initiative?”
Well...
Because the fastest route through uncertainty has become you.
Initiative competes badly with instant access to an expert.
Sometimes the best help is another question
Instead of:
“Here's what you need to do.”
Try:
“What do you think you should do?”
Annoying at first.
Especially when you know the answer.
But something different happens.
They have to think.
Then perhaps:
“What are the risks?”
“What information do you need?”
“What would you do if I wasn't here?”
Now you're transferring judgement rather than merely transferring an answer.
That is slower.
That's the point.
Capability is being built.
Don't answer questions people can answer themselves
Not as a rigid rule.
As a diagnostic.
Someone asks:
“What should I do?”
Before answering, ask yourself:
Do they genuinely lack information?
Authority?
Competence?
Or merely confidence?
Those require different interventions.
Information:
Give it.
Authority:
Delegate it.
Competence:
Teach it.
Confidence:
Stop rescuing them before they discover they can cope.
Fixers often respond to all four with the same solution:
I'll do it.
That's efficient today.
Expensive tomorrow.
Cross-training is redundancy for humans
Organisations already understand redundancy in technology.
Backups.
Failover systems.
Multiple suppliers.
Emergency power.
We are oddly comfortable running critical human processes with absolutely none.
Only Claire understands payroll.
Only James knows the customer.
Only Sarah can run that machine.
Only the owner can approve the quote.
Then Claire gets ill.
James leaves.
Sarah retires.
Owner goes on holiday.
Panic.
Team research has shown cross-training can improve people's understanding of one another's roles and, under some high-workload conditions, improve coordination and performance.
Classic experimental studies found cross-trained teams developed stronger interpositional knowledge than teams without that training, although effects depend on task type and conditions.
Again, a simulated team task is not the same as running an SME.
But the principle is useful.
Resilience increases when more than one person understands how work fits together.
The best time to transfer knowledge is before you need to
Obvious.
Rarely done.
Because when everything is working, transfer feels non-urgent.
Dave is here.
Sarah isn't leaving.
The owner isn't planning to disappear.
So documentation can wait.
Training can wait.
Succession can wait.
Then one day it can't.
A 2024 systematic review of organisational knowledge-transfer procedures found organisations commonly invest in collective transfer methods, communication processes and digital systems precisely because losing experienced people can otherwise remove difficult-to-replace tacit and explicit knowledge.
Knowledge transfer is prevention.
And prevention is always vulnerable to the same problem:
Nobody feels the benefit today.
The fixer rarely has time to make themselves unnecessary
This is perhaps the core paradox.
You need to document the process.
No time.
You need to train somebody.
No time.
You need to delegate.
No time.
Why?
Because you're too busy being the person everything depends on.
Perfect.
The problem prevents its own solution.
That is why dependency removal sometimes requires deliberately accepting lower short-term efficiency.
Block the time.
Train the person.
Allow the slower attempt.
Document the weird process.
Let someone shadow.
Give decision rights.
Review afterwards.
If you wait for spare capacity, it may never arrive.
The fixer consumes the capacity that would have removed the need for the fixer.
Leaders have to resist rewarding the wrong behaviour
Someone rescues a deadline.
Thank them.
Then ask why rescue was necessary.
Don't simply give them the next disaster because they're good at disasters.
Someone always stays late.
Appreciate it.
Then ask why staying late keeps being required.
Someone knows everything.
Value them.
Then ask how more people can learn.
Someone is the only client contact.
Recognise the relationship.
Then widen it.
Praise heroics where heroics were genuinely needed.
But don't build the next operating model around the assumption that heroism will always be available.
Fixers also need to stop collecting problems
This is personal.
Someone mentions something.
Fixer hears responsibility.
“I'll sort it.”
Why?
Did they ask?
Are you the right person?
Could they solve it?
Does it even need solving?
I still have to catch myself with this.
You can develop such a strong identity around fixing that problems become invitations.
You see inefficiency and feel compelled to own it.
Agency does not mean accepting every solvable problem as your personal assignment.
Sometimes the most agentic thing is identifying the right owner and leaving the problem there.
Not every dependency is bad
This needs nuance.
Specialists exist for a reason.
I would rather a highly competent specialist make some decisions than distribute them among ten enthusiastic amateurs.
Small companies cannot duplicate every role.
A surgeon may be uniquely skilled.
A technical expert may legitimately hold rare knowledge.
A founder may possess relationships nobody can quickly recreate.
The goal isn't zero dependence.
That's unrealistic and potentially inefficient.
The goal is knowing where dependence exists and deciding whether the risk is acceptable.
There is a difference between:
This person is unusually valuable.
and:
This process collapses if this person has flu.
The first is good.
The second deserves attention.
The key-person paradox is particularly useful here
The 2026 study of small voluntary organisations found precisely this contradiction.
The people whose commitment, knowledge and relationships made the organisation strong were simultaneously the people around whom vulnerability accumulated.
The researchers describe concentrated knowledge, disproportionate burden, difficulty relinquishing control and weak succession as interconnected rather than separate problems.
That's the fixer trap.
Strength and weakness wrapped around the same person.
You can test your dependency quite easily
Take a hypothetical week away.
No phone.
No laptop.
No quiet checking.
What stops?
Not:
What becomes slightly less convenient?
What genuinely stops?
Which decisions wait?
Which clients cannot be served?
Which processes nobody understands?
Which passwords disappear?
Which approval only you can provide?
Which relationship exists entirely through you?
Which weird workaround has never been documented?
There's your list.
Not necessarily of things to immediately delegate.
Of dependencies.
Now you can decide.
The same test works for managers
What does the team need you for every day?
Strategy?
Leadership?
Complex judgement?
Good.
Routine approval?
Minor customer questions?
Information already stored somewhere?
Decisions people are capable of making?
Less good.
A manager becoming less involved in routine decisions does not mean becoming less useful.
It should create capacity for work only the manager can do.
That's the point.
Delegation isn't about doing nothing.
It's about moving your effort up the value chain.
Sometimes people don't want the fixer to change
This can surprise you.
You start asking people to take ownership.
They preferred the old arrangement.
Of course they did.
Uncertainty used to belong to you.
Decision risk belonged to you.
Difficult conversations belonged to you.
You carried the anxiety.
Delegation doesn't merely transfer tasks.
It transfers responsibility.
Not everyone immediately enjoys that.
So the fixer can encounter resistance from the very people they thought would be delighted to receive more autonomy.
Capability development is cultural.
Not simply procedural.
You may also miss being needed
This is the part leadership books rarely capture properly.
You finally build a team that doesn't need you for every decision.
And it can feel...
Odd.
Nobody calls.
Nobody asks.
The problem gets solved without you.
You find out afterwards.
Part of you thinks:
Fantastic.
Another part thinks:
Oh.
If your identity has been built around usefulness, successful delegation can feel suspiciously like becoming less important.
That is the emotional side of dependency removal.
You have to separate:
I matter
from:
Everything must pass through me.
Those are not the same.
Being needed is not the highest form of usefulness
Imagine a parent who ties their child's shoes forever because they're quicker at it.
Extremely useful.
Until the child is twenty-seven.
The purpose of some forms of help is to eventually make the help unnecessary.
Leadership should work similarly.
Teach.
Support.
Catch when needed.
Then gradually step back.
Your value isn't diminished because another person can now do something you taught them.
Your value multiplied.
Strong systems distribute capability
This is one reason knowledge sharing matters so much to organisational resilience.
A 2026 study involving 1,131 participants across 175 SMEs found that employee social connections and knowledge sharing were associated with stronger organisational resilience, particularly where high-involvement working practices supported the exchange and use of that knowledge.
The exact mechanisms will differ enormously between businesses.
But the broader direction is sensible.
Knowledge trapped in individuals can be powerful.
Knowledge connected across people is more resilient.
The fixer should become an architect
Not overnight.
But eventually.
At first:
Solve the problem.
Then:
Understand why the problem reached you.
Then:
Remove the cause if possible.
Then:
Make sure another person could handle the next version.
That's a different role.
The fixer asks:
How do I make this work?
The architect eventually asks:
How do I make this work without requiring me every time?
That's not withdrawal.
That's maturity.
There are four stages I wish I'd understood earlier
First: Rescue.
Sometimes the thing is on fire.
Deal with it.
Second: Diagnose.
Why did this need rescuing?
Unexpected event?
Bad luck?
Or recurring system weakness?
Third: Transfer.
Who else needs the knowledge, authority or capability?
Fourth: Test.
Next time it happens, don't automatically step in.
See whether the new system works.
Most fixers complete stage one brilliantly.
Then return to stage one.
Forever.
You have to let the new system wobble
This is hard.
You delegate.
Something takes longer.
The customer asks a question.
Your hand twitches.
I'll take over.
Don't.
Unless the consequence genuinely matters.
Because if every wobble triggers rescue, everybody learns:
The new system isn't real.
Adam still owns it.
A developing person needs enough room to experience manageable consequences.
Otherwise responsibility never fully transfers.
This does not mean tolerating avoidable failure
Another important distinction.
Don't deliberately let a customer suffer so someone can “learn”.
Don't allow unsafe work.
Don't ignore serious financial risk.
You remain responsible for designing appropriate supervision.
The art is creating safe failure, not reckless failure.
Lower-risk decisions.
Review points.
Clear escalation criteria.
Support without immediate takeover.
That's how competence grows without gambling with things that genuinely matter.
The fixer trap can exist at home too
One person knows:
what food is needed,
where the uniforms are,
which child needs what on Tuesday,
when the forms are due,
what birthdays are coming,
which appointment needs booking,
where everything lives.
They complain nobody helps.
Then somebody tries.
“Not like that.”
So they take it back.
Family systems can develop key-person dependency just as businesses do.
Not because one person planned it.
Because capability accumulated.
Then expectation accumulated around it.
The mechanism is remarkably similar.
Capability attracts dependency unless you deliberately redistribute it
That may be the central principle.
If you are good at something and helpful, people will naturally bring more of it to you.
That's rational.
You cannot stop that entirely.
Nor should you want to.
The skill is noticing when demand for your capability has stopped being a compliment and started becoming structural reliance.
There is a point where:
“They trust me”
becomes:
“They cannot function without me.”
Different sentence.
The Fixer Trap is a default life problem
Because nobody chooses it all at once.
You help today.
Stay late tomorrow.
Take another responsibility next month.
Become the person clients call.
Keep a process because teaching somebody feels harder.
Answer while you're away.
Rescue another deadline.
Five years later, you're exhausted and everyone insists you're too important to step back.
Congratulations.
You succeeded yourself into captivity.
There was no moment where the trap snapped shut.
The door closed one helpful decision at a time.
I don't want to stop being a fixer
That's important.
I still like solving problems.
I still move towards difficult things.
I still take enormous satisfaction from being useful.
I don't want to extinguish that.
The lesson isn't:
Stop fixing.
It is:
Stop confusing repeated rescue with a healthy system.
Fix the thing that genuinely needs fixing.
Then ask whether your intervention made the next problem less likely to need you.
If it didn't, perhaps you only borrowed time.
The real test of capability might be what happens when you leave
Not permanently.
Go away for a week.
Can people decide?
Can they find information?
Can customers be helped?
Can work move?
Can someone else solve the thing?
If yes, you haven't become less valuable.
You have built value that exists beyond your own availability.
That is much more powerful.
Indispensable is flattering
Resilient is better.
An indispensable person can keep a fragile system alive.
A resilient system can benefit enormously from that person's expertise without depending on their constant presence.
That's the difference I wish I had understood earlier.
My mistake was never that I helped too much.
Helping created many of the opportunities that shaped my career.
The mistake was letting repeated help quietly become architecture.
Perhaps the question isn't “How much do they need me?”
Maybe it's:
What can they do because I was here?
Can they think better?
Decide better?
Solve more?
Understand the client?
Run the process?
Train somebody else?
Carry knowledge forward?
If your contribution creates more capable people, your value remains even when you're absent.
If your contribution only makes everybody better at finding you, the trap is still tightening.
That is the uncomfortable question for anyone who takes pride in being the one who sorts things.
What are you still proud of being needed for that the system should have learned to do without you?
Sources And Further Reading
Mark C. Bolino, Anthony C. Klotz, William H. Turnley and Jaron Harvey, “Exploring The Dark Side Of Organizational Citizenship Behavior”, Journal Of Organizational Behavior (2013).
A major conceptual review challenging the assumption that voluntary extra-role behaviours are invariably positive. The authors examine conditions under which citizenship behaviour can create costs for employees and organisations, including overload, pressure and work-family consequences.
Mark C. Bolino, Hsin-Hua Hsiung, Jaron Harvey and Jeffery A. LePine, “‘Well, I'm Tired Of Tryin'!’ Organizational Citizenship Behavior And Citizenship Fatigue”, Journal Of Applied Psychology (2015).
Using multi-wave data from 273 employees and peers, the researchers found that citizenship behaviour could contribute to citizenship fatigue depending on organisational support, team relationships and pressure to engage in extra-role behaviour. Citizenship fatigue was also negatively related to later citizenship behaviour.
Systematic Review And Meta-Analysis Of Compulsory Citizenship Behaviour (2023).
A synthesis of 53 publications examining compulsory citizenship behaviour, defined broadly as extra-role activity performed under direct or indirect workplace pressure. The review maps a range of antecedents and outcomes and reinforces the distinction between genuinely voluntary helping and extra-role contribution that has become socially or organisationally expected.
Aamir Suhail, Inam Ul Haq, Muhammad Umer Azeem and Eran Vigoda-Gadot, “Compulsory Citizenship Behavior, Role Overload, Creativity And Service-Oriented Voluntary Behavior” (2024).
A three-wave study involving 265 frontline employees and supervisors found compulsory citizenship pressure associated with role overload, with downstream relationships to creativity and voluntary service behaviours that differed between generational groups in the sample.
Şehrinaz Polat, Hanife Tiryaki Şen and Dilek Özdemir Ürkmez, “Citizenship Fatigue As A Mediator Between Compulsory Citizenship Behavior And Work-Life Balance Among Nurses”, Journal Of Nursing Scholarship (2026).
A cross-sectional study of 499 nurses found compulsory citizenship behaviour positively associated with citizenship fatigue and negatively associated with work-life balance. Citizenship fatigue partially mediated that relationship in the studied sample.
Christopher M. Barnes et al., “Harmful Help: The Costs Of Backing-Up Behavior In Teams”, Journal Of Applied Psychology (2008).
Experimental work showing that helping teammates can create both benefits and costs. Backup providers could neglect their own taskwork, while under particular conditions recipients who received substantial backup contributed less in a later task. The study demonstrates why helping behaviour should be evaluated at system level rather than assumed to be cost-free.
“The Key People Paradox: Human Capital Vulnerability In Smaller Voluntary Sport Organisations” (2026).
A qualitative study showing how concentrated commitment, tacit knowledge and emotional investment can simultaneously enable organisations to function and create vulnerabilities around workload, delegation and succession. The authors frame key-person dependency as a structural condition rather than merely an individual's refusal to delegate.
Linda Argote, “Knowledge Transfer Within Organizations: Mechanisms, Motivation, And Consideration”, Annual Review Of Psychology (2024).
A major review of organisational knowledge transfer examining how knowledge moves between people and units, why transfer can improve performance and how the nature of knowledge, relationships and motivation affects whether transfer succeeds.
“Procedures For Transferring Organizational Knowledge During Generational Change: A Systematic Review”, Heliyon (2024).
A systematic review of 28 articles on organisational knowledge-transfer procedures. The review highlights digitalisation, intra-organisational communication and collective approaches as recurring elements in efforts to retain and transfer both tacit and explicit knowledge.
Review Of Turnover-Induced Organisational Knowledge Loss.
A systematic synthesis of research on knowledge lost when organisational members leave, highlighting particular vulnerability around tacit, experiential knowledge, professional networks and expertise that is difficult to formalise and transfer.
Minseo Kim, Terry A. Beehr and Matthew S. Prewett, “Employee Responses To Empowering Leadership: A Meta-Analysis” (2018).
Across 55 independent samples, empowering leadership was positively related to employee motivation, resources, attitudes and behavioural/performance outcomes, although relationship strengths varied across outcome categories.
Catherine E. Volpe, Janis A. Cannon-Bowers, Eduardo Salas and Paul E. Spector, “The Impact Of Cross-Training On Team Functioning”, Human Factors (1996), with later replication and extension.
Experimental research found cross-training could improve team processes, communication and understanding of teammates' roles. Later work suggested benefits may be particularly relevant under high workload and in highly interdependent tasks.
T. E. Edafioghor, Q. Zhou and C.-H. Wu, “Leveraging Employees' Social Capital For Organizational Resilience In Small And Medium-Sized Enterprises” (2026).
Research involving 1,131 participants across 175 SMEs found evidence linking employee bridging social capital and knowledge sharing with organisational resilience, particularly in businesses using high-involvement working practices.
Research Gaps
“The Fixer Trap” is a conceptual synthesis rather than an established academic construct.
Research exists on organisational citizenship behaviour, citizenship pressure, backing-up behaviour, key-person dependency, empowerment, knowledge transfer and workload. This essay combines those literatures into a practical mechanism called the Fixer Trap. The complete feedback loop has not been validated under that name.
Helping behaviour is generally valuable.
The essay focuses deliberately on situations where helping becomes repetitive, pressured or dependency-producing. It should not be interpreted as evidence that employees should stop supporting one another. Strong teams require cooperation and backup.
The “harmful help” findings depend on context.
The 2008 backing-up behaviour study examined controlled team tasks. The finding that recipients sometimes reduced later taskwork occurred under particular experimental conditions and does not establish that routinely helping a colleague makes them lazy or dependent.
Compulsory citizenship research is not the same as voluntary fixer identity.
Employees pressured by an organisation to perform unpaid or extra-role work face a different mechanism from highly autonomous people who voluntarily take excessive responsibility. The two can overlap when voluntary contribution gradually becomes expected, but they should not be treated as identical.
Citizenship fatigue varies with organisational support.
Research indicates extra-role behaviour is not universally exhausting. Strong team relationships, genuine voluntariness, recognition and organisational support can materially change how helping is experienced.
The 2026 nursing study is cross-sectional.
Associations between compulsory citizenship behaviour, fatigue and work-life balance cannot establish the full direction of causality. Nursing also represents a demanding professional context that may not generalise directly to ordinary commercial workplaces.
The key-people-paradox study concerns smaller voluntary sport organisations.
Its account of concentrated knowledge, burden and succession is highly relevant conceptually but comes from a specific organisational setting. Commercial SMEs, large corporations and public institutions may display different dependency mechanisms.
Some key-person dependency is economically rational.
Duplicating every specialist skill, relationship or decision role would be prohibitively expensive in many small organisations. Resilience involves choosing where redundancy is worth its cost rather than eliminating all concentration.
Tacit knowledge cannot always be fully transferred.
Documentation helps, but years of experience, judgement, relationships and pattern recognition cannot always be captured in procedures. Organisations may need overlapping experience, shadowing, mentoring and time rather than expecting complete codification.
Cross-training evidence is context-sensitive.
Classic studies often use simulations and controlled teams. Cross-training can improve coordination and role understanding, but it also consumes time and may be inefficient for specialised roles where full role duplication provides little value.
Empowering leadership is broader than delegation.
Meta-analytic evidence for empowering leadership includes behaviours such as encouraging participation, expressing confidence, supporting autonomy and sharing information. It does not prove that simply delegating more tasks will improve performance.
Poor delegation is not always caused by a controlling fixer.
Lack of skills, staffing shortages, regulatory restrictions, scarce expertise, workload and previous failed delegation may make concentration rational. Leadership behaviour is only one possible cause.
Being highly needed is not necessarily evidence of weak leadership.
During a turnaround, crisis, specialist project or early-stage company, intense reliance on a key individual may be temporary and appropriate. The concern arises when emergency concentration quietly becomes the permanent operating model.
The essay does not establish an ideal level of organisational redundancy.
Additional people, knowledge transfer and cross-training all have costs. The appropriate level depends on consequences of failure, likelihood of absence, task complexity, organisational size and available resources.
Fixer identity and psychological attachment deserve more direct research.
The essay argues that people may derive status, meaning and identity from being needed, making dependency emotionally difficult to relinquish. This is consistent with broader identity and leadership research but is not directly established by the studies cited here.