Head of Content at Promote
Managers usually don't reinforce training because L&D keeps asking for something they were never set up to give, a request that shows up late, generic, and disconnected from what the manager is actually accountable for. The fix isn't a better-worded ask; it's designing the manager's role into the program from the start, not requesting it once the program is already built.
Every L&D team has sent some version of this email: "Please remind your team to complete the module by Friday," or "Take 15 minutes this week to talk through what they learned." And every L&D team has watched that email land, get skimmed, and quietly go nowhere.
The easy conclusion is that managers don't care enough about development. The more useful conclusion is that L&D keeps asking for something managers were never set up to give.
Most requests for manager involvement arrive late, generic, and disconnected from what the manager is actually responsible for that quarter, so even a manager who values development has no natural way to act on them.
Think about how most manager involvement gets requested. A program is designed, built, and scheduled. Somewhere near the end of that process, someone adds a slide, an email template, or a "manager's guide" that asks managers to reinforce what their team just learned. The ask shows up late, it shows up generic, and it shows up disconnected from anything the manager is actually responsible for that quarter.
None of that is a reflection of whether managers value learning. It's a reflection of how the request was designed, or rather, how it wasn't.
Three things tend to be true at once, and together they explain most of the gap:
When manager involvement keeps falling flat, both sides quietly lower their expectations of each other, L&D starts working around managers instead of through them, and managers start skimming L&D's requests instead of acting on them, which makes every future ask easier to ignore.
When the ask keeps failing, both sides quietly adjust their expectations, and not for the better. L&D starts assuming managers can't be relied on and works around them instead of through them. Managers start treating L&D's requests as one more email to skim rather than act on. Neither side is wrong about what they're observing, they're just both responding rationally to a broken exchange, and every repetition makes the next ask a little easier to ignore.
The real cost shows up beyond the training itself. When employees sense that their manager doesn't take development seriously, that reads as a signal about the organization as a whole, not just about one course that didn't stick.
Treat manager time as a constraint to design around, not a favor to request: decide the manager's role before the program is built, keep the ask small and repeatable, and tie it to something the manager already owns rather than to L&D's own metrics.
The shift that actually works is small to describe and harder to implement: treat manager time as a constraint to design around, not a favor to request. The same way a good program design accounts for a limited budget or a distributed workforce, it should account for the reality of how much attention a manager can realistically give, and build around that, rather than hoping for more.
In practice, that looks like three changes:
Seen this way, the manager-involvement gap isn't a motivation problem. It's a performance barrier, something standing between a learning intervention and the behavior it's supposed to produce, and it deserves to be identified and managed like any other barrier, not wished away with a better-worded email. It's the same reasoning behind starting a learning journey by naming an invested stakeholder before the program begins, rather than hoping for manager buy-in after the fact.
Managers were never the obstacle. The ask was.
A few things to consider before trying the platform:
…there’s a Demo guide within each module, explaining all the nifty features of the Promote Platform! You can find it under resources on the right hand side of the screen.
