Leading Without Overfunctioning
Why high-achieving leaders become the stabilizer of every system—and how to lead without burning out
If you're a high-achiever in leadership, chances are people describe you with some version of the same sentence.
“You’re the one who keeps everything running smoothly.”
At first, that feels like a compliment.
You’re organized.
You anticipate problems.
You keep things moving when others get stuck.
In meetings, you’re usually the person who can see the next step before the conversation gets there.
When tension appears, you naturally help stabilize it.
And because this works, systems start organizing around you.
Not intentionally.
Just gradually.
Until one day you realize something uncomfortable:
Things work really well when you’re actively holding them together.
But the moment you step back, things slow down.
Decisions stall.
Responsibility gets fuzzy.
People look toward you for direction.
That’s usually the moment a leader begins to recognize a pattern many high-achievers fall into:
Overfunctioning leadership.
How Strong Leaders Accidentally Become the System’s Stabilizer
Systems naturally move toward stability.
In systems theory this is called homeostasis.
When tension appears inside a group, something in the system usually absorbs it.
In families it might be the calm sibling.
In organizations it might be the manager who solves problems fastest.
In teams it’s often the person who can organize chaos quickly.
Over time, that person becomes the functional stabilizer.
The system learns something simple:
If instability appears, this person will handle it.
Psychiatrist Murray Bowen described this dynamic as overfunctioning and underfunctioning cycles.
When one person consistently absorbs responsibility, others unconsciously step back.
Not because they’re incapable.
Because the system has already found its stabilizer.
Why Your Brain Reinforces This Pattern
There’s also a neurological reason this role can feel natural for high-achievers.
Human brains are constantly trying to reduce uncertainty. The brain is always updating predictions about the world.
When something unpredictable happens, the brain experiences prediction error, which creates tension.
Several regions get involved:
the anterior cingulate cortex, which detects conflict
the amygdala, which responds to potential threat
the prefrontal cortex, which works to organize solutions
When you resolve a problem quickly, the brain registers that the prediction error has been reduced.
The situation becomes predictable again.
Dopamine systems reinforce behaviors that successfully improve predictions.
In simple terms:
Problem solved → uncertainty reduced → brain reinforces the strategy that worked.
If you're highly capable at resolving instability, your brain learns something quickly:
Stepping in works.
So the reflex becomes:
detect instability → intervene → restore order
Why Teams Adapt Around Competence
Here’s where leadership systems come in.
Research in organizational psychology shows that groups constantly adjust their behavior based on what works inside the system.
If someone consistently:
anticipates problems
solves them quickly
organizes decisions
regulates tension
others gradually adjust their effort.
They stop scanning for those same problems.
They redirect their attention elsewhere.
Responsibility quietly flows toward the person who absorbs it best.
This is sometimes called a competence trap.
The stronger the stabilizer becomes, the more the system depends on them.
Which leads to a paradox many high-achieving leaders experience:
The more capable you are, the more responsibility gravitates toward you.
When Leadership Turns Into Performance
At first, this dynamic feels efficient.
Projects move faster.
Problems resolve quickly.
The system runs smoothly.
But over time something subtle shifts.
Leadership stops being about guiding the system.
It becomes about personally stabilizing the system.
And that’s where pressure builds.
Many leaders notice a thought underneath the workload that sounds like this:
If I’m not holding this together, things might fall apart.
And if things fall apart, it can start to feel like evidence about you.
About your leadership.
About your competence.
About whether you’re doing the job well enough.
When competence becomes the proof of value, leadership slowly becomes performance.
The Hidden Cost: Regulatory Fatigue
Another reason this pattern becomes exhausting is something researchers sometimes call regulatory fatigue.
Stabilizing systems requires a surprising amount of cognitive work.
Leaders who act as the system’s stabilizer are often doing several things simultaneously:
regulating their own reactions
interpreting complex situations
making rapid decisions
managing the emotional tone of the group
All of this relies heavily on the prefrontal cortex, which handles:
decision-making
impulse control
emotional regulation
perspective taking
The prefrontal cortex uses significant cognitive resources.
When someone repeatedly provides cognitive and emotional regulation for an entire system, the load accumulates.
The work is also largely invisible.
When a leader successfully stabilizes tension:
The conflict never escalates.
The problem resolves quietly.
The system continues functioning.
Which means the effort often goes unnoticed.
Ironically, the more effective you are at stabilizing systems, the less visible your effort becomes.
A Real Example: The Competence Trap in Leadership
One leader I worked with ran a high-performing operations team.
He was excellent at organizing complexity.
During meetings, whenever discussions became messy, he could quickly structure the problem and move the group toward a decision.
At first this helped the team tremendously.
But after a year something interesting happened.
Every difficult decision started routing toward him.
Team members would analyze the issue, but eventually conversations would pause.
Then everyone would look at him.
He eventually said something that captured the pattern perfectly.
“I realized I accidentally trained the team to wait for me.”
He wasn’t controlling.
He was simply the fastest stabilizer in the room.
What Stable Leadership Actually Looks Like
The goal isn’t to become less capable.
It’s to stop positioning yourself as the shock absorber for every instability.
Research on distributed leadership shows that strong leaders gradually shift from stabilizing systems themselves to designing systems that stabilize collectively.
In practice that often includes three shifts.
Clear ownership
Responsibility is explicitly defined so work doesn’t quietly drift toward the most capable person.
Shared regulation
Multiple people in the system learn how to interpret problems and manage tension.
Tolerating temporary instability
Leaders resist the reflex to fix problems immediately.
Allowing some uncertainty creates space for others to develop capability.
This can feel uncomfortable at first.
Not because it’s wrong.
But because your brain has learned that intervening quickly restores order.
One Practice to Try This Week
If you tend to become the stabilizer in groups, try one experiment this week.
When tension appears, pause before stepping in.
Instead of asking:
“How do I fix this?”
Ask:
“Who should be developing the ability to handle this?”
Then do three things.
Clarify ownership.
Stay present without solving the problem yourself.
Allow the system to stretch long enough for someone else to organize the solution.
The goal isn’t withdrawal.
It’s distributed capability.
The Shift That Changes Leadership
Many high-achievers built their reputation on competence.
That’s not a problem. Competence is valuable.
But leadership becomes sustainable when competence stops being the way you prove your value.
You still see the problems early.
You still understand the system.
You still have the capacity to step in.
But you’re no longer the person holding the entire structure together.
You’re the person building systems that can stand without you.
I explore this pattern more deeply in my book UNPACKED, where I break down how high-achievers develop these roles and how they begin separating performance from identity.
Because leadership was never supposed to mean carrying everything.
It was supposed to mean creating systems that don’t collapse when you step back.
