A senior leader finishes another twelve-hour day.

The inbox is still full. Several decisions are waiting for approval. Two managers have asked for help with problems they were expected to solve themselves. Tomorrow’s calendar has no space left for strategic work. The leader is frustrated.

“I cannot leave them alone for a day,” they say. “Everything comes back to me.”

Ask the team and you may hear a different version of the same story.

“We have learnt to wait. Whenever we make a decision, it is changed.”

Both perspectives can be true.

The leader feels trapped by a team that does not take enough ownership. The team feels trapped by a leader who does not truly allow it. This pattern is more common than many executives would like to admit. It often develops slowly, disguised as commitment, high standards and personal responsibility. The leader becomes the person who knows the most, solves the fastest and carries the greatest pressure.

At first, this creates results. Later, it creates dependence.

When Competence Becomes a Bottleneck

Many leaders reach senior positions because they are highly capable. They see problems quickly, make connections others miss and know how to act under pressure.

These strengths are valuable. They can also become dangerous if the leader continues using them in exactly the same way after the role has changed.

The skills that help someone become an exceptional individual performer are not necessarily the skills required to build an exceptional organisation.

A capable manager may solve a problem in twenty minutes that would take a team member two hours. Correcting the work personally feels efficient. Taking over appears responsible. The client receives an answer sooner and the immediate risk disappears.

But something else has happened. The manager has solved today’s problem while preserving tomorrow’s dependency.

If this pattern continues, team members stop wrestling with difficult questions. They bring unfinished thinking to the leader because experience has taught them that the leader will provide the answer. Some become cautious. Others become passive. The strongest may eventually leave because they no longer see enough space to grow.

The leader then looks at the team and concludes that nobody demonstrates sufficient initiative. What the leader may not recognise is that initiative has been repeatedly interrupted.

Rescue Is Not Always Support

Good leaders support their people. But there is a difference between supporting someone and rescuing them. Support develops capability. Rescue removes discomfort.

When a leader steps in too quickly, the problem disappears before the employee has had the opportunity to think, struggle, decide and learn. The leader experiences relief because the situation is under control again. The employee experiences relief because responsibility has moved upwards. Both people receive an immediate reward. That is why the pattern is so easy to repeat.

Over time, the leader becomes increasingly overloaded and the team becomes less confident. Eventually, the leader complains that employees are not ready for greater responsibility, while employees complain that responsibility is never genuinely given to them.

The organisation remains caught between two sincere frustrations.

Leaders rarely create this dependency intentionally. Many believe they are being helpful. Some are protecting the organisation from risks they have learnt to anticipate. Others have inherited teams that genuinely lack experience. But even when close control begins for a valid reason, it should not become the permanent operating model. A temporary response to risk can quietly turn into a leadership identity.

The Emotional Reward of Being Indispensable

There is another part of this pattern that is more difficult to discuss.

Being needed can feel good.

It provides evidence of competence, importance and value. The constantly ringing telephone confirms that the leader matters. The overloaded calendar becomes proof of commitment. Solving problems creates a sense of control that strategic work, with all its uncertainty, may not provide.

Some leaders complain about being indispensable while unconsciously protecting that position.

They say they want independent thinkers, but continue to enter every important discussion. They ask for recommendations, then replace them with their own. They delegate tasks but retain every meaningful decision. They tell people to take ownership, yet respond harshly when someone makes a reasonable decision they would not have made themselves.

The team eventually discovers that there is one reliably safe option: wait for the leader. This is not simply a delegation problem. It is often connected to identity.

• If I am no longer the person with all the answers, what is my value?
• If the team can operate without me, will I still matter?
• If someone else develops a better approach, what does that say about my expertise?

These questions are rarely spoken aloud. Yet they can shape behaviour more powerfully than any formal leadership principle. The difficulty is not only learning how to give away responsibility. It is learning how to remain secure while others become more capable and less dependent.

High Standards Can Hide a Need for Control

Leaders who struggle to release control often describe themselves as having high standards. Sometimes that is entirely true. Quality matters. Some decisions carry serious commercial, legal or reputational consequences. Delegation should never mean abandoning judgement.

But high standards and personal control are not the same thing.

A leader with high standards makes expectations clear, defines decision boundaries, ensures that people understand the consequences and creates appropriate checks. A controlling leader allows people to act, but only if they reach the same conclusion in the same way the leader would.

This distinction is important.

There are many ways to produce good work. When a leader corrects every difference in style as though it were a failure in quality, people learn to imitate rather than think. They stop bringing original ideas because originality creates additional risk. The leader may then see a team that appears aligned but lacks intellectual independence. Uniformity is not always evidence of excellence. Sometimes it is evidence that people have stopped offering alternatives.

A useful question for any leader is: “Is this genuinely wrong, or is it simply different from how I would do it?”

The answer is not always comfortable.

The Organisation Pays for Leadership Dependency

A leader-centred organisation can look successful for a long time.

The leader has visibility over everything. Important decisions receive personal attention. Problems are escalated quickly. Clients know who to contact when something goes wrong.

The hidden costs appear gradually.

Decisions slow down because too many of them wait for the same person. Managers become messengers rather than leaders. Meetings multiply because people need access to authority. Strategic priorities are neglected while senior executives solve operational problems.

The organisation may appear fast because the leader responds quickly. In reality, the whole system is moving at the speed of one person’s availability.

This also creates risk.

What happens when that leader becomes ill, takes a holiday, changes role or leaves the company?

If the organisation loses direction whenever one person is absent, that is not proof of the leader’s exceptional value. It is evidence that the organisation has not converted the leader’s value into institutional capability.

The strongest leaders do not simply produce results while they are present. They build the judgement, confidence and systems that allow results to continue in their absence.

Delegation Is Not Giving Away Tasks

Many managers believe they delegate because they distribute work across the team. But assigning a task is not the same as transferring ownership.

Real delegation requires clarity about the intended outcome, the authority the person has, the decisions they can make independently and the situations that genuinely require escalation.

Without this clarity, employees are left to guess. Some take too much risk. Others take none. Effective delegation also requires the leader to tolerate a certain amount of productive discomfort.

The employee may need more time. The first version may be imperfect. The approach may be different. A conversation may not be handled with the same confidence the leader would bring.

That discomfort is part of development.

Leaders cannot ask people to grow while protecting them from every situation in which growth occurs. This does not mean allowing serious mistakes to unfold unnecessarily. It means distinguishing between a mistake that threatens the business and a learning experience that threatens only the leader’s preference for control.

The distinction requires judgement, patience and emotional maturity.

What Happens When You Leave the Room?

A revealing test of leadership is not what happens while the leader is present. It is what happens when the leader leaves the room.

• Do people continue thinking, or do they pause until the leader returns?
• Can managers disagree constructively and still make a decision?
• Do employees understand the priorities well enough to make reasonable trade-offs?
• Can somebody challenge an established approach without waiting for permission?
• Does the team know which decisions it owns?
• Most importantly, can people act without trying to predict what will please the leader personally?

A team that functions only in the presence of authority is not truly empowered. It is supervised.

The transition away from dependency is rarely immediate. Leaders must change their own responses before expecting the team to change its behaviour. If employees have been trained to escalate every question, they will not suddenly become confident because the leader announces a new commitment to empowerment.

They will watch what happens the first time they make a decision independently. That moment will teach them whether the change is real.

The Leader’s Role Must Evolve

There is a point in every leader’s development when personal capability is no longer enough.

The role must shift from solving to enabling, from knowing to questioning and from protecting standards personally to building a system that protects them collectively.

This can feel like a loss at first. The leader is no longer involved in every decision. Problems are solved without their direct contribution. Other people receive recognition for work the leader once would have carried personally.

But this is not a reduction in leadership value. It is evidence that leadership is multiplying. The goal is not for the leader to become irrelevant. The goal is for the organisation to stop using the leader’s constant intervention as a substitute for its own capability. A leader’s legacy is not the number of decisions that required their approval. It is the quality of decisions people can make because they were led well.

If everything still depends on you, the most useful question may not be, “Why is my team failing to take ownership?”

It may be:

“What am I still doing that teaches them to wait?”