The most dangerous leader is not always the weak one.

Sometimes it is the highly capable one.

The one who sees the answer before everyone else. The one who can cut through noise, make the call, write the message and get the thing moving.

The organisation admires them for it.

Until, slowly, it starts depending on them for it.

There is a kind of leader I encounter often: experienced, quick, commercially sharp, able to hear a complicated problem and see what needs to happen.

When something starts going wrong, they step in. A project is drifting, so they create the plan. Two functions cannot agree, so they broker the decision. Communication is unclear, so they write the message. Nobody is owning the follow-through, so they chase it.

Usually, things improve.

Which makes the behaviour hard to question.

This pattern keeps appearing. Good people sit around the table. Intelligent people. People who care about the organisation and want it to succeed.

Yet the organisation still depends on a small number of people to turn discussion into movement.

Information is shared, but does not travel far enough. Priorities are discussed, but not translated into work. Projects exist, but ownership and deadlines remain loose. Meetings happen, but decisions return because they never really closed.

It would be easy to call this an accountability problem. I do not think that goes far enough.

It is a management team development problem.

If I believe people are not doing enough, my instinct will be to increase pressure: more checking, more follow-ups, more instructions, more senior involvement.

For a while, this works. Things move faster.

But the organisation is also learning where responsibility really sits. Not in the org chart, but in practice.

People learn that when something becomes complicated, important or uncomfortable enough, someone more senior will enter the room and sort it out.

Capable adults can become dependent in a system like that. Not because they lack ability, but because the organisation rewards escalation more than judgement.

One of the hardest transitions in leadership is moving from solving problems well to building people who can solve problems without you.

The second is slower.

Telling someone what to do may produce an answer in five minutes. Asking how they see the problem, what risks they will carry, what they recommend, and how they will bring others with them takes longer.

Their answer may not be as good as yours.

At least not yet.

That yet is where leadership development lives.

Do they ask the responsible person to make the call, or quietly take the decision back? Can they tolerate a slightly imperfect solution so someone else learns to carry responsibility? Can the team disagree and still close? When execution becomes difficult, does ownership stay where it belongs, or migrate upwards?

That is the real curriculum.

Management team problems are not always dramatic. Sometimes the team simply becomes a sophisticated discussion forum: lots of intelligence, lots of conversation, very little closure.

When that happens often enough, the senior leader compensates. They become more involved because somebody has to keep the organisation moving. Everyone else becomes slightly less responsible. So the senior leader becomes even more involved.

Management team development is not an argument for letting important things fail in the name of learning. It is about noticing when intervention has become the operating model.

There is a difference between stepping in because a situation genuinely requires you and stepping in because the organisation has never developed another way of functioning.

That distinction matters even more during growth, transformation or uncertainty.

As complexity grows, the heroic leader model stops scaling. Too many decisions intersect. Too much information is dispersed. Too many consequences are impossible for one person to see.

At that point, leadership cannot simply mean having stronger individual leaders. The management team itself has to become capable of leading.

That means making decisions together and actually closing them. Disagreeing without endlessly reopening the question. Communicating decisions through their own parts of the organisation. Challenging each other rather than waiting for the CEO to arbitrate. Carrying the consequences of collective decisions.

The real test of a management team is not whether it can perform well when the CEO is in the room.

It is what it can carry when the CEO is not.

Can it close decisions? Hold tension? Disagree without fragmenting? Communicate clearly? Take ownership without waiting for rescue? Develop judgement in the layer below?

If yes, the organisation is building leadership capacity.

If no, the solution may not be another leadership programme. It may be time to look more closely at how the team actually leads when the real work begins.

Because a strong management team should not make the leader's life easier.

Over time, it should make the organisation less dependent on the leader.

If this is a pattern you recognise in your management team, book a management team discovery conversation with me