Your completion rate is 96 percent. Your people opened the module in one tab, worked in another, and clicked next until the certificate appeared. Everyone involved knows this. The dashboard does not.
There is a ritual that happens in almost every large organization, several times a year, and almost nobody defends it out loud. A mandatory module lands in the inbox. It is forty minutes long. It has a narrator with an unhurried voice, a scenario involving fictional colleagues named Priya and Mark, and a quiz you can pass by elimination without watching a single slide. People finish it while eating lunch. The completion is logged. The report goes up. Everybody moves on.
We should be honest about what this is. It is not learning. It is documentation. The organization needed a record that the training happened, and it got one. Whether anyone can now do anything differently was never actually the thing being measured.
This matters more than it used to. When the content was fire safety and expense policy, the gap between completion and capability was mostly harmless. Now the same delivery model is being pointed at things the business genuinely depends on: data handling, AI tool usage, customer conversations, safety in a warehouse running at double the seasonal volume. The ritual has not changed. The stakes have.
It is tempting to blame L&D for this, which is both unfair and unhelpful. Nobody sat in a room and chose theatre. It is what you get when three reasonable pressures meet.
The measure was available, so it became the goal. Completion is easy to count, easy to chart and easy to defend in an audit. Capability is none of those things. Given a metric that is cheap and a metric that is true, organizations reliably optimize the cheap one.
Coverage got confused with reach. Sending a module to nine thousand people feels like reaching nine thousand people. It is not the same thing, and the difference is invisible in every report the system produces.
Nobody is incentivized to find out. If you measure only completions, the programme always looks like a success. Asking a harder question can only make your numbers worse, so the harder question tends not to get asked.
If your training would produce the same completion rate whether or not anyone watched it, you are not measuring learning. You are measuring compliance with a clicking task.
The fix is not more engaging content, and it is definitely not gamifying the same forty minutes. It is changing what the system asks for.
Make it short enough to be honest
A forty minute module signals that your time does not matter, and people respond accordingly. Five focused minutes on the one thing this role actually has to get right will be watched. The long version is often long because nobody was willing to decide what mattered most.
Ask for a decision, not a click
A quiz you can pass by elimination proves nothing. A short scenario where the person has to choose and then sees why that choice worked or failed is the difference between recognition and judgment. It also takes less time than the module it replaces.
Deliver it where the work is
Frontline and distributed teams do not have a quiet hour to sit with a course. On a phone, between tasks, in the language they actually work in, is not a compromise on quality. It is the only version that gets genuine attention rather than a tab left open.
Report the change, not the click
Pick one thing the training was supposed to move: incident reports, escalation quality, first-week productivity, the error that keeps recurring. If it moved, you have a programme. If nothing moved but completions hit 96 percent, you have a receipt.
Take your most recent mandatory module. Two weeks after everyone completed it, ask ten people at random to name one thing they now do differently because of it. Not what the module covered. What they changed.
Most organizations that try this stop after six or seven conversations, because the answer is already clear. That is not a failure of the people. It is a design result, and it can be designed differently. The organizations getting this right are not spending more on learning. They are spending it on fewer minutes that actually land.
Courseplay is built for the version that lands: short, role-specific learning delivered on the devices a distributed frontline workforce actually uses, scenarios that ask for a decision instead of a click, and reporting that connects what changed in the person to what changed in the business.
If your last training report led with a completion rate, the more useful number is sitting one question behind it.
Want to save time? Pick a slot that works for you:
Book a TimeTell us a bit about your organization and we’ll set up a personalized demo.