Manager Enablement Is Your Real L&D Gap

Every large organisation I work with has a version of the same problem. The learning is fine. The manager enablement around it does not exist, and that is where the value leaks out.

You can see it in the numbers if you look in the right place. Completion is high. Feedback scores are respectable. Six months later, nothing observable has changed in how the work gets done. The instinct is to blame the content, so the next cycle commissions better content, and the result is identical.

However, the content was rarely the constraint. The manager was.

Why does manager enablement decide whether learning sticks?

Because the manager controls every condition that determines whether a new behaviour survives contact with the job.

They decide what gets prioritised in the week after the course. They decide whether someone gets to practise something badly before they do it well. They decide what gets noticed, what gets corrected, and what quietly gets dropped because the quarter is busy. Therefore no learning intervention outranks those decisions.

When a manager does not know what their team just learned, cannot recognise the behaviour when it appears, and has no reason to protect the time it takes to develop, the learning has nowhere to go. It was not wasted in the classroom. It was stranded afterwards.

What actually happens in the week after a course?

This is the part that rarely gets designed, and it decides everything.

Someone returns to a full inbox and a delivery deadline. They have a new model in their head and no immediate reason to use it. The old way is faster, known, and safe. Within about ten working days the new approach has either been used and reinforced, or it has not, and after that it is gone.

In fact, almost no programme designs for those ten days. We design the eight hours in the room and treat the following fortnight as somebody else's responsibility. Then we measure at ninety days and report disappointing results.

The single highest-return change I have seen a large organisation make was not to a course. It was giving every manager three questions to ask their team member within a week of attending, and making it visible whether that conversation happened.

Why do managers get skipped so consistently?

Three reasons, and none of them are that L&D has not thought of it.

First, managers are not the sponsor. The programme is bought for the learner population, the business case is written about the learner population, and the manager sits outside the scope that got funded.

Second, manager time is the most contested resource in the organisation. Asking for ninety minutes of it requires a stronger case than asking for a day of a learner's time, and that case is rarely made.

Third, and specifically, it is genuinely harder work. Building a course is a defined project with a deliverable. Building manager enablement is a change of habit across a dispersed population with no completion certificate at the end. It does not photograph well in a board pack.

Is manager enablement just more training for managers?

No, and treating it as another course is the most common way it fails.

Managers do not usually need to be taught the content their team learned. They need three much smaller things: to know what was covered, to be able to recognise it being done well or badly, and to have a reason to bring it up.

That is a communication and process problem far more than a training problem. A one-page summary, two example behaviours, and a calendar prompt will outperform a manager development module almost every time, because it fits inside the job rather than competing with it.

The moment manager enablement becomes a programme, it acquires a completion metric, and the completion metric replaces the outcome. You end up training managers about supporting learning instead of supporting learning.

How do you build it without launching another programme?

Start from what the manager already does, and attach to it.

Every manager already holds one-to-ones. That is your delivery mechanism, and it costs nothing to use. The task is to give them something concrete and short enough that using it is easier than not using it.

Concretely, that means naming the two or three behaviours the programme is meant to produce, in the language the manager actually uses rather than the language of the learning objectives. It means giving them one question per behaviour. And it means being honest that you are asking for about ten minutes, not for a coaching commitment they will not make.

Ultimately, make it visible. Not as a compliance report, but so the organisation can see where the conversations are happening and where they are not. The gap between those two is usually the same gap you see in your outcome data three months later, which is a far more useful diagnostic than another feedback survey.

Three things that shift the odds

Design the fortnight, not just the day. Whatever you are building, spend some of the design effort on what happens in the ten working days afterwards. That period decides your outcome and currently gets no design attention at all. Manager enablement means giving language, not learning. Two or three behaviours, described in words they would use, with one question each. Resist the pull to turn it into a module. The value is in its smallness. Make the conversation visible. You cannot mandate a good coaching conversation, but you can make it obvious whether any conversation happened. That visibility does more than any amount of encouragement, and it gives you a leading indicator months before your outcome measures report anything.

None of this is expensive. Manager enablement fails in most organisations not because it is hard to fund, but because it never had an owner, a scope, or a place in the plan. It is the cheapest unclaimed improvement in most L&D functions, and it sits one conversation away from work you are already paying for.