Why Most Leadership Development Fails, and What Works Instead

14 min read
The short version
Organisations spend an estimated USD 60 billion a year on leadership development, yet as little as 5% of training reaches the job and nearly a third of L&D leaders cannot point to any return. The content is rarely the problem. The failure is structural. Development is sold as an event when it only works as a process, and the responsibility for it is rarely held clearly by anyone. This is what fails, why, and the questions to ask before you fund another program.

Years ago I attended a two-day new-leader workshop. I remember sitting in the room thinking I already knew much of the content. Not because I was clever or arrogant. I had been an individual contributor for years, working under some good leaders and some bad ones, and I had absorbed plenty by watching. The fundamentals weren't new to me. The workshop covered them well, but it covered them.

Two days later I was back at my desk, trying to lead my first team, and I was completely unprepared for the things I had to do. How do I run a performance review here? How do I balance pushing my people to deliver with supporting them when the pressure is on? How do I communicate expectations clearly enough that nobody is guessing? How do I know when to step in and when to give someone space to figure it out themselves? Navigating people turned out to be genuinely hard, and the workshop hadn't helped me with any of it. Not because the workshop was bad. Because the workshop, on its own, was never going to be enough.

That experience was one of the things that eventually led me to build a development consultancy with my partner Rob, and it shapes how we think about what leadership development is for. The workshop did its job, badly, but the bigger failure was that nobody owned the work between the workshop and the daily reality of leading. The provider had stopped. My organisation hadn't picked up. I was on my own with a list of unanswered questions and a half-day's worth of frameworks I would never use again.

This is the new leader version of a problem that runs much wider. The experienced leader's version is quieter but the same shape. They are assumed to be capable, sent on the occasional executive program that covers what they already know, or given a coach with no integration into anything else, and left to navigate whatever new challenge has arrived (a restructure, a doubled team, hybrid working, leading alongside AI) without any real development structure at all. Both fail for the same underlying reason. Development is treated as a thing you finish, when it is something you have to keep doing.

The new leader
The experienced leader
What gets bought
A two-day workshop on leadership fundamentals
A generic executive program, or a one-to-one coach in isolation
What fails
The content is pitched at concept level when the leader needs daily craft, and nothing follows it
The development is generic when the leader needs specific stretch, or siloed when it needs integration
What is missing
A system that helps them translate concepts into how things work here
An honest conversation about where they are still developing, and the structure to keep doing it
The assumption
They need to be taught
They already know enough

If you have been burned by a program that promised transformation and delivered a nice few days out of the office, or you are about to sign off on a budget and want to avoid that outcome, this is for you.

The three jobs almost nobody splits clearly

Most conversations about why leadership development fails treat it as if one party is responsible. The provider. The L&D team. The leader. In reality, three jobs exist, and development fails most often because nobody has agreed who does which.

The provider's job is to teach what is transferable. The structure of a good coaching conversation. How to give feedback that lands. How to think about delegation, decision-making, holding the line on hard calls. Concepts and skills that carry across organisations and contexts. A good external provider does this part well. A bad one promises more than they deliver and leaves the rest unmentioned.

The business's job is to teach what is specific to here, and to build the structure that makes the rest applicable. How performance reviews really work in this company. The unwritten rules of how decisions get made. The values that guide trade-offs. The processes, the tools, the calendar. And, every bit as importantly, the structure that supports a leader after the workshop. Their own manager, the time to practise, the permission to be imperfect. The business owns the integration problem and the reinforcement problem. Almost nobody owns either properly.

The leader's job is to do the hard work of trying, getting it wrong, asking for feedback, reflecting, adjusting. No provider does this for them and no business forces it. The leader has to be willing to develop. Most are. They rarely get the support to do it well.

When leadership development fails, it is almost always because the business has assumed the provider will cover its job too, the provider has been happy to imply they will, and nobody is doing the bit that really matters, which is the integration of the craft into the daily life of the work, sustained over time. The workshop becomes the scapegoat for a system that was never built around it.

The numbers nobody puts in the proposal

The spend is enormous. Research published in Behavioral Sciences puts the global figure at an estimated sixty billion US dollars a year. This is not a fringe activity. It is one of the largest sustained investments organisations make in their own people.

Few things shape an organisation as much as the quality of its leaders. Gallup's research, drawn from millions of employees, found that managers account for at least 70% of the variance in team engagement, more than pay, perks or the mission statement on the wall.

Managers account for at least 70% of the variance in team engagement. Gallup

And engagement is not a soft number. Gallup's 2024 data shows organisations with highly engaged teams run around 21% more profitable and see far lower turnover than those with disengaged ones. So the people you put in charge, and how well you develop them, move the things the business cares about most. Performance, culture and whether your best people stay. Developing leaders well is not a nice-to-have. It is one of the highest-leverage decisions an organisation makes, which is exactly why getting it wrong is so costly.

The returns are far harder to find. Across the research, the same pattern repeats. The application of what gets learned is minimal, with some studies finding as few as five per cent of participants successfully putting it to work, and around one in ten programs failing outright. The people who buy and run this work see it too. In a survey of 500 CHROs and L&D leaders, nearly a third said their learning and development investment had little, no, or unknown impact on revenue or profit. Read that again. The people closest to the spend, the ones who commission it, cannot point to what it returned.

The clearest number is the one about transfer. Research published in the Proceedings of the National Academy of Sciences estimated that as little as 15% of learning from traditional classroom-style training results in sustained behavioural change in the workplace. So for every dollar that goes into the room, somewhere between seventy and eighty-five cents of the learning never makes it back to the job. It fades on the drive home.

These figures have not improved meaningfully in decades. That tells you something important. This is not a problem of better slides or a more charismatic facilitator or a slicker app. The same approach keeps producing the same disappointing result because the approach itself has the same flaw built in.

The failure has a shape

To fix it, you have to see it clearly. The diagnosis is not that any one program is bad, or any one provider is incompetent, or any one buyer was naive. The diagnosis is that the way leadership development is bought, delivered and supported has a particular shape, and that shape produces predictable failures. The next several sections walk through what those failures look like. They start with the one the whole industry blurs.

Training is an event. Development is a process.

A training event is a moment. It has a start time and an end time. People gather, content gets delivered, and then it is over. The format is efficient and easy to budget for. You know exactly what it costs and exactly when it finishes. This is precisely why organisations love it and precisely why it fails.

Development is not a moment. It is what happens to a person over time as they try something, get it wrong, get feedback, adjust and try again. It is slow, uneven and hard to put on an invoice. It does not finish on Friday. It happens in the ordinary run of the work, in the conversations a leader has with their team on a Tuesday afternoon, in the way they handle a difficult piece of feedback, in the decision they make under pressure and reflect on afterwards.

When you fund the event and not the process, you are paying for the easy 15% and ignoring the hard 85%. You are buying the part that feels like development and skipping the part that builds leaders.

Nobody became a good driver by attending a driving seminar. They became a good driver by driving, badly at first, with someone in the passenger seat giving feedback, over many months. Leadership is no different. The workshop is the seminar. What is almost always missing is the months of practice with someone in the passenger seat.

Stuffed with so much content that none of it sticks

There is a particular version of the event that fails harder than the rest, and it fails for a reason that looks like generosity.

Programs get overstuffed. Too many models, too many frameworks, too many concepts crammed into a day or two because more content feels like more value. The buyer wants their money's worth and the provider wants to look comprehensive, so the result is a program that introduces twelve ideas and lands none of them. People walk out with a blur. Ask them a fortnight later what they took away and they will struggle to name one thing they have changed.

This is the event model taken to its logical end. If the workshop is the only shot you get, you try to fit everything into it. But overwhelm produces under-application. A program that taught one habit properly, and gave people the time and support to practise it, would change more behaviour than one that paraded a dozen.

The harder discipline, and the more useful one, is restraint. Pick the two or three things that matter most for these leaders, in this organisation, right now. Teach those properly. Leave the rest out. A program confident enough to do less is usually one that understands how change really happens.

Sent in to fix something a workshop was never built to fix

Often the program is commissioned at the worst possible moment, as a response to a problem already on fire.

The team dynamic has soured. Cross-team collaboration has collapsed. Divisional strategies are competing or unclear and pulling people in opposite directions. Someone decides the answer is leadership training. So a short, intensive program gets dropped on top of a structural or relational problem it was never designed to reach.

You have to start somewhere, and naming the problem in a room is a reasonable first move. But a two-day intensive cannot resolve a systemic issue. The problem is organisational. The intervention is individual and brief. The maths does not work, and when the dynamic has not shifted a month later, the conclusion drawn is that leadership development does not work, when the real issue is that an event was asked to do a structure's job.

Boston Consulting Group's research makes the underlying point bluntly. Training money gets wasted when the training is not geared to drive business results, because it becomes separated from the organisation's objectives. A program commissioned as a panic response is the sharpest version of that disconnect. It was never tied to the actual problem in the first place, so even excellent content has nothing to grip.

This is the same failure in a different costume. The problem was deep and ongoing, so the response needed to be deep and ongoing. A sustained effort, aimed squarely at the real issue and run across time, is the thing that moves it. A workshop dropped on top of it is a sticking plaster on a structural fracture.

The people most often failed by this

Both leaders we met at the top of this piece end up here, for opposite reasons.

The newly promoted one, the strong IC who got handed a team, fails because they were given concepts when they needed the daily craft, and nobody helped them translate. The experienced one fails for the reverse reason. They are assumed to have arrived. Development stops being aimed at them. Then the role changes underneath them (a restructure, a doubled team, hybrid working, leading alongside AI) and they are expected to handle it from a repertoire that was built for the role they used to have.

Both failures come from the same place. An assumption that development is a thing you finish, when it is something you have to keep doing all the way through.

Life gets in the way, and autopilot wins

So why does development so rarely get kept going? Because the rest of the failures we have walked through play out at the level of design and structure. This one plays out inside the leader's week.

A leader comes out of a good workshop genuinely intending to lead differently. Then Monday arrives. The week gets busy. They are pulled in fifteen directions, the targets are still due, the inbox is still full, and the new behaviour, the one that does not yet come naturally, is the first thing to go. Under pressure, people revert to what is automatic. The half-learned habit gets dropped and autopilot takes over.

This is not weakness. It is how everyone behaves under load. New behaviour is fragile, and without something holding it in place, the old one wins.

This is the failure that the industry knows most about, and the one it has done least to fix.

The market knows this. Most of it has not fixed it.

To be fair to the industry, none of this is a secret. L&D publications and major research bodies have been writing about it for years. The Harvard Business Impact 2025 study of more than 1,100 L&D professionals across 14 countries names the gap clearly. The Korn Ferry Institute's research independently identifies organisational context as the one area most often overlooked, and points to the leader's own manager as the most critical lever for transfer. The blended-delivery shift is real, and well intentioned. Buying a flat two-day workshop with nothing around it is increasingly seen as the low-impact option it always was.

The trouble is that "behaviour change" has become a marketing line faster than it has become a practice. A great many programs that promise reinforcement and application deliver a workshop with a few extras bolted on, a pre-read here, a single follow-up call there, and call it a journey. Real reinforcement, the manager actively involved, the time to practise, the integration into the day job, is harder to build and rarer to find. The structure is thin, the manager is still absent, and the behaviour still fades.

The deeper failures are quieter but more entrenched. The three roles we named earlier (provider, business, leader) are still rarely split clearly when a program is bought. Senior leaders routinely delegate L&D to HR without personal involvement. Managers see training as optional rather than something they own. Most programs still measure success through attendance and satisfaction rather than through whether anyone leads differently. None of these are secrets either. They are sitting in plain sight in the same industry research that names them, year after year, while the way programs get bought and run shifts only at the margins.

The market has bought the idea that development is a process. It has mostly not built the structure to deliver one.

When a workshop is the right call for leadership development

Good development starts by splitting the work cleanly. The provider, the business and the leader each have a role, and each has outcomes they own. Once those are agreed, the question of format follows. The workshop is one format among several, and it pulls its weight when used well, but only when it sits inside a structure rather than instead of one.

There are two situations where a workshop genuinely earns its place. The first is awareness. A workshop is a good way to introduce a new idea, build shared language across a group, or signal that the organisation takes something seriously. If the goal is genuinely to inform rather than to change behaviour, a workshop does that job well. The mistake is expecting awareness to become capability on its own, with nothing built around it.

The second is a kickoff. The best programs often start with an event, because bringing people together generates energy and a shared starting point. The difference is what comes next. In a program that works, the workshop opens the process. In a program that fails, the workshop is the process. Same beginning, completely different result, decided entirely by whether anything is built to follow it.

What development looks like when it works

That structure, the one a workshop sits inside, is what we build at Catalyst Enablement.

Our leadership programs are built around each organisation's context rather than delivered as the same off-the-shelf content to everyone, and the coaching within them adapts to the individual leaders taking part. They run across time, not across a single offsite. They build practice and reinforcement into the months after the initial sessions, so the new behaviour has somewhere to live across the busy weeks where it would otherwise fade.

The most distinctive piece is who holds the work in between sessions. We put each leader's own manager, the person one level up, into the design as the one who keeps the development alive. That manager is the biggest influence on whether anything sticks, so the structure is built to be held by them. The framework underneath gives them a simple, repeatable way to hold the development conversations most managers were never trained to have. The person being coached does the thinking. The coach holds the structure.

That shift, from event to process, is the whole game. It is the difference between the 15% that sticks and the 85% that fades.

There is a fair objection here. These managers are busy too, pulled in as many directions as anyone, so how do they find the time to coach the leaders below them? The answer is the reason structure matters. Coaching feels like extra work when a manager has no method, because then every development conversation is invented from scratch and lands as one more project on the pile. A simple, repeatable structure does the opposite. It makes the conversation shorter, lighter and easier to repeat, and it happens inside the one-to-ones and check-ins the manager is already holding with their people. The point is not to add coaching on top of the week. It is to change what already happens in the time that is already there.

None of this makes behaviour change easy. It stays hard, because changing how a person leads is hard, and no framework removes the effort or the relapses. What a structure does is give the effort somewhere to live across the months, instead of leaving it to evaporate the moment the workshop ends. That is a more honest promise than transformation in two days, and it is the one that holds up.

It also matters more now than it used to. Leadership itself is changing, and the leaders coming through are increasingly managing people and tools that know more than they do about the work in front of them. Rob has written about that shift in leading people who know more than you do, and the throughline is the same. When you lead by holding the structure of good conversations rather than by being the most expert person in the room, you need that structure to be something you practise, not something you once heard about at an offsite.

How to tell if a program will drive real change

If you are weighing up a leadership program, judge it on its structure, not its brochure. The content will look good. They all do. The signals that predict whether it will change behaviour sit elsewhere. Ask these questions, and weigh what a good answer sounds like against a weak one.

  • Who owns which part of the development? A strong answer separates clearly what the provider will do (the transferable craft), what the business needs to own (the integration with how things work here, plus reinforcement) and what the leader is responsible for (showing up, practising, being honest about where they are stretched). A weak answer is a provider pitching as if they will do all of it, or no clarity at all.
  • What happens in the eleven months after the workshop ends? A strong answer describes a structure, ongoing coaching, practice, reinforcement, follow-up. A weak answer is vague, or describes more content. If there is no real answer, you are buying an event.
  • How will the participant's own manager be involved? A strong answer builds the manager into the design as the person who reinforces the behaviour. A weak answer leaves them out entirely. The single biggest influence on whether someone develops is their direct manager, and a program that ignores that relationship has left its most powerful lever on the table.
  • How is this tailored to our leaders and our context? A strong answer asks about your problems, your industry and the level your people are leading at, and uses your live challenges as the material. A weak answer is the same program everyone else gets.
  • How is this calibrated to where these leaders truly are right now? A strong answer differentiates between new leaders needing the daily craft and experienced leaders needing specific stretch. A weak answer is the same content for everyone, regardless of where they sit on their own development.
  • How much are you trying to teach, and over what time? A strong answer is paced. It might cover a lot of ground, but spread across months with practice between each piece, so one thing lands before the next arrives. A weak answer crams a long list of models into a day or two and calls the length value. The problem was never how much gets covered. It is how much gets crammed into too little time, because content with no room to be practised is content that fades.
  • How will we know if behaviour changed, not whether people enjoyed the session? A strong answer names the behaviours it expects to shift and how it will track them. A weak answer measures attendance, satisfaction and self-reported reflections, none of which tell you whether anyone leads differently.

A provider with a real point of view will welcome these questions, because the answers are where their value lives. A provider selling a two-day event will steer you back to the brochure.

Leadership development is not a waste of money. Delivered as an event, dropped on a busy organisation and asked to fix things it was never built to fix, it mostly is. Delivered as a structure that runs across time, tied to the real work, held by the managers who are already there, and split honestly between the provider, the business and the leader, it becomes one of the highest-return investments an organisation makes. The difference was never the quality of the program on paper. It is what happens after everyone walks out of the room, and who is holding which part of the work.

If your last program faded the moment people reopened their inbox, it was never development. It was an event. The good news is that the difference is structural, which means it is fixable, and it is the work we do.

Talk to us about building development that lasts past Friday.

Sources

blogs and articles

Keep reading

Leadership In The Age Of AI: The Work Is Good. The Muscle Isn’t Built

AI has decoupled the work from the worker. A junior now produces what once signalled ten years of experience, and the old shortcut for reading capability no longer holds. Leading well means judging the work and the person as two separate questions.

How Professional Reputation Really Gets Built at Work

Reputation is built from how others experience you, not what you intend. Here is what closes the gap, and why it matters more now.
let's talk

Talk to us about your goals.

We work with organisations across Australia and New Zealand to build capability that delivers results.