Mandatory training: forty minutes of clicking next to prove you were there

The points below about compliance e-learning are ordered by how much difference they make, not by how often they get repeated.

The module is evidence, not education

Regulators and insurers frequently expect organisations to demonstrate that staff were trained on a given topic, and a completion record is that demonstration. The record has to exist, be dated and cover everyone, which is a documentation problem rather than a teaching problem. A system optimised for producing records will produce excellent records, and nothing in that optimisation rewards anybody learning anything.

That is why modules are uniform across roles, repeated annually regardless of need, and assessed with questions that cannot be failed permanently. The design is entirely rational once you know what it is for, which is worth understanding before getting angry at the person who assigned it.

Forced pacing is a presence check

Modules that disable the next button for a fixed period are measuring elapsed time, which is the only proxy for attention the system can observe. The measurable effect is that people open the module in a second window and do something else, which the system records as engagement.

Three clicks later, disabling navigation also prevents skipping to material you already know, which penalises exactly the people who least need the training. Allowing a test-out route, where a passing score exempts you from the content, solves this and is comparatively rare. Where it exists it usually indicates a training team that has thought about the problem rather than purchased a solution to it.

Annual modules fight against how memory works

Learning research consistently finds that spaced repetition and retrieval practice produce far better retention than a single long exposure. A forty-minute module once a year is close to the worst available schedule for retaining anything by the following January. Short, frequent interventions delivered near the moment of relevance perform substantially better and are harder to administer.

Because the compliance requirement is annual, the schedule is set by the audit calendar rather than by the evidence on learning. Organisations that genuinely want behaviour change usually run something else alongside the mandatory module and do not call it training.

Phishing simulations are the interesting exception

Simulated phishing exercises measure behaviour rather than completion, which makes them one of the few workplace training tools with a real outcome measure. They also generate resentment when used punitively, and several high-profile exercises have caused significant damage to trust.

The evidence on long-term effectiveness is mixed, with click rates generally falling and the durability of that change less clear. Design matters enormously, since an exercise that punishes reporting or that impersonates something distressing achieves the opposite of its aim. The version that works tends to be frequent, low-stakes and paired with an easy reporting button rather than with a disciplinary record.

Why nobody fixes it

The cost of a bad module is diffuse and lands on employees, while the cost of an incomplete record lands on a named person during an audit. That asymmetry makes over-assignment the safe choice, so modules accumulate and are rarely retired.

Off-the-shelf content is cheaper than tailored content and is written to cover every jurisdiction, which is why it is generic and long. Tailoring it requires subject expertise and legal review, which costs more than the entire compliance budget in many organisations. The equilibrium is therefore predictable, and complaining about it individually has approximately no effect.

Making the hour less wasted

Read the summary or the transcript where one exists, since it usually contains the entire content in a fraction of the time. Take the assessment first if the system permits it, because passing it is often the only outcome that matters.

Note the one or two items that are genuinely specific to your organisation, as those are the parts not copied from a template. Report a badly targeted module through whatever channel exists, since assignment lists are occasionally reviewed and never volunteered for review. And accept that the forty minutes is a tax on employment, which is at least a more honest description than professional development.

Everything above, in order of what to do first

1. The module is evidence, not education. Regulators and insurers frequently expect organisations to demonstrate that staff were trained on a given topic, and a completion record is that demonstration.
2. Forced pacing is a presence check. Modules that disable the next button for a fixed period are measuring elapsed time, which is the only proxy for attention the system can observe.
3. Annual modules fight against how memory works. Learning research consistently finds that spaced repetition and retrieval practice produce far better retention than a single long exposure.
4. Phishing simulations are the interesting exception. Simulated phishing exercises measure behaviour rather than completion, which makes them one of the few workplace training tools with a real outcome measure.
5. Why nobody fixes it. The cost of a bad module is diffuse and lands on employees, while the cost of an incomplete record lands on a named person during an audit.
6. Making the hour less wasted. Read the summary or the transcript where one exists, since it usually contains the entire content in a fraction of the time.

The takeaway

It is a record, not a lesson. Find the transcript and get on with your day.

The fix is usually trivial, which is the most annoying part.