The Missing Link in Every Development Program

I have observed this pattern consistently across Singapore, Hong Kong, and Australia. A well-designed program runs. Participants are engaged. The facilitator is excellent. The content is relevant. By the final session, people leave motivated, with new frameworks, new language, and genuine intention to do things differently.

Three weeks later, almost nothing has changed.

Not because the program failed. Because the system around the program failed.

And at the centre of that system failure, almost every time, is the same missing link — the direct manager.

What Managers Are Typically Asked to Do

In most organisations, a manager’s involvement in a development program looks like this: they nominate their direct report to attend. They receive a completion notification when it is over. That is it.

No conversation before the program about what the participant should focus on. No check-in during the program about what they are trying. No structured discussion afterwards about what they observed or what support they would offer.

The manager is the most influential person in that participant’s working life — and they have been made a bystander.

What Actually Happens When Managers Are Not Involved

The participant returns to work. They are motivated. They have new ideas. Then the emails pile up. The quarter-end targets land. The team has a crisis. The old habits are faster, more comfortable, and nobody is reinforcing the new ones.

Within three weeks, the learning fades. Not because the participant did not want to change. Because the environment around them did not change at all.

James Kirkpatrick calls the structures that prevent this “Required Drivers” — the reinforcement, encouragement, and accountability systems that make on-the-job application stick. In my experience across APAC, Required Drivers are almost always absent.

The L&D team designed a great program. Nobody designed the environment the participant returned to.

The Five Manager Behaviours That Change Outcomes

The research on this is clear. Managers do not need to become coaches or learning experts. They need to do five specific things.

1. Before the program — Have a focused conversation

Ask what the participant wants to focus on and why it matters to their role. Ten minutes. It signals that development matters and creates intention before day one.

2. During the program — Check in once

Ask how it is going. What is landing? What are you trying? This keeps learning alive between sessions rather than confined to the classroom.

3. After the program — Create one application moment

Do not wait for new behaviour to happen organically. Deliberately create a situation where the participant can apply what they learned in real work.

4. When you see it — Name it specifically

“I noticed you handled that differently than you would have six months ago.” Specific recognition reinforces far more powerfully than general praise.

5. When you do not see it — Ask about it

Not as a performance conversation. As a development conversation. “What got in the way this week?” This signals that application is expected, not optional.

None of this requires significant time. It requires intention — and a belief that developing people is part of the manager’s job, not a task delegated entirely to HR and the L&D team.

Why This Is Harder in Asia Pacific

There is a cultural dimension to this that is rarely spoken about directly.

In Singapore, Hong Kong, and Australia — particularly in sales-driven and high-performance cultures — the majority of managers reached their role because they were exceptional individual contributors. They were promoted because of what they could do, not because of how well they could develop others.

They lead by doing. They lead by example. They lead by being the most capable person in the room.

The idea that their role now includes actively reinforcing a direct report’s learning behaviour — sitting with someone after a program, noticing their behaviour, having a structured development conversation — is genuinely foreign to how they think about management.

This is not a motivation problem. It is a role clarity problem. Nobody has told these managers that development reinforcement is their responsibility. So they do not do it. Not out of negligence — out of genuine unawareness that it was ever expected.

What It Looks Like When It Works

The managers who change outcomes are not necessarily the most talented or the most experienced. They share one quality: they treat development as a recurring conversation, not a one-time event.

They check in after programs — not to audit, but to understand. They create space in team meetings for people to share what they are working on. They reference the development program weeks after it has ended. They connect business challenges back to the capabilities their team is building.

Their direct reports do not experience development as something that happens away from work. They experience it as something woven into how their team operates.

The result is not just better application of learning. It is a team culture where growth is expected, modelled, and sustained.

The Question That Changes Everything

Most organisations evaluate their L&D investment by asking: was the program good? The more important question is: what did managers do in the 90 days after the program ended?

That question is almost never asked. And until it is — until manager involvement in development is treated as a non-negotiable rather than a nice-to-have — organisations will keep investing in well-designed programs and wondering why the needle does not move.

When was the last time your managers had a structured conversation with a direct report about their development — not their performance, their development? What would change if that happened consistently, across every team, every quarter?