The Best Leaders Don’t Create Dependence
- Adam R.
- Aug 27
- 5 min read
Your team performs exceptionally well when you're there.
Decisions get made.
Problems get solved.
Projects move forward.
People know what they need to do.
Then you leave.
And everything slows down.
Questions pile up. Decisions wait for your return. People hesitate because they're not sure what you would want them to do.
From one perspective, that can feel flattering.
Look how much they need me.
But I think a leader needs to be willing to ask a much more uncomfortable question:
Why do they need me this much?
Because if your presence is required for the system to function, you may not have built a high-performing team.
You may have built a dependency.
I Had to Learn This Myself
There was a point in my leadership career when I realized I was carrying far too much for my team.
I was carrying the ideas.
The direction.
The problem-solving.
The vision.
I thought I was supporting them.
In reality, I was enabling them.
If the team needed direction, I gave it.
If there was a problem, I solved it.
If something needed to move forward, I got the ball rolling.
And when you operate like that long enough, something starts to happen.
People learn to wait for you.
That's when I began to understand that leadership isn't about proving how valuable I am by becoming necessary for every decision.
My value as a leader should be reflected in how capable the people around me become.
Being Needed Can Feed the Leader More Than the Team
I understand why leaders fall into this trap.
Being needed feels good.
If everyone comes to me for answers, I must be valuable.
If nobody can make the decision without me, I must be important.
If everything runs through me, I must be doing a good job.
But sometimes that's ego masquerading as leadership.
The question isn't whether your team needs you.
It's what they need you for.
Do they need you to make every decision, solve every problem, and tell them what to do next?
Or do they need you for mentorship, guidance, feedback, and development?
Those are very different relationships.
I like to think of leadership a little like train tracks.
Your team is the train.
As a leader, you help establish the direction, the parameters, and the boundaries that allow that train to move where it needs to go.
Your job isn't to become the engine.
Stop Being the Answer Machine
Someone comes into your office with a problem.
You know the answer.
So you give it to them.
Problem solved.
Except, what did they actually learn?
This is where I changed the way I approached problem-solving with my teams.
Instead of immediately giving someone the answer, we'd work through the problem together.
What happened?
Why do you think it happened?
What created the problem?
What have you already tried?
What do you think we should do next?
Most of the time, something interesting happens.
They already know more of the answer than they think they do.
My job becomes helping them work their way toward it.
There's a major difference between solving someone's problem and teaching someone how to solve problems.
One gets you through today.
The other develops capability for tomorrow.
Eventually, I don't want someone coming to me saying:
"Adam, what should I do?"
I want them coming to me saying:
"Here's the problem. Here's what I think caused it. Here are the options. Here's what I think we should do."
Now we're developing a leader.
Autonomy Still Needs Guardrails
None of this means stepping away and telling people:
"Good luck. Figure it out."
That's not development.
That's abandonment.
People need clarity.
They need expectations.
They need resources.
And they need to understand what success actually looks like.
If I'm giving someone ownership of a project, I want them to understand the target and the parameters they need to operate within.
Then:
Go own it.
I'm here if you need me.
We'll keep an open feedback loop.
And when it's over, we'll look at it together.
What went well?
What didn't?
What did we learn?
What should we do differently next time?
That's where mistakes become valuable.
Because success gives us information.
Failure gives us information too.
If I constantly step in before someone can make a mistake, I'm taking that information away from them.
Autonomy without expectations can become ambiguity.
But expectations without autonomy becomes control.
Good leadership requires both.
Micromanagement Teaches People to Need You
This is one of my biggest issues with micromanagement.
It doesn't just tell someone:
“I don't trust you.”
It can actually teach them to stop trusting themselves.
If every decision gets second-guessed, every mistake gets immediately corrected, every project gets taken over, and every meaningful choice requires approval, eventually the safest behavior becomes:
Wait for the manager.
Then six months later the leader is frustrated because:
"Nobody takes initiative around here."
But what behavior did we teach them?
If you repeatedly teach people not to make decisions without you, you can't be surprised when they stop making decisions without you.
That's not an employee problem.
That's a system the leader helped create.
The Goal Is a Self-Sustaining Ecosystem
One of the things I'm most proud of from my years leading people was developing someone directly underneath me to the point that they could do my job.
We had constant feedback loops.
Training.
One-on-ones.
Open conversations about expectations.
I shared what had made me successful, but I also gave them room to develop their own judgment.
Eventually, they didn't need me to tell them what to do.
They understood the job.
But then something even better happened.
They began developing the person underneath them to do their job.
That's when leadership starts to compound.
I didn't just help create one capable employee.
That person was now creating capability in someone else.
That's the ecosystem I believe good leadership should create.
Information moves.
Feedback moves.
Ownership moves.
Capability moves.
And none of it depends on one person being in the building.
Give Away What You Know
An insecure leader can look at a highly capable person underneath them and see a threat.
What if they outperform me?
What if they become more valuable?
What if they eventually take my job?
So information gets withheld.
Visibility gets limited.
Decision-making stays centralized.
The leader remains the gateway everyone has to go through.
It might make that leader feel secure.
But it makes the organization fragile.
Because when knowledge, relationships, and decision-making live inside one person, what happens when that person leaves?
The capability leaves with them.
I don't think leadership is about protecting your value by withholding it.
I think it's the opposite.
Give away what you know.
Teach people how you think.
Let them challenge you.
Give them opportunities to own things.
Allow feedback to travel both ways.
And when someone becomes capable enough to outperform you in something?
Good.
You helped create that.
What Happens When You Leave?
Eventually every leader leaves the room.
Maybe it's for the day.
Maybe it's vacation.
Maybe it's a promotion.
Maybe one day you leave the organization entirely.
What happens next tells you a lot about what you built.
Do decisions stop?
Do people wait?
Does performance decline because the person holding everything together disappeared?
Or does the team keep moving?
People solve problems.
Standards remain.
Feedback continues.
Someone you developed is now developing somebody else.
That's the goal.
And yes, I hope the people I've led miss having me around.
Relationships matter to me.
But I'd rather be missed because of the impact I had on people than needed because they couldn't function without me.
The goal of leadership isn't to build an organization around your presence.
It's to build capability that remains in your absence.
Set the direction.
Give people the tools.
Create clear expectations.
Let them own decisions.
Let them make recoverable mistakes.
Build feedback loops.
Give away what you know.
And eventually, watch them teach someone else.
The best leaders don't create dependence.
They create more leaders.
Comments