The reason most leadership development does not stick has nothing to do with the quality of the content. It is that the content lives in an event, and the job lives in the flow of work, and the two never meet. People leave an excellent two-day programme genuinely changed, walk back into an unchanged system on Monday, and by Friday the old gravity has pulled them back into exactly who they were. The development did not fail. It was never embedded in the first place. And unembedded development is not really development at all. It is entertainment with a certificate at the end.
This gap is expensive. US companies alone spend almost $14 billion a year on leadership development, yet in McKinsey's survey only 11% of more than 500 executives strongly agreed that their leadership-development efforts achieve and sustain the desired results. Sit with that number for a moment. Nearly nine in ten leaders are spending real money on development they do not believe changes anything durably. That is not a content problem. It is a design problem. The development was bolted on rather than built in.
I have spent two decades on the wrong side of this equation and then the right side of it, and the difference is stark. When development is treated as a course you attend, it decays the moment the course ends. When it is treated as something woven into how the organisation actually works, how people are managed, how decisions get made, how feedback flows, it compounds instead of decaying. The goal is not a better event. It is a system that keeps developing people whether or not an event is running.
The frustrating part is that the individual pieces usually work. The facilitators are good. The frameworks are sound. People genuinely learn. The waste happens entirely in the handoff, the moment a changed person is returned to an unchanged environment with no plan for how the change survives. It is like teaching someone to swim in a calm, shallow pool and then dropping them into a fast, cold river with a completely different current, and then blaming the swimming lesson when they struggle to stay afloat. The lesson itself was perfectly fine. The transfer from pool to river was never designed at all.
I have come to think of the two-day programme as roughly the first ten per cent of the work, and the embedding as the other ninety. Almost everybody spends their budget and attention the other way around. They invest heavily in the event, choose the provider carefully, agonise over the agenda, and then invest almost nothing in what happens afterward. So they pay full price for ten per cent of the outcome and call the result disappointing. It is not disappointing. It is exactly what that allocation of effort was always going to buy.
Why leadership development does not stick: the embedding gap
The core failure is what I call the embedding gap, the distance between where development happens and where the work happens. Close that distance and behaviour changes. Leave it open and even brilliant training evaporates against the daily reality it never touched. The wider that gap, the faster the decay, and in most organisations the gap is enormous: development happens in a hotel and the work happens in a completely different world with none of the same support, permission or reinforcement.
- Development is separated from the work — The programme runs offsite, on its own calendar, disconnected from the projects and pressures people face every day. So the new behaviour has no live context to attach to. It was learned in one environment and abandoned in another, and skills without a home in the daily work do not survive first contact with a busy week.
- The manager was never involved — A person's manager shapes their behaviour far more than any facilitator ever will. Yet most development ignores the manager entirely. They neither attend, reinforce, nor even know what was taught. Without the manager reinforcing it in one-to-ones and real decisions, the new behaviour has no daily advocate and quietly dies.
- There is no accountability for applying it — People are held accountable for their results, not for whether they applied what they learned. So the learning becomes optional, and optional things lose to urgent things every single time. What gets measured and expected gets practised; what is merely hoped for gets forgotten by the second week.
- The system around the person did not change — You can develop a person perfectly and drop them back into a structure that rewards the old behaviour. The structure wins, every time, because it is present every day and the training was present for two. If your promotion criteria, incentives and decision rights still favour the way things were, no amount of individual development will hold against them. You are effectively asking one person to out-argue the entire operating system of the company, alone, on willpower. They will lose, and they should not be blamed for it. The design set them up to fail.
Leadership development that sticks is not an event people attend. It is a property of the system people work inside, where managers reinforce it, the work provides the practice, and the structure rewards the behaviour you developed. Build the system and the development compounds. Skip it and even the best programme decays by Friday.
How to embed leadership development so it actually holds
Embedding is not more training. In many cases it is less training and more design, deliberately wiring development into the machinery of the organisation so the growth continues long after any programme ends. These are the moves I make when the brief is to make development stick rather than just happen.
Notice that none of these moves are about the classroom. Every one of them is about what surrounds the classroom, the manager, the work, the accountability, the structure. That is deliberate. The classroom is the one part of development that already works reasonably well, so pouring more effort into it produces diminishing returns. The leverage is entirely in the environment the learner returns to. If you improve the two-day programme by twenty per cent, you get a marginally better event. If you improve the environment it returns into, you change whether any of it survives at all. That is where the disproportionate return lives, and it is the part almost nobody is funding.
- Anchor it to real work: Attach development to a live remit, a hard project, a struggling team, a real decision. People grow by doing difficult things with support, not by discussing them in the abstract. The work is the curriculum.
- Make managers the primary developers: Equip and expect every manager to develop their people in the ordinary flow of one-to-ones, feedback and delegation. The manager is the highest-leverage development tool in the company, and usually the most neglected one.
- Build accountability for application: Hold people accountable not just for outcomes but for practising the capability you invested in. What is expected and reviewed gets done. What is merely offered gets shelved.
- Change the surrounding system: Align promotion, incentives and decision rights with the behaviour you are developing, so the structure pulls in the same direction as the training instead of quietly undoing it.
The manager is the multiplier you are ignoring
If I had to pick one lever that decides whether leadership development sticks, it would not be the programme design or the facilitator or the framework. It would be the manager of the person being developed. A supportive manager who reinforces the new behaviour in daily work will make an average programme stick. An absent or dismissive manager will make the best programme in the world evaporate. And yet managers are the group most consistently left out of the development they are meant to reinforce. We send the individual on the course and leave their most important influence entirely untouched, then act surprised when nothing holds. It is the most predictable failure in the whole field, and the most avoidable.
So when I redesign development to embed it, I start there. I bring managers into the process, teach them how to coach the specific capabilities being built, and make developing their people an explicit, reviewed part of their own role. This is the same logic behind integrating leadership development into everyday activities: the point is to stop treating development as a place you go and start treating it as a way you work. When the manager becomes the developer, development stops being an event on the calendar and becomes a constant in the culture.
There is a compounding effect here that most organisations never unlock. When managers develop their people well, those people become better managers in turn, who then develop their own people well. The capability replicates down through the organisation on its own, because you built the mechanism that reproduces it rather than the event that delivers it once. That is the whole prize. A programme develops the people who attend it. An embedded system develops the people who will never attend anything, because their managers carry it to them. One is a cost you repeat every year. The other is an asset that appreciates. And once it is running, it is remarkably hard for a competitor to copy, because it is not a programme they can buy but a capability you grew inside your own management layer over time. That is the quiet advantage embedded development builds: not a better-trained cohort, but an organisation that gets better at making leaders every year, on its own, faster than anyone outside it can replicate.
Where embedding connects to leadership capability architecture
Embedding is not a technique you apply to a programme; it is a consequence of building development into your leadership capability architecture. When development is a designed part of how the organisation runs, connected to the work, owned by managers, reinforced by the structure, it stops being fragile. It is also precisely why so many leadership development programs fail to change business performance: they invested in the event and neglected the system that would have carried it.
If you are about to sign off another year of leadership development, ask a different question than which provider or which framework. Ask what happens on the Monday after. Ask who reinforces it, where people practise it, and what in your structure will either hold the new behaviour or quietly undo it. Answer those and you will get development that compounds. Ignore them and you will buy, once again, an event people enjoyed and then forgot, at roughly the price the numbers above describe. The difference between the two outcomes is not budget and it is not the calibre of the provider. It is whether you designed for the Monday. Development that sticks is built, deliberately, into the ordinary machinery of the organisation. Everything else is just a well-reviewed way to spend a training budget.
Embedding connects to two related problems worth reading next: why digital transformation programs fail for the same reason (an event bought instead of a behaviour led), and why leadership capability does not scale with company growth unless you build it deliberately. If you want development that actually holds, the Capability Foundation sprint is built around exactly this, and CapabilityAI keeps developing your leaders in the flow of their real work rather than in a one-off event.