Rogue Entity Encounters
Common Habitat: Workplaces, families, teams, households, friendships, volunteer groups, collaborative projects, leadership roles
Appearance: Reliable people receiving more work because they are reliable, capable people continually rescuing weaker systems, excellence rewarded with additional burden
Classification: Role / Labor / Systemic Entity
Danger Level: Moderate to Severe
Primary Effect: Converts demonstrated capability into an expanding obligation to compensate for everyone and everything that functions less reliably
Preferred Target: Whoever gets things done
There are four people in the room.
Something needs doing.
One person does it well.
Next time:
“Can you handle this?”
Sure.
They do it well again.
Next time nobody asks.
The work simply appears near them.
Eventually they are doing:
Their work.
The forgotten work.
The difficult work.
The emergency work.
And the work that supposedly belongs to someone else.
Then one afternoon they finally make a mistake.
Someone says:
“What’s going on with you?”
Interesting.
Competence has apparently become a subscription service.
Meet The Competence Tax.
Field Identification
The Competence Tax appears when capability creates additional burden without corresponding authority, resources, compensation, or relief.
You solve problems.
Therefore:
More problems arrive.
You remain calm.
Therefore:
You handle crises.
You remember things.
Therefore:
You become responsible for remembering.
You work quickly.
Therefore:
You receive more work.
You rarely fail.
Therefore:
Your failures become unusually visible.
Success has increased the price of success.
Competence Is Good Magic
Learn things.
Become capable.
Practice.
Develop judgment.
Know how to repair the machine.
Run the meeting.
Calm the room.
Write the report.
Organize the trip.
Competence creates freedom.
The entity appears when a system discovers your competence and begins using it as a substitute for repairing itself.
Encounter
A team had six employees.
One was exceptionally organized.
When deadlines approached, she noticed what had been forgotten.
She reminded people.
Checked details.
Corrected mistakes.
The projects succeeded.
Her manager praised her.
“I don’t know what we’d do without you.”
At first this felt good.
Years later, she realized the sentence was not entirely a compliment.
The team genuinely did not know what it would do without her.
Because every time the system failed, she prevented anyone from experiencing the failure.
She had become the invisible bridge across every missing piece of road.
The Reliable One
Reliability attracts dependence.
If you say you will arrive:
You arrive.
If you take the task:
It gets done.
If someone needs help:
You respond.
Eventually people stop planning for the possibility that you might be unavailable.
Why would they?
Historically:
You always catch the ball.
The system begins throwing without checking whether you are looking.
The Fast Worker
You finish your work early.
Excellent.
Reward:
More work.
You finish that early.
Reward:
More work.
Eventually the slow worker completes six tasks.
You complete twelve.
Both worked eight hours.
Your efficiency has been converted entirely into increased output for the system.
Perhaps that arrangement is fair.
Perhaps not.
But notice it.
Efficiency should sometimes purchase:
Capacity.
Rest.
Higher compensation.
Greater responsibility with greater authority.
Not merely another shovel.
The Good Listener
Competence is not only technical.
Perhaps people tell you things because you listen well.
You understand.
You don’t judge.
You know what to say.
Soon:
Everyone comes to you.
Bad day.
Relationship.
Family problem.
Work problem.
Existential crisis.
You became emotionally competent.
Now you have acquired an unofficial waiting room.
The Calm Person
Something goes wrong.
Everyone panics.
You don’t.
So:
“Go get them.”
“You talk to him.”
“Can you handle this?”
Again.
Again.
Again.
The calmest nervous system becomes communal emergency equipment.
Useful.
But emergency equipment also requires maintenance.
The Strong One
“You’ll be fine.”
Maybe.
Strong people often receive less support precisely because they appear capable of surviving without it.
Someone else struggles visibly.
Help arrives.
The strong person struggles quietly.
More responsibility arrives.
Strength can become a camouflage that hides need from the group.
The Parentified Expert
Sometimes this begins young.
A child is mature.
Responsible.
Observant.
Capable.
So adults give them more.
Watch the sibling.
Help with the house.
Manage the younger children.
Don’t cause problems.
“You’re the responsible one.”
Praise and burden become difficult to separate.
The child learns:
Competence means carrying more.
The Household Expert
One person cooks better.
So they cook.
One person notices dirt.
So they clean.
One understands money.
So they manage finances.
Specialization can be excellent.
But if every task goes to whoever performs it best, something strange happens.
The less competent person is protected from practice.
The more competent person becomes increasingly indispensable.
Skill difference widens.
The tax increases.
Weaponized Incompetence
Sometimes someone learns:
If I perform badly enough, someone else will take over.
Laundry ruined.
Reservation forgotten.
Task half-finished.
“You’re just better at this.”
Maybe.
But competence requires practice.
If one person’s poor performance permanently transfers responsibility to the more competent person, failure has become profitable.
Whether deliberate or not, the system rewards incompetence.
The Rescue Loop
Someone fails.
You fix it.
Immediate problem solved.
But:
They do not experience the full consequence.
They do not build the missing skill.
The system does not change.
Next time:
Same failure.
You rescue.
Competence has become a maintenance mechanism for dysfunction.
The Competence Tax and The Manufactured Obligation
Natural companions.
Competence Tax says:
You’re good at this.
Manufactured Obligation says:
Therefore it is now your job.
A skill becomes a role.
A role becomes an expectation.
An expectation becomes a duty.
The Competence Tax and The Ghost Job
You notice what nobody else notices.
You perform the invisible task.
Soon the system depends on it.
Nobody officially assigned it.
Nobody measures it.
Nobody compensates it.
But stop doing it—
and everyone discovers the Ghost Job was holding up the ceiling.
The Competence Tax and The Borrowed Emergency
Something goes wrong.
Who gets called?
The capable person.
Their evening disappears because someone else created an emergency.
Again.
Eventually competence creates permanent on-call status.
The Competence Tax and The Default Yes
The capable person is asked because:
They usually say yes.
Then because they usually say yes:
They are asked more.
A beautiful little machine.
The Default Yes feeds the Competence Tax.
The Competence Tax creates more opportunities for the Default Yes.
The Competence Tax and The Gratitude Leash
“We really appreciate everything you do.”
Good.
Then:
Another task.
Another emergency.
Another weekend.
Gratitude is pleasant.
But praise is not always compensation.
Sometimes:
“You’re amazing”
is being used where:
“We need to redistribute this work”
would be more useful.
The Competence Tax and The Consistency Trap
You’ve always been dependable.
Now you are exhausted.
But stopping feels inconsistent.
“That’s not like you.”
Correct.
Perhaps the old pattern became unsustainable.
Reliability should not require permanent overextension.
The Bus Factor
A useful systems question:
If this person disappeared tomorrow, what would stop functioning?
Not because they will disappear.
Because systems with one critical person are fragile.
If the answer is:
Everything.
Then the solution is not:
Make sure that person never rests.
The solution is:
Build redundancy.
Teach.
Document.
Distribute.
The Hero Problem
Organizations sometimes love heroes.
Someone saves the launch.
Fixes the disaster.
Works all night.
Catches the mistake.
Excellent story.
But if heroism becomes routine, investigate the system.
A healthy system should not require someone to repeatedly perform miracles for ordinary operations.
Repeated heroics can be evidence of structural failure.
Praise Can Hide Extraction
“You’re the only person I trust with this.”
Feels good.
Maybe true.
Also means:
More work.
“Nobody does it like you.”
Wonderful.
Also:
More work.
“You’re such a natural leader.”
Excellent.
Also perhaps:
Please manage everyone without title, authority, or compensation.
Receive praise.
But inspect the package attached to it.
The Punishment of Excellence
Imagine two workers.
One consistently performs at 70%.
One consistently performs at 100%.
A crisis arrives.
Who receives the extra work?
Often:
The 100% worker.
Because they can handle it.
If repeated indefinitely, the system teaches something perverse:
High performance produces higher burden.
Eventually capable people learn to hide capacity.
That is bad system design.
Countermeasure: Stop Automatically Rescuing
Before fixing:
Does this actually belong to me?
Then:
What happens if I don’t intervene?
Perhaps disaster.
Then intervene.
Perhaps inconvenience.
Let it happen.
Systems need feedback.
Countermeasure: Make Work Visible
List what you actually do.
Not merely the official role.
Reminders.
Training.
Corrections.
Coordination.
Emotional labor.
Emergency handling.
Documentation.
Preparation.
The invisible workload becomes negotiable once it is visible.
Countermeasure: Trade Work, Don’t Stack It
Someone adds a task.
Ask:
“Which existing priority should move?”
Powerful.
The new task no longer floats magically above the calendar.
It must occupy real space.
If everything is priority one, priority has lost meaning.
Countermeasure: Teach Instead of Take Over
Someone struggles.
Instead of:
“Give it here.”
Try:
“I’ll show you.”
Slower today.
Much faster over the next year.
Competence that spreads becomes infrastructure.
Competence that hoards every task becomes a bottleneck.
Countermeasure: Document the Spell
You know how to do something important.
Write it.
Checklist.
Instructions.
Template.
Process.
Now knowledge can travel without requiring your body to accompany it.
A documented spell can be cast by more than one Mage.
Countermeasure: Allow Adequate Work
Dangerous for perfectionists.
Someone else does the task differently.
Not as elegantly.
But adequately.
Leave it.
If you correct every 85% solution into your preferred 100%, people may eventually stop trying.
Not every task requires your standard.
Countermeasure: Ask for Matching Authority
If you are responsible for outcomes:
Do you have authority over the inputs?
If not:
Problem.
Responsibility without authority is fertile ground for Competence Tax.
If the system expects you to own the result, you may need:
Decision rights.
Resources.
Time.
Staff.
Budget.
Information.
Real ownership requires tools.
Countermeasure: Ask for Matching Compensation
If your role expanded:
Perhaps the job changed.
Title.
Pay.
Hours.
Scope.
Recognition.
Not every additional responsibility requires negotiation.
People help each other.
But sustained structural expansion deserves structural acknowledgment.
Countermeasure: Become Temporarily Unavailable
Sometimes a system cannot reveal its dependencies while the competent person remains continuously present.
Take the day off.
Do not answer immediately.
Let someone else run the meeting.
Let another person solve the problem.
This is not sabotage.
It is a systems test.
Healthy structures should survive the absence of individual members.
When You Are the Competent One
Do not weaponize competence either.
“Nobody can do this except me.”
Perhaps because nobody has been allowed to.
Control can hide inside helpfulness.
If being indispensable has become part of your identity, distributing skill may feel threatening.
Notice that.
A Mage should create more capable people.
Not permanent dependence.
When Someone Else Is Competent
Notice how often you call them.
Before:
“Can you handle this?”
ask:
Could I learn?
Could someone else do it?
Is this actually their responsibility?
Am I asking because they are appropriate—
or because they are reliable?
Protect the capable people in your systems.
They are often carrying things nobody remembers handing them.
The Mage’s Competence
A Mage learns.
Practices.
Becomes reliable.
Carries weight.
But mastery is not measured by how many failing systems can be strapped to one person’s back.
Higher competence should create greater choice.
Not less.
Sometimes mastery means:
I can do this.
Sometimes:
I can teach this.
Sometimes:
I know who should do this.
Sometimes:
This does not need doing.
And sometimes the most advanced spell is:
No. I am not taking that one.
Field Note
There is a strange reward awaiting the person who becomes good at carrying weight.
More weight.
At first this may feel like recognition.
People trust you.
Good.
You are useful.
Good.
You can handle difficult things.
Good.
But inspect the load occasionally.
Some of what you carry belongs to you.
Some you chose because you care.
Some is genuinely yours because of your role.
And some arrived simply because everyone noticed you rarely drop anything.
Set those pieces down long enough to read the names written underneath.
A healthy system does not prove your strength by requiring you to compensate forever for everyone else’s weakness.
Your competence is a resource.
A spell.
A craft.
A form of power.
Use it generously when you choose.
Teach it where you can.
Build systems that preserve it.
But do not confuse being capable of carrying something with being required to carry it.
Otherwise mastery becomes punishment.
And that is the favorite trick of The Competence Tax.
Leave a Reply