Every organisation with required training has the same conversation once a year, when the completion figure comes in lower than it should be. The conclusion is usually that the content is dull and needs to be livelier.
That diagnosis survives because it is comfortable — it makes the problem a production budget rather than a design decision. But entertaining required training still gets skipped, and the four reasons below explain the completion rate better than tone does.
It is too long for what it contains
A forty-minute module carrying eight minutes of actual content is the most common form of this. People work out the ratio within the first two screens, and from then on they are looking for the skip control rather than reading.
The fix is unglamorous: cut it to its length. If the policy change is four points, the module is four points, and the completion rate goes up because finishing it is no longer a decision. Length is also the thing employees complain about most specifically, which makes it the easiest to verify before you spend anything on production.
It arrives at the wrong time
Required training is often assigned in a batch, on a date chosen by whoever runs the calendar, which lands it in a month-end close or a seasonal peak. The resulting completion figure gets read as disengagement when it is a scheduling collision.
Assigning against the employee rather than the calendar solves most of it — training attached to a start date, a role change, or a renewal falling due arrives when it is relevant and does not compete with the same deadline for everyone at once.
It was not written for the person taking it
One module sent to everybody has to be written for everybody, which means most 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.
Employees read irrelevance quickly and generalise from it: two sections that clearly do not apply to them is usually 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 their team’s outstanding items rather than only the individual seeing their own. Most of the gap closes at that point, because the follow-up comes from the person whose opinion affects the employee’s week.
What to measure instead of completion
Completion says a module was closed. It does not say anything was understood, which is why a 98% completion rate can sit alongside an incident that the training was supposed to prevent.
A short assessment afterwards is worth more, and it is worth more again if the questions are situational rather than definitional. "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 — as SAMA, HRSD, and the Gulf telecom authorities all do in different forms — the answer they want is the record, and the record is worth keeping accurate for its own sake. But the number worth managing internally is whether the training changed what people know.