Compliance training that sticks: from box-ticking to applying

Why box-ticking does not work

The goal of compliance training is twofold: people must know it and do it, and the organisation must be able to show that they have learned it. In practice the second requirement becomes the first. A module emerges that mainly produces evidence, not behaviour. The outcome: a fully completed training and a forgotten rule.

The solution is not less evidence, but more learning, in the same learning journey.

Short pieces, more often

Divide the material into short learning moments of a few minutes, with a question per idea. Spread them over the year. That fits what we know about memory: spacing and retrieval work better than one hour once a year. See spaced repetition and microlearning with swipeslides.

Make people decide, not just read

Rules are only understood when you have to apply them in a situation where they clash with rush, interest or loyalty. Use scenarios: a branching storyline in which the learner chooses and sees the consequences, or a scenario game in which a team handles an incident. For cybersecurity there are examples such as CEO fraud and a press call. See scenario games for decisions.

A conversation with a CrewMate can help with situations in which you have to say no or report something.

The evidence you need

For the organisation, demonstrability counts. CoVince gives a certificate as a PDF per learning journey with a public verification page, and a certificate collection per person. Progress is visible per learner and per step. If you have an LMS, a learning journey can run in it through SCORM, xAPI or LTI 1.3 with grade passback, so your existing records stay correct.

Staying honest: a certificate proves that someone has gone through and answered something, not that they always behave that way. That is why it belongs next to behaviour signals. See measuring learning.

Applying it at work

A rule that is not on the shop floor is forgotten. Hang short refreshers on the work processes where the rule applies: a workflow that shows a short slide at the moment it is relevant. Use the learning journey’s chat for questions and a CrewMate for "am I allowed to do this?". See learning in the flow of work.

An example: privacy in daily work

Instead of an annual module on privacy rules: four short learning moments, spread over the year, each around one situation. A colleague asks by email for a customer list. A customer calls and asks for another person’s data. A laptop is left behind on the train. Each learning moment consists of a situation, a choice, the consequence of that choice and a short explanation of the rule.

Whoever completes all four receives a certificate with a verification page. The team leader sees in the progress who is done and which situation often went wrong, and discusses it in the team meeting. It is less work for the employee each time, and worth more to the organisation.

Being able to report safely

Compliance only works if people dare to report what goes wrong. Design the learning journey so that this becomes normal. Show in scenarios that reporting is the right choice, even when it is uncomfortable. Use a CrewMate conversation to practise how to raise something with a colleague or manager. And let the debrief of a scenario game be about the system and not about who was to blame.

See practising with an AI role-play for practising such conversations.

Different roles, different learning journeys

Not everyone needs the same rules. An employee at the front desk has different risks than someone in finance or IT. A learning journey with branches can adapt the route to the role: whoever processes customer data gets different situations than whoever only uses internal documents. That way nobody spends time on what does not apply to them.

That yields two things: more engagement, because the examples are recognisable, and better data, because you see per role where it goes wrong. A workflow can assign the right learning journey to the right group. See learning in the flow of work.

An annual cycle instead of an annual module

One possible set-up. Quarter 1: a short learning moment and a scenario at the start of the year. Quarter 2: a repetition with a new case and an open question. Quarter 3: a team session with a scenario game, followed by a debrief. Quarter 4: a short test and the certificate. In between, short refreshers can be assigned for events or changes.

That way you work on the same theme all year, instead of ticking it off once a year. See spaced repetition for the rhythm.

Checklist for a compliance learning journey

• One behaviour per learning moment, not one topic per module.
• At least one decision per topic, with consequences.
• Multilingual where the team is.
• Certificate with verification page and progress per employee.
• A place for questions, and someone who answers them.
• A report per group to see which topic is weak.