How to Build Compliance Training People Don't Resent

Compliance training is the only category of learning where the designer's goal and the learner's goal are openly different. The organisation needs evidence that people were trained. The learner wants to be finished. Pretending otherwise produces the click-through-and-forget courses everyone complains about.

You can do considerably better without pretending the tension doesn't exist.

Start with what the evidence actually needs to show

Before designing anything, get clear on what an auditor or regulator would need to see. Usually some combination of:

• Who completed the training, and when.
• That they were presented with specific content.
• That they demonstrated understanding, not just attendance.
• That they acknowledged an obligation, explicitly.
• A retained record with dates, for a defined period.

Everything you build should serve one of those. If a section serves none of them and doesn't help the learner do their job, cut it — it's there because someone was nervous, not because it's required.

Separate 'must know' from 'good to know'

The single biggest cause of bloated compliance training is legal and subject-matter reviewers adding material defensively. The result is a 45-minute course where 10 minutes is mandatory and 35 is context nobody retains.

Split it deliberately: the course covers what people must know and do. Everything else becomes a reference document they can consult — which is more useful anyway, because that's how people actually use policy content.

Use scenarios, not definitions

Nobody breaches a policy because they couldn't recite its definition. They breach it because they didn't recognise the situation.

So build recognition, not recall. Instead of 'What is a conflict of interest?', ask: 'A supplier you've dealt with for years offers you tickets to a match. What do you do?' The second question tests the thing that actually matters.

Make the acknowledgement deliberate

A tick box at the end of a course that someone scrolled past is weak evidence. A well-designed attestation is a distinct, deliberate step: the obligation restated plainly, a checkbox, and a separate confirm action. Two actions, not one.

This matters legally and practically — it's harder to claim you didn't understand something you actively confirmed on its own screen.

Assess in a way that means something

Knowledge checks that can be passed by elimination prove nothing. Three things improve them:

• Plausible wrong answers — distractors that represent real misconceptions, not obvious nonsense.
• Scenario framing rather than definition recall.
• Locked progression on critical items, so learners can't skip past the questions that matter.

Respect people's time, visibly

Tell learners at the start how long it will take, and be accurate. State what they'll be asked to confirm. Nothing generates more resentment than a course that claims 15 minutes and takes 40.

Plan the refresher differently

An annual refresher that repeats the original course teaches nothing and wastes everyone's time. Refreshers should be shorter, focus on what changed, and lean on assessment rather than content — test first, teach only what people got wrong.

The honest summary

Good compliance training is short, scenario-based, deliberately acknowledged, and honest about its own purpose. It will still not be the highlight of anyone's week. But it can stop being the thing people mock in the break room, and it can produce evidence that actually holds up.