Two people attend the same two day programme. Same facilitator, same materials, same cohort. Three months later one of them has changed how she runs her team meetings and the other cannot remember much beyond the model on day one. The difference was not motivation, seniority or prior knowledge. It was that one of them had a manager who asked about it on the Monday.
Most L and D teams know this. Very few programme designs act on it. The design effort goes into content, facilitation and platform, all of which are within the team’s control, while the largest single influence on whether anything sticks sits with a person who never attended and was never asked to do anything.
Why the manager matters more than the programme
Behaviour change after training depends on what happens in the weeks afterwards, in the environment where the behaviour has to occur. The line manager controls most of that environment. They control whether there is time to practise, whether an early clumsy attempt is received well or badly, whether the new approach conflicts with what actually gets rewarded, and whether the topic is ever mentioned again.
Consider what a participant faces on their first day back. Their inbox has three days of accumulated work. The new approach is slower than their existing habit, because all new approaches are slower before they are faster. Nobody has adjusted their targets. If their manager does not signal that using the new approach matters, the participant makes an entirely rational choice to do the thing they already know how to do quickly.
The learner did not fail. The design assumed a supportive environment that nobody had built.
Why the usual manager involvement does not work
Most organisations have already tried to involve managers, and it usually takes one of three forms that predictably underdeliver.
The pre-programme briefing email. Sent to managers a week before, explaining the programme’s objectives. It is read by a minority and remembered by almost none. It asks for awareness rather than action.
The manager conversation guide. A two page document suggesting questions to ask after the programme. Well designed, genuinely useful, and it competes for attention with everything else in a manager’s week. Optional resources are used by the managers who were already going to do it.
Managers attending the same programme. Better, and expensive. It also assumes the manager’s problem is not knowing the content, when the more common problem is not making room for it.
These fail for the same reason. They treat manager support as an information problem when it is a workload and accountability problem. Managers are not unaware that development matters. They are being measured on other things.
Five design changes that shift the odds
These are ordered roughly by how little political capital they require.
Give the manager a task, not a briefing. One specific action with a deadline. Before the programme, a fifteen minute conversation with the participant about which situation they will apply this to. Not a request to be supportive. A named thing to do, at a named time.
Make the participant’s application plan visible to the manager by default. If the participant leaves with a commitment, send it to the manager rather than to the participant alone. This costs nothing and changes the first conversation back, because the manager now knows what was promised.
Schedule the follow-up conversation before the programme runs. A diary invitation for three weeks after, created during enrolment. Booked time survives. Intentions do not. This single change tends to outperform any amount of post-programme content.
Ask what the participant should stop doing. New behaviour needs time that already belongs to something. Requiring the manager to name what comes off the plate turns a vague endorsement into a real resource decision, and it exposes early whether the organisation actually wants this change.
Report uptake by manager, not only by participant. If your data shows completion by learner, nobody is accountable for the environment. Showing which teams applied the learning changes who is having the conversation about it. Use this carefully, since it can turn punitive quickly, but visibility alone often does the work.
What this looked like in practice
A financial services organisation was running a well regarded coaching skills programme with consistently high satisfaction scores and very little observable change in how managers ran one-to-ones. The L and D team had already tried adding follow-up modules and a digital nudge campaign. Both had a brief effect that decayed within about six weeks.
They changed the enrolment process rather than the programme. Enrolment now required two things: a short note from the participant’s manager naming one situation where the skills would be used, and a diary slot booked for a twenty minute conversation four weeks after the programme.
Enrolment dropped by roughly a third in the first cohort. That was uncomfortable and it was informative. The people who did not enrol were largely those whose managers would not spend twenty minutes on it, which is a reasonable prediction of who was not going to apply it anyway.
Among those who did attend, application at three months rose substantially and, more usefully, the L and D team could finally see where the blockages were. Two departments showed almost no application, which turned out to have nothing to do with the programme and everything to do with a workload problem those managers had been raising for a year.
The honest caveat: total participant numbers fell. The team had to make the argument that fewer people changing behaviour was worth more than more people attending, which took a conversation with their sponsor about what the function was for.
Common traps
Asking managers to be supportive. Support is not a task. Nobody can put it in a diary or tell whether they have done it. Ask for a specific action at a specific time.
Blaming managers. Most are running short-staffed teams against targets that do not mention development. If the system rewards output and asks for capability building in its spare time, you have a system problem and no amount of manager communication will fix it.
Adding manager involvement without removing anything. If you ask for three new touchpoints per participant and a manager has nine reports, you have asked for a considerable amount of unbudgeted time. Ask for less and make it non-optional rather than more and optional.
Measuring satisfaction and calling it evidence. Participants routinely rate programmes highly and change nothing. Satisfaction tells you whether the experience was good. It tells you almost nothing about transfer.
Reflection questions
For L and D teams, ideally alongside a sponsor rather than alone.
- For your most recent programme, what exactly were managers asked to do, and how many did it?
- What does a participant have to stop doing to make room for the new behaviour, and who agreed to that?
- If application is low in a particular team, would you currently be able to see it?
- Are your managers rewarded for anything that relates to developing their people, or only for output?
- Would your sponsor accept fewer participants in exchange for more behaviour change, and have you actually asked?
You can improve a programme a great deal without touching the manager relationship, and most teams have already extracted most of that gain. The remaining variance sits with someone who never attended. Design for that person, or accept that a good part of your budget is producing satisfied participants and unchanged behaviour.
