Why Great Programs Fade and How to Make Them Stick

Ever left a leadership program feeling genuinely different? Not just informed but changed. Clearer about what matters, more intentional about how you show up, carrying real commitments that you fully intend to keep.

And then the week after returns. The inbox, the pressure, the team who wasn't in the room with you, the pace picks up, dissolving the space that had catalysed your renewed perspective. Slowly, almost without noticing, the person you were in that room starts to recede. Insights begin to blur and the commitments that felt so solid begin to soften. The momentum that you do manage to hold on to then faces what can feel like an insurmountable task: reshaping a system that didn't change while you were gone. Within a few weeks, it can feel as though the program happened to a slightly different version of you, despite the excitement and dedication that you returned with.

This experience is so common it deserves a name. We call it re-entry disappointment, and understanding why it happens is the first step toward designing programs that don't produce it.

You changed, but the system didn't. Now what?

The honest answer is the system usually wins.

Not because people lack commitment or the learning wasn't real. Because systems are patient. They don't argue with you when you return with new intentions. They simply continue operating according to their existing logic, their rhythms, their expectations, their unwritten rules about "how things are done here". Over time, without structural support for new behaviour, those expectations quietly reassert themselves. The growth made inside the program gets absorbed back into the patterns that existed before it.

This is not a failure of the individual. It is a design problem. Programs that invest everything in the quality of the in-room experience and nothing in the architecture of what happens after it are only doing half the job. Creating energy and insight in the room is, comparatively, quite easy. Designing a program whose impact is still visible six months later is a different and considerably harder problem, and it is the one that actually matters.

Where learning actually happens

Research from the Centre for Creative Leadership offers a useful reframe here. Their findings suggest that across different forms of development, roughly 70% of meaningful learning comes from on-the-job experience, from trying new things in role and reflecting deliberately on what worked and what didn't. A further 20% comes from learning with and through others, coaches, peers, and managers who create the conditions for reflection and growth. Formal training accounts for the remaining 10%.

This is not an argument against formal programs. It is an argument about what formal programs are actually for. Their primary job is to equip people for the learning that happens back in the work itself, and then to stay present while that learning unfolds.

Which shifts the question from "how do we design a better program?" to "how do we design a program that makes learning in the flow of work more likely?"

What that looks like in practice

The answer lies in building the habit of small, deliberate experiments embedded in the work week that already exists. Not new initiatives, not additional effort, but conscious choices to do something already planned in a slightly different way. Identify a focus, design the experiment, and then reflect on what changed as a result. What was different? What impact did it have? What would you do differently next time?

This is the thinking behind our Workplace PRAC, a four-phase cycle of Practice, Reflect, Adapt, and Consolidate that sits at the heart of how we design programs. At the close of each workshop, leaders identify a specific outcome they want to achieve and choose one or two behaviours they will experiment with to get there. They share that plan with a small peer group, a learning pod off our to six people, who provide support and accountability between sessions. The emphasis is on doing what was already planned, differently. Then they go and do it, not in a simulated environment, but in the real work that was already in their calendar.

Following each instance of practice, leaders reflect critically on the outcome they achieved, what worked, what didn't, and why. Based on what they have learned, they refine their approach and continue. Finally, they bring their insights back to their learning pod in a facilitated group coaching session, consolidating what worked and determining the behaviours they want to carry into their next cycle.

The power of this approach is not in any single experiment. It is in the frequency and the intention. Learning becomes less of an event and more of a practice, something that compounds quietly over time rather than fading between program modules.

The partnership that makes it stick

None of this works without honesty, and honesty requires a particular kind of relationship between participants and the people supporting their development. One where it is safe to name what is getting in the way when you return to the system. One where the program doesn't pretend that re-entry is straight forward. One where facilitators stay present and accountable beyond the room, and where participants stay engaged and honest about the distance between their intentions and their actions.

The contract between them has to be explicit about this from the beginning. Facilitators who design for the room but not for re-entry are only doing half the job. Participants who engage fully in the room but disengage from the work when they return are too.

Running a program that feels good at the time is achievable. Running one that produces sticky, lasting impact is the genuinely difficult part, and it is only possible when both sides take that challenge seriously together.

A final reflection

The moments for learning are already in the calendar. They are in the difficult conversation that needs to happen, the meeting where something different could be tried, the decision that could be made more deliberately. What determines whether those moments become development is not the quality of the program that preceded them. It is the quality of attention brought to them, and the quality of the system built to support that attention when the energy of the room is long gone.