A manager emails: 'We need a two-day course on delegation.' Sixteen people, two days, a venue booked.
The request describes a solution. It says nothing about the problem. Delegation may be failing because managers don't trust their teams' capability, because handoffs have no agreed checkpoints, because workload is allocated by whoever shouts loudest, or because delegation is quietly punished when something goes wrong.
Each of those has a different fix, and only one of them is a course.
Taking the order feels responsive. It is actually the moment L&D stops being useful. A short diagnostic conversation — what happens now, what should happen, what makes it hard — costs an hour and routinely reframes the ask.
For trainers, it changes what you teach. For instructional designers, it changes whether you design a course at all. For L&D managers, it means defending a queue you can explain. For HR leaders, it means capability conversations that begin with evidence, not requests.
The question worth asking: how many items on your learning plan are solutions looking for a problem?
Comments 0
Sign in to like, save or comment.
No comments yet. Start the discussion.