Stop Sending Better People Back Into the Same Broken System.

When a leadership team is not working, the instinct is understandable.

Find the person who is struggling. Coach them. Give them feedback. Send them on the programme. Help them become more confident, more self-aware, more decisive or better at difficult conversations.

That can be valuable work.

It can also be completely insufficient.

Because the individual is rarely the whole problem.

A leader can leave a coaching session clear, committed and ready to act differently. Then they walk straight back into a team that still avoids conflict, blurs ownership, escalates every difficult decision and rewards the people who keep everyone comfortable.

They have changed their intention.

The system has not changed its behaviour.

The team teaches people how to behave.

Every leadership team has an operating pattern, whether it has named it or not.

It decides what happens when someone disagrees. It decides whether bad news travels early or late. It decides who really makes the call. It decides whether people speak plainly or carefully manage the room.

That pattern is stronger than an individual’s good intentions.

If the team rewards agreement, the leader who raises the difficult point becomes “negative.”

If the team tolerates unclear ownership, the leader who tries to create a decision gets told to be more collaborative.

If every risk is escalated to the founder, the leader who acts independently gets treated as reckless.

If poor performance is handled privately and vaguely, the leader who holds a clear standard is seen as disruptive.

You can coach that person for months. But if they return to the same pattern every week, you are asking them to survive the system rather than helping them change it.

That is maintenance. It is not transformation.

Coaching matters. It just cannot carry the whole job.

This is not an argument against coaching.

Coaching can increase awareness. It can make a leader see the habit they could not see before. It can help them understand how they are landing, practise a difficult conversation or build the confidence to take a position.

Those things matter.

But coaching one person while ignoring the group dynamic assumes the issue lives inside that person alone.

It often does not.

The problem may be a decision process that makes ownership impossible. It may be a leadership meeting where no one is expected to decide. It may be a founder who says they want challenge but punishes disagreement. It may be a group that has spent years learning to route everything around one powerful voice.

None of that disappears because one leader becomes more articulate.

You cannot coach someone out of a system that keeps creating the same failure.

Stop asking, “Who is the problem?”

The more useful question is: What pattern is this team creating together?

That question changes the work.

Instead of isolating a person, you look at the operating environment they are in. You look at the repeated moment where execution breaks down. You look at what the team does under pressure, not what it says it values in a workshop.

Start with the evidence:

• Which decisions keep returning unresolved?
• Where does ownership disappear?
• What conversations does the team keep postponing?
• Who gets listened to, and who gets worked around?
• What type of bad news arrives too late?
• Which leaders are carrying work that belongs elsewhere?
• What happens when someone challenges the usual way of operating?

You are not looking for someone to blame. You are looking for the pattern that makes the same outcome predictable.

Once the pattern is visible, the team can no longer pretend that every problem is an individual issue.

Real change has to happen at two levels.

Effective leadership development works with both the individual and the team.

At the individual level, people need a clear baseline. They need to understand the behaviour they bring into the room: where they avoid, over-control, withdraw, rescue, dominate or wait for permission.

At the team level, they need to see what happens when those behaviours combine.

One person avoids conflict. Another fills the silence. Another sends the issue back to the founder. Another says nothing and then disagrees afterwards. The result is not four separate development needs. It is a team pattern.

The work then becomes practical:

1. Make the pattern visible. Name what actually happens, using examples the team recognises.
2. Set the operating rules. Clarify ownership, decision rights, escalation points and the purpose of the meeting.
3. Practise in real work. Do not leave the new behaviour in a training room. Use it on the live decisions that are currently stalled.
4. Hold the standard together. A new rule means nothing if the team lets the old response return under pressure.
5. Track whether the system is changing. Look for movement in decisions, ownership, speed, candour and follow-through.

This is harder than giving two leaders access to coaching and hoping their improvement spreads.

It is also more honest.

The proof is what happens when support is removed.

A development intervention has not worked because people enjoyed it, completed it or said it gave them useful insight.

It has worked when the team handles the next difficult issue differently without needing an outside person to rescue the conversation.

Do they name the real issue sooner?

Does someone own the decision?

Can the team disagree without making disagreement personal?

Does a leader act without waiting for the top of the organisation to tell them what to do?

Does bad news arrive while there is still time to change the outcome?

That is the standard.

The goal is not a dependent client who needs another intervention every time pressure rises. The goal is leadership capability that lives inside the business.

You can coach the individual.

You still have to fix the team.