Learn

Why Leadership Development Fails to Change Behavior

Leaders learn the move. Then they walk back into a room they still misread, and the move lands on the wrong problem.

Leadership development usually fails to change behavior because it teaches leaders new responses, then sends them back to situations they still misread. The move gets learned. The moment it's supposed to fit doesn't.

That isn't the explanation you usually hear. So let's start with the usual ones.

The usual explanations

In 2014, McKinsey published why leadership-development programs fail. Its four mistakes still hold up: programs overlook context, separate reflection from real work, underestimate mind-sets, and fail to measure results.

All true. But notice what they assume. They assume the leader, once back at work, can see the situation well enough to know which of their new skills it calls for.

The failure underneath

Organizations are bad at that step, and they know it. In surveys of 106 C-suite executives from 91 companies in 17 countries, Thomas Wedell-Wedellsborg found that 85% agreed their organizations were bad at problem diagnosis. 87% agreed the flaw carried significant costs. He published the findings in Harvard Business Review in 2017.

If organizations struggle to diagnose problems, their leaders struggle too. Every day, in much smaller rooms.

Here's what that looks like. The team is stuck in analysis paralysis. Meetings end without decisions, and every new round of data produces more questions instead of fewer. It looks like a process problem, so the trained leader brings in a decision framework. The next meeting stalls in the same place, now arguing about who owns the decision. The process wasn't the real problem. The likelier driver was fear of being wrong with your name on the call. That's hindsight talking, though. In the room, it's a read you'd test before you acted on it.

Or the energy in the room is flat. It looks like a motivation problem, so the leader rallies the team. It works for an afternoon. Then it's flat again, because one person had quietly checked out weeks earlier and everyone else had organized around the gap.

Or one voice dominates the conversation. It looks like a personality problem, so the leader has a quiet word. The person pulls back, and the room gets quieter. That voice had been holding the conversation together, and three people who were already hesitant now have even less cover to speak.

Wrong read. Confident response. Worse outcome.

In every case the leader used a skill their training gave them, and used it well. The training worked. It was aimed at the wrong problem.

What it costs you

Misdiagnosis doesn't only waste the fix. Each time a leader responds to the wrong thing, the team learns what that leader can hear. They start bringing the surface instead of what's underneath.

The meetings get smoother. The updates get safer. The real issues show up afterward, in the hallway and in the message that arrives at nine on a Tuesday night. From the outside it looks like a team that's fine. From the inside, nothing real is moving.

No program can teach its way past that. A leader who can't see what's happening will keep applying excellent skills to the wrong problems, and the team will keep quietly protecting them from the truth.

What changes behavior instead

Teach the read first. Diagnostic Leadership builds the step every other skill depends on: seeing what's actually happening before deciding what to do. Then build it the way skills actually form:

  • Start with the leader's own default. Before anything else, leaders learn the move they reach for when a room goes sideways. You can't override a pattern you can't name.
  • Practice on real situations. Leaders bring the rooms they're actually in, not someone else's case study.
  • Observe and correct. Someone watches the leader read a room and says what they saw.
  • Space it out. Notice, then name, then generate other explanations, then test with one small move. Each step gets a week in real work before the next one is added.

When it takes hold, you can see the capability move from the program into the organization. At OddBytes, one leader went from participant to guiding the next cohort in about five weeks. A participant in that cohort wrote: "He would pop in when it felt necessary, gave feedback that was clear and would pop back out."

That's what transfer looks like. The skill left the classroom and showed up in someone else's room.

Three questions for your current program

  • Does it teach leaders to read a situation before it teaches them how to respond?
  • Do leaders practice on their own work, with someone watching?
  • Can you name one decision that went differently because of it?

If the answer to the last one is no, the program may be good. It just isn't changing behavior.

Questions

Why do leadership development programs fail?

McKinsey's research points to four mistakes: overlooking context, separating reflection from real work, underestimating mind-sets, and failing to measure results. Underneath all four, most programs teach responses without teaching leaders to read the situation those responses are meant for.

What percentage of executives say their organizations are bad at diagnosing problems?

In Thomas Wedell-Wedellsborg's surveys of 106 C-suite executives, published in Harvard Business Review in 2017, 85% agreed their organizations were bad at problem diagnosis and 87% agreed it carried significant costs.

How do you make leadership training stick?

Have leaders practice on their real work, observe and correct them, space the learning across weeks, and start with the skill every other skill depends on: reading what's actually happening before choosing a response.

What is Diagnostic Leadership?

Diagnostic Leadership is the discipline of reading what's actually happening before deciding what to do. Leaders practice it through three questions: What do I see? What's driving it? What does this moment need?