Are you frustrated that your team keeps coming to you for answers?
Do you feel like projects only move forward when you push them?
Do you find yourself wondering:
• Why don’t they take ownership?
• Why don’t they show more initiative?
• Why aren’t they thinking ahead?
• Why am I involved in everything?
If so, you are not alone.
This is one of the most common leadership challenges I encounter coaching senior leaders and executive teams.
The symptoms are familiar.
You are in back-to-back meetings.
Questions arrive all day.
Decisions pile up on your desk.
You have no time for your strategic work.
You feel like the bottleneck.
You may even find yourself muttering the dreaded word:
“Micromanagement.”
Or your team might be muttering it behind your back.
The problem might be your team.
And it probably starts with you.
Sorry. 😉
My clients hear this from me all the time:
If you want your team to change, you have to change first.
That is where ownership starts.
The Killer Coaching Question
When a leader describes these frustrations, I always ask:
“What is your role in this dynamic?”
That question usually creates a pause.
Because most leaders immediately focus on what their team is doing wrong.
The breakthrough happens when they examine their own contribution.
A Real Leadership Example
I recently worked with a President and their Senior Leadership Team.
The President wanted more ownership.
More accountability.
More initiative.
More cross-functional thinking.
Less dependency.
Instead, leaders kept bringing problems upward.
Not recommendations.
Not options.
Problems.
The President wanted them to engage their peers, think systemically, and bring thoughtful recommendations.
Then something interesting happened.
In a separate 1:1 session, one of the Senior Leadership Team members complained about exactly the same thing regarding their own team.
“They keep coming to me for everything.”
I asked:
“Does this sound familiar?”
Lightbulb.
The President wanted him to step up.
He wanted his team to step up.
He suddenly realized the dynamic was repeating itself.
The leadership challenge was not isolated.
It was systemic.
This idea comes from systems thinking, popularized by thinkers such as Peter Senge in The Fifth Discipline. Systems create patterns of behaviour that repeat across levels of an organization.
What happens at the top often cascades throughout the system.
The President changes.
The SLT changes.
Managers change.
Teams change.
Or not.
Why Leaders Create Dependency
Most leaders do not intentionally create dependence.
In fact, their intentions are usually positive.
They want to help.
They want success.
They want efficiency.
Common reasons include:
• You have done the job before
• You know the answer
• You can solve it quickly
• You want to be helpful
• You want quality outcomes
• You want consistency
• You are avoiding uncertainty
There are often hidden payoffs too.
Stepping in can provide:
• A sense of control
• Feeling needed
• Feeling knowledgeable
• Feeling powerful
• Being seen as supportive
• Immediate progress
Unfortunately, those short-term benefits often create long-term dependence.
The First Step: Define Success
Before delegating anything, get clear on what success looks like.
Many leaders skip this step.
Organizations have visions.
Projects have objectives.
Your delegation should too.
Ask yourself:
• What outcome do I want?
• What does good look like?
• What decisions can they make?
• What decisions remain mine?
The clearer you are, the easier it becomes for others to succeed.
The Seven Levels of Delegation
One of the most useful frameworks comes from Michael D. Watkins, author of The First 90 Days, and variants of delegation levels have also been popularized by leadership thinkers such as Jurgen Appelo and John C. Maxwell.
The principle is simple:
Not every task requires the same level of autonomy.
Think of delegation as a spectrum.
Leader Delegation Level Employee Autonomy
The mistake many leaders make is assuming delegation is all or nothing.
It is not.
The conversation should explicitly define where the task sits.
Match Autonomy to Capability
One critical factor often gets overlooked.
Does the employee actually have the skills to succeed?
If not, autonomy without support becomes abandonment.
Ask them:
• Do they know how?
• Have they done this before?
• What training is needed?
• Who can teach them?
• What resources are available?
Make skill gaps visible early. What do they need to do to be capable? What do you need to do to upskill them?
That creates learning rather than frustration.
The Hardest Part: Letting Go
For many leaders, delegation is not a capability problem.
It is an emotional one.
You know how you would do it.
You know how it should be done.
You know how to get there quickly.
The challenge is letting go of “the how.”
You can define:
• Why it matters
• What success looks like
• Boundaries and constraints
Then allow someone else to determine the path.
Their route may differ from yours.
That is often where growth happens.
For them.
And for you.
This Applies at Home Too
Parents understand this instinctively.
You do not teach a child to ride a bike by doing all the pedalling yourself.
You gradually transfer responsibility.
My Dad ran beside me holding my banana-seat until I was stable enough for him to let go.
The same principle applies at work.
Ownership grows through experience.
Confidence grows through responsibility.
Capability grows through practice.
Final Thoughts
If your team lacks ownership, accountability, initiative, or independent thinking, start by looking at the system.
Then look at yourself.
Ask:
“What is my role in this dynamic?”
That question may be uncomfortable.
It is also where change begins.
Leadership is not about having all the answers.
It is about creating the conditions where others can develop them.
The goal is not for your team to need you more.
The goal is for your team to need you differently.
Ready to stop being the bottleneck?
Soft Skills HARD RESULTS is a practical guide to exactly this, written for leaders who are technically excellent but want to get more from the people around them. Purchase the book here.
