Why leadership training evaporates, and what makes it stick

The Monday problem

Almost every leadership programme ends on a high. The room is engaged, the insights feel sharp, people leave with a page of commitments they mean to keep. Then Monday arrives. The inbox is full, the standing meetings resume, the pressures that shaped the old behaviour are exactly where they were left. Within a fortnight, most of what felt like a breakthrough has quietly dissolved back into the way things were always done. The learning happened. The change did not.

This is not a failure of the day. It is a failure of what happens after it, and it has a name. The training-and-development field calls it the transfer problem: the gap between what a leader learns and what a leader actually does differently at work. It is the single biggest reason leadership spend underdelivers, and it is almost never the thing programmes are designed to solve.

Insight is not the bottleneck

The instinct, when development does not stick, is to look at the content. Was the model right, was the facilitator good enough, did we cover the wrong things. Usually the content was fine. The leader genuinely understood the idea in the room. They could explain it back, they could see how it applied to their own situation, they meant every word of their commitment to do things differently.

Understanding is not the bottleneck. The bottleneck is everything that sits between the moment of insight and the next time the leader is in a real situation under real pressure, with no facilitator present and every old incentive intact. That gap is where development goes to die, and most programmes treat it as someone else's problem. The session is built with enormous care. The transfer is left to chance.

Decades of work on training transfer point at the same culprits, and none of them are about the quality of the teaching. Learning delivered as a single event, with no spacing, fades fast: the brain consolidates through repetition over time, not through one intense exposure. Learning that the leader's own manager neither notices nor supports has no reinforcement in the environment that matters most. And learning that returns to an unchanged context, the same meetings, the same rewards, the same unspoken rules, meets a system perfectly arranged to produce the old behaviour. The leader is not weak. The design simply asked a fortnight of goodwill to defeat years of conditioning.

Treat development as a process, not an event

The reframe is simple to state and hard to live by. Capability does not transfer because a programme was good. It transfers because the conditions around the programme were built to carry it. An event teaches. A process changes behaviour. Most leadership spend buys the first and hopes for the second.

At CapabilityFX we think about this through the DUAL model, which describes development as a movement that happens inside-out, over time, rather than a download that happens in a room. Discover, Understand, Accept, Lead. The early stages, seeing clearly and making honest sense of what you see, can begin in a workshop. The later stages cannot. Accepting an uncomfortable truth about how you lead, and then actually leading from that new place, only happen through repeated encounters with real situations, reflected on honestly, again and again. That is not an event. It is a practice, and a practice needs a structure around it that a single programme date cannot provide.

This is also where transfer either holds or collapses under pressure. My colleague Dr Eric Albertini has written about how most programmes train the visible, skilled half of a leader and skip the half that determines whether any of it survives a hard moment, in his piece on training the wrong half. The two problems compound. If you only train the surface, and you also leave the transfer to chance, the trained behaviour evaporates exactly when the business most needs it to hold.

The four conditions that make it stick

The research on transfer is unusually consistent about what closes the gap. Four conditions do most of the work, and not one of them is about the content.

Spacing. Behaviour consolidates through repeated exposure spread over time, not through a single immersive hit. A programme that runs as four touchpoints across five months will change more than the same hours compressed into two days, because the leader keeps returning to the work after trying it in the real world. The compression that suits a budget calendar is the enemy of durable change.

Manager involvement. The leader's own manager is the most powerful reinforcement signal in the system, and the most commonly ignored. A manager who asks, after a programme, what the leader is trying to do differently and then notices when they do it, multiplies the effect. A manager who never mentions it tells the leader, accurately, that nothing has actually changed.

Reinforcement in the environment. Behaviour follows what gets noticed and rewarded. If the new behaviour is harder and earns nothing while the old behaviour is easier and still gets praised, the old one wins. Transfer requires the surrounding context to stop punishing the very thing the programme asked for.

Accountable reflection. Not a satisfaction survey. A structured, repeated return to a simple set of questions. What did you try, what happened, what did you avoid, and why. Reflection is where an experience becomes a lesson the leader owns. Without it, experience just accumulates without teaching anything.

Our 4D method is built to hold these four conditions across the arc of an engagement rather than to simulate them in a single sprint. The point is not the method. The point is that transfer is a design choice, and most programmes never make it.

What it looks like in practice

The abstraction gets concrete fast when you watch real leaders return to real desks. These are composites, drawn from patterns I see repeatedly on the commercial side, not identifiable individuals.

The regional operations manager whose insight lasted nine days. A logistics business ran a well-regarded two-day programme on delegation and trust. A regional operations manager left it genuinely changed in his own mind. He had seen, clearly, that he was the bottleneck on every decision, that his team had stopped bringing him solutions because he always rewrote them, and that this was a problem he had created. He meant to change. For the first week he held back, let his supervisors make the call, resisted the urge to correct. Then a delivery failure landed on a Thursday, his own manager asked him directly and sharply why he had not caught it, and within a day he was back to signing off everything personally. Nothing in his environment had changed to support the new behaviour. The first time it cost him, the old behaviour returned, because the old behaviour was the one the system actually rewarded. The programme was fine. There was no spacing to let the new habit consolidate, no conversation with his manager about what he was trying to do, and no reflection structure to help him make sense of the setback rather than simply retreat from it. The insight was real and it lasted nine days.

The HR business partner who built the bridge in. Contrast that with a financial services firm that ran a similar programme but designed the transfer deliberately. An HR business partner there refused to treat the workshop as the deliverable. Before it ran, she briefed every participant's line manager on what the programme would ask of their people and what to watch for. She scheduled three thirty-minute reflection sessions across the four months that followed, each built around the same few questions. She asked managers to name, in their one-to-ones, one thing they had seen the leader do differently. One participant, a finance team lead who habitually absorbed conflict rather than addressing it, practised holding a direct conversation she would previously have avoided, came to a reflection session having done it badly, talked it through, and tried again better the next month. By the fourth month it was no longer an effort. It was how she worked. The content was no better than the logistics firm's. The transfer was built rather than hoped for, and the behaviour held.

What separates the two cases is not the leaders and not the teaching. It is whether anyone designed the bridge between the room and the job. In the first case the bridge was left to the leader's willpower against an unchanged system. In the second it was engineered, and the engineering is what survived contact with Monday.

What HR and L&D directors should change

If this lands as a diagnosis, the good news is that the fixes are mostly about design and sequencing, not about more budget. Three shifts close most of the gap.

Stop buying events; commission processes

Before you approve a programme, ask how the behaviour is meant to survive the week after it ends. If the answer is a strong session and a feedback form, you are buying an event and hoping for transfer. Insist that any engagement includes spacing across months and a reflection structure between touchpoints. The same hours, sequenced differently, do markedly more work.

Make the line manager part of the design

The single cheapest intervention available is briefing managers before a programme and asking them to notice afterwards. It costs almost nothing and it is the strongest reinforcement signal a leader has. A programme that ignores the manager is asking the learning to survive in the one environment that most determines whether it can.

Measure the right thing, later

Reaction scores on the day measure enjoyment, not change. Ask the harder question three and six months out. Is the leader doing the specific thing differently, in the specific situations where it matters. That is the only measure of transfer that means anything, and it is the one most programmes never collect. If you want a structured read on where your leaders actually stand on the dimensions that hold under pressure, our assessments page sets out what we use and why.

This piece sits alongside a deeper argument by Dr Eric Albertini about why most programmes do not build capability in the first place. His is about what you build. This one is about whether what you build ever makes it to the job. Both have to be right for the spend to return anything.

Build the bridge, not just the day

The room is the easy part. Any competent provider can deliver a good day. The work that determines whether your investment returns anything happens in the weeks after, in the unglamorous business of spacing, reinforcement, manager involvement, and honest reflection. That is the bridge between insight and behaviour, and it does not build itself. Left to chance, it does not get built at all, and the learning evaporates on schedule.

Development that sticks is development that was designed to stick. If you want to look at your own leadership spend through that lens, and work out where the transfer is leaking, start a conversation with us. We will begin with what happens on Monday, not with what happens in the room.

The leaders described here are representative composites drawn from patterns we observe in practice, not identifiable individuals.