Organizations with required training tend to have the same conversation once a year, when the completion figure comes in lower than expected. The usual conclusion is that the content is dull and needs to be livelier.
That diagnosis is comfortable, because it turns a design decision into a production budget. Entertaining required training still gets skipped, though, and the four reasons below often explain the completion rate better than tone does.
It is too long for what it contains
Example: a forty-minute module carrying eight minutes of actual content. People work out the ratio within the first few screens and start looking for the skip control.
The fix is unglamorous: cut it to its length. If the policy change is four points, the module is four points, and finishing it stops being a decision. Length is also easy to check before you spend anything on production. Ask a few people who took last year’s version how long it felt.
It arrives at the wrong time
Required training is often assigned in a batch, on a date chosen by whoever runs the calendar, which can land it in a month-end close or a seasonal peak. The low completion figure that follows gets read as disengagement when it is a scheduling collision.
Assigning against each employee’s own dates removes much of the collision. Training attached to a start date, a role change, or a renewal falling due arrives when it is relevant, and it does not put everyone on the same deadline at once.
It was not written for the person taking it
One module sent to everybody has to be written for everybody, which means much of it does not apply to any given reader. A branch teller and a treasury analyst do not face the same risks, and a module covering both teaches each of them a lot about the other one’s job.
People notice irrelevance quickly and generalize from it: two sections that clearly do not apply to them can be enough to convince someone that the rest does not either. Targeting by role costs more to build once and considerably less to deliver every year after.
Nothing happens if it is not done
This is the uncomfortable one. Where completion has no consequence and non-completion has no consequence, the training is optional in practice regardless of what the assignment says, and employees are correct to treat it that way.
The consequence does not have to be punitive, and mostly should not be. It usually just has to be visible: the manager sees the team’s outstanding items, and each person still sees their own. The follow-up then comes from the person whose opinion affects the employee’s week, which is often enough to close much of the gap.
What to measure beyond completion
Completion says a module was closed. It does not say anything was understood. Example: a 98% completion rate can sit alongside an incident that the training was supposed to prevent.
A short assessment afterwards tells you more, especially if the questions are situational. "Which of these is the correct procedure" tells you something; "what is the definition of the policy" tells you the person can read.
Where a regulator asks what training people completed, the answer they want is the record, and the record is worth keeping accurate for its own sake. The number worth managing internally is whether the training changed what people know.