Ask any L&D manager what their compliance module is meant to do and they’ll tell you: inform staff, tick the box, log the completion. Ask them what the learner is meant to feel while doing it and you’ll usually get a blank look. That blank look is the entire problem.

Most corporate eLearning treats learners like filing cabinets. Open the drawer, drop in the policy, close it again. Then we act surprised when, a week later, the drawer is empty.
Information transfer isn’t learning
I’ve sat through more storyboard reviews than I can count where the SME pushes to add another paragraph of policy detail to slide 14. The instructional designer pushes back. The SME wins, because the SME owns the risk register. And the module ships with another wall of text that no one will remember by Friday.
Here’s the uncomfortable bit. The research on memory has been clear for decades: emotion is one of the strongest predictors of what gets encoded and recalled. If a learner feels nothing during a module, the content has to fight uphill against everything else competing for their attention that day. Most of the time, it loses.
This isn’t an argument against accuracy or rigour. Compliance content has to be correct. But correctness alone doesn’t make it stick. A WHS module that lists hazards is forgettable. A WHS module that opens with a frontline worker explaining the morning his mate got hurt because nobody spoke up is not.
What “emotional design” actually means in practice
When I talk about emotion in custom eLearning content development, I’m not talking about swelling music and sad faces. I’m talking about specific design choices that give the learner something to care about for the next fifteen minutes.
A few that consistently earn their place:
Characters with actual problems
Not “Sarah from accounts” smiling in a stock photo. A character with a name, a role, a pressure they’re under, and a decision to make. We built a procurement integrity module last year for a state government client where the protagonist was a mid-level officer who’d been quietly accepting tickets to industry events for years. He didn’t think he was doing anything wrong. The learner walked through his week with him and watched the line move. Completion data was fine. The feedback was the interesting part: people said the module made them think about their own inbox.
Stakes that match the workplace
Generic scenarios with generic consequences (“Your manager will be disappointed”) don’t land. Real stakes do. Losing a contract. Hurting a colleague. Being the person on the front page. The stakes don’t have to be catastrophic, but they have to be recognisable. If a frontline retail worker watches a scenario and thinks “yeah, I had that exact customer last Tuesday,” you’ve already won half the battle.
Tension before resolution
This is the bit most modules skip. They give you the rule, then a scenario that demonstrates the rule, then a tick. No tension. The learner is never genuinely uncertain. Compare that to a branching scenario where the first “right” answer turns out to have a downstream consequence you didn’t see coming. That moment of “oh” is where the learning actually happens.
Why most teams don’t build it this way
It’s not because L&D teams don’t know better. It’s because emotional design is harder, slower, and politically riskier inside an organisation.
Harder because writing a believable scenario takes a different skill set than summarising a policy. Slower because it requires real conversations with the people who do the job, not just the people who wrote the policy. Riskier because legal and risk teams get nervous when a module shows a character making a bad decision, even when that’s the entire point.
I’ve watched a perfectly good scenario get watered down in review because someone worried that depicting the wrong choice might “send the wrong message.” It doesn’t. Sanitising the scenario sends the wrong message. It tells the learner this isn’t a real workplace and the module isn’t really about them.
The teams that do this well push back, with evidence. They show stakeholder groups two versions: the safe one and the honest one. Nine times out of ten, the honest one wins the room. People know what they recognise.
Where to start if your current library is flat
You don’t need to rebuild everything. A few practical moves go a long way:
- Pick the one module that matters most and rewrite the opening two minutes. Replace the learning objectives slide with a scene. A voice. A problem. Get the learner to lean in before you teach them anything.
- Audit your scenarios for tension. If the “right” answer is obvious from the question, it’s not a scenario, it’s a quiz dressed up. Add a plausible distractor that a real person would actually choose.
- Talk to the workforce, not just the policy owner. Ten minutes with a frontline worker will give you more usable scenario detail than ten emails with a senior manager.
- Resist the urge to over-explain at the end. Let the consequence land. Trust the learner to get it.
The point of all this
Custom eLearning content development is one of the few places in a corporate training program where you can actually shape how someone feels about their work for fifteen or twenty minutes at a time. That’s a rare opportunity. Spending it on bullet points is a waste of money and a waste of the learner’s attention.
If your last module reviewed well, completed well, and was forgotten in a fortnight, the gap probably isn’t the content. It’s the absence of anything for the learner to feel. Worth thinking about before the next storyboard goes to review.
Have a module in your library that you suspect isn’t landing? Pull it up, watch the first three minutes, and ask yourself what the learner is meant to feel. If you can’t answer, that’s where the next version starts.

