At the end of a leadership programme, participants are often asked to write down what they will do differently. The exercise is usually sincere. People identify conversations they need to have, decisions they should approach differently and habits they want to change. They may share their commitments with a colleague. There is energy in the room and a genuine sense of possibility.

A few months later, the notebook is in a drawer. Urgent work has taken over. The commitments are less clear and very little in the organisation appears to have changed. It is tempting to conclude that participants lacked discipline. Sometimes they did. But the explanation is rarely quite that simple.

Something happened between insight and application. Understanding what happened in that space is central to building capability.

Intention is only the beginning

A good learning experience can change how somebody sees a problem. It can provide language for something they have sensed but not previously articulated. It can challenge settled assumptions or give a person the confidence to attempt something new.

These are meaningful outcomes. But they are not yet changed performance.

Between a new intention and sustained behaviour lies ordinary organisational life. Workload, hierarchy, incentives, team expectations and established routines all shape what happens next.

A manager may return from a programme determined to delegate more effectively. Yet their own leader continues to demand immediate answers from them personally. The team has had little opportunity to develop. Deadlines leave no space for supported practice. A mistake made by a team member is likely to be interpreted as a failure of supervision. The manager may remember the learning perfectly. But their environment still favours control.

Learning transfer is therefore not principally a problem of memory. It is often a problem of workplace design.

Learning must attach itself to something real

Generic development can be intellectually stimulating and practically weak. Participants may agree with everything being discussed without recognising where it applies in their work. They leave with broad intentions such as “communicate more effectively”, “think strategically” or “empower the team”. These are admirable desires. They are not yet application plans.

Learning becomes more consequential when it connects to a live responsibility, difficult decision, strategic priority or recurring problem.

A participant should be able to answer a straightforward question: where will I use this? The answer should be reasonably specific.

A leader is not merely going to “give better feedback”. They are preparing for a conversation with an experienced colleague whose performance has changed. A team is not simply going to “think more strategically”. It is reconsidering which markets, clients or activities deserve attention. A manager is not vaguely going to “delegate more”. They are identifying responsibility that another person can take, what authority will accompany it and how support will be provided.

When no opportunity for application is visible, transfer is fragile from the outset.

People need the chance to practise

Organisations sometimes invest in capabilities that the work does not allow people to exercise. They teach strategic thinking to people who are rarely included in strategic conversations. They develop coaching skills among managers whose spans of control and workloads make meaningful one-to-one discussion almost impossible. They encourage judgement while requiring most significant decisions to be escalated.

The promise of development and the design of work contradict one another.

Capability requires use. This does not mean people should be placed recklessly into situations for which they are unprepared. It means that development should include progressively demanding opportunities to exercise the capability in real conditions.

Someone learning to influence across an institution needs a cross-functional issue on which to work. A future leader needs more than a succession label. They need experience of decisions, stakeholders and consequences beyond their present role.

Formal learning can prepare people for these experiences. It cannot replace them.

Somebody at work must notice

What managers pay attention to tends to acquire organisational importance.

If a participant returns from a substantial programme and nobody asks about it again, the signal is clear. Attendance mattered. Application did not.

The manager does not need to become a substitute facilitator. Nor should they police learning through a mechanical series of forms and compliance checks. A more useful role is that of an accountability partner.

Before the development experience, manager and participant can discuss why the capability matters and where it may be applied. During the programme, they can maintain a connection with live work. Afterwards, they can review what the participant is trying, what they are noticing and what may be preventing progress.

The conversation need not be elaborate. Questions such as these can be enough:

• What are you thinking differently about?
• Where could you use this in the next few weeks?
• What happened when you tried?
• What are you finding difficult?
• Is there anything I am doing that makes this harder?
• What support or authority do you need?

The final question is particularly important. Organisations often focus on the participant’s responsibility while leaving managerial obstacles unexamined.

New capability may initially look awkward

There is another reason people return to familiar habits. Using a new capability can temporarily make performance feel slower and less fluent.

A manager accustomed to solving problems personally may find effective delegation uncertain and time-consuming at first. A team adopting a more rigorous decision process may initially take longer to reach a conclusion. Someone learning to give direct feedback may handle the first conversation imperfectly.

Established behaviours have the advantage of familiarity, even when they are not especially effective. If the organisation allows no room for imperfect practice, people will retreat to behaviours in which they already feel competent.

This does not mean lowering standards or accepting poor performance indefinitely. It means recognising that development has a practice stage. People need the opportunity to try, receive feedback, make adjustments and try again. A culture that demands immediate fluency while claiming to value learning is likely to produce caution rather than growth.

Feedback must be close enough to help

An annual performance conversation is too distant from the moment in which a new capability is being used. Feedback has greater value when it sits close to application.

That may take the form of a short conversation with a manager, reflection with a peer, a coaching discussion or an after-action review following an important decision. A cohort might meet to discuss where application succeeded and where organisational reality proved more difficult than the programme suggested.

The form matters less than the existence of a learning loop. Without feedback, the participant may not know whether the new behaviour is having the intended effect. They may persist with an unhelpful interpretation, abandon a promising practice too quickly or assume that nobody else considers the development important.

Reflection also matters. Experience alone does not guarantee learning. People can repeat the same approach for years without examining why it produces the results it does. Capability grows when experience is combined with attention.

Let the work become part of the development

Some of the strongest development designs use the workplace not as the destination after learning, but as part of the learning process itself.

A strategy programme can help participants address a real strategic choice. A feedback module can lead into actual conversations, followed by structured reflection. Systems thinking can be applied to an organisational blockage that has resisted conventional solutions. AI leadership development can include a governed workplace experiment rather than stopping with demonstrations of tools. A governance programme can change how information, challenge or decisions move through an actual forum.

This changes the relationship between learning and performance. Participants no longer have to translate a generic experience into their context entirely by themselves. The work provides the case, the opportunity for practice and at least some of the evidence of progress.

There remains a place for external cases, conceptual frameworks and the intellectual distance that a well-designed programme can provide. The point is not to collapse learning into everyday work. It is to create dynamic movement between the two.

Measure what moves

Organisations often measure the part of learning that is easiest to observe. They know who attended, who completed and how participants rated the programme. These are sensible measures, but they sit near the beginning of the story.

A more serious evaluation asks a sequence of more nuanced questions. Did people engage with the experience? Did their understanding deepen? Did they apply anything differently? Was the change sustained? Did it make a credible contribution to better work?

That final question requires care. Institutional performance is influenced by many factors, and it is often difficult to draw a neat causal line from one programme to one business result. Organisations should resist inflated claims about return on investment where the evidence does not justify them.

But complexity is not a reason to stop at satisfaction scores.

The standard should be credible evidence rather than spurious precision. Changed behaviours, improved decisions, stronger succession, better management conversations and greater consistency in an important process may all provide useful evidence of capability growth.

The measures should reflect the capability the organisation intended to build.

The organisation is part of the intervention

When development fails to produce change, organisations commonly review the facilitator, the content and the participant. Sometimes they should. Programmes vary in quality and not every participant engages seriously.

They should also review the workplace. Did the learning connect to a real priority? Was there an opportunity to practise? Did the manager pay attention? Was feedback available? Did the participant have permission to act differently? Did the wider organisation reinforce or punish the intended behaviour? What has been built around the learner matters.

If the answer is very little, limited transfer should not surprise us.

An action plan at the end of a programme may be helpful, but it is not a transfer system. Capability grows when insight is connected to experience, practice, feedback, managerial attention and an environment that makes different performance possible.

Learning may begin in a programme. Whether it becomes capability is decided largely by what happens next.