Most mandatory modules open the same way: a wall of policy, a definition of terms, a paragraph about why this matters to the organisation. Somewhere around screen four, a real example appears. By then the learner has already decided this is a box to tick, and they're clicking Next as fast as the player allows.
The content isn't usually the problem. The sequence is.
Lead with the moment, not the rule
Flip it. Open every section with a short, recognisable scenario from the learner's actual day — a near-miss, an awkward decision, a moment they've lived. Only once they feel the problem do you introduce the governance principle as the answer. Now the rule has somewhere to land, because it's solving a problem the learner already recognises as theirs.
This isn't a trick to make dry content palatable. It mirrors how expertise actually forms: we remember principles attached to situations, not principles in isolation.
Respect the learner's week
Keep sections short and modular. Mandatory onboarding is competing with a hundred other first-week tasks, and a 90-minute monolith guarantees skim-and-forget. Five focused minutes that stick beats an hour that doesn't — and a modular structure lets people complete it in the gaps they actually have.
Then layer the depth. Give everyone a clear, scenario-led path, with the full policy detail available on demand for those who need it. Completeness and clarity stop fighting each other the moment you stop forcing every learner through every clause.
- Open each section with a lived scenario, not a definition.
- Introduce the policy as the resolution to that scenario.
- Keep modules short; make depth optional, not mandatory.
- Measure engagement with xAPI, not just pass/fail.
Measure what actually happened
Finally, measure engagement, not just completion. A 100% pass rate tells you people reached the final quiz, not that anything changed. With xAPI you can see which sections held attention and which got abandoned — and improve the module instead of guessing. Compliance training that nobody remembers isn't compliance; it's a liability with a certificate attached.