Every LMS I have ever touched has a dashboard, and the biggest number on that dashboard is almost always completion. Ninety-four percent complete. A wall of green checkmarks. It looks like success. It gets screenshotted and dropped into a report, and everyone nods.
I want to make the case that this number, the one we lean on most, is quietly telling us almost nothing.
Completion measures that someone reached the end of a course. That is all it measures. It does not tell you they learned anything, that they can do anything new, or that the training changed a single thing about how they work. We have built an entire reporting habit around a number that was never designed to answer the question we actually care about.
What Completion Actually Tells You
Let me be fair to it. Completion is not useless. It tells you that a learner was assigned a course and clicked through to the end. For compliance records, where you sometimes just need proof that a course was delivered, that has a real purpose.
But notice how narrow that is. Completion confirms attendance. It is the training equivalent of counting how many people walked into a lecture hall, not how many walked out understanding the lecture.
A learner can complete a course while skimming every screen, guessing through the quiz, and retaining nothing. The checkmark looks identical whether they mastered the material or clicked next for twenty minutes with the tab half ignored. When the same green mark covers both, the mark has stopped meaning anything useful.
Why We Cling to It Anyway
So why do we keep putting it at the center? Because it is easy, and because it is comforting.
- It is automatic. The LMS counts it for you. No design work, no extra effort. The number is just there.
- It looks like accountability. A high completion rate feels like proof the training function is doing its job, even when it proves nothing about impact.
- It is a clean number. Ninety-four percent is tidy and defensible. “Did behavior change?” is messy and harder to put in a slide.
I understand the pull. When someone asks whether the training worked, having a confident number to point at is a relief. But a confident number that measures the wrong thing is worse than admitting the real answer is harder to find.
What We Should Be Measuring Instead
Here is the shift I am arguing for. Stop asking “did they finish” and start asking “what can they now do that they could not before.” That one change reframes everything.
A few directions that actually get at learning:
- Performance change. Did the thing the training targeted actually move? Fewer errors, faster handling, better decisions on the job. This is the real prize, and it lives outside the LMS.
- Demonstrated capability. Not a recall quiz, but a task. Can the learner do the thing, in a scenario or in their real work, rather than recognize the right answer from four options.
- Confidence and application. Are people actually using what they learned, and do they feel equipped to? A quiet follow-up weeks later tells you more than any completion bar.
None of these are as easy to pull as a completion percentage. That is exactly the point. The easy number and the meaningful number are not the same, and we have been settling for the easy one.
Designing for Proof, Not Just Progress
This is where it connects back to how we build. If you want to measure capability, you have to design for it from the start. You cannot bolt real measurement onto a course that was only ever built to be clicked through.
That means building in moments where the learner has to actually perform. A realistic scenario with a consequence. A decision that reveals whether they understood. A task that looks like the job, not like a test. When those are in the course by design, the evidence of learning comes out naturally, and you are no longer stuck pointing at a completion bar and hoping.
It also means being honest with stakeholders earlier. If someone wants proof the training worked, the time to agree on what proof looks like is before the build, not after. Decide together what success means in terms of behavior, and the whole project gets pointed at something real.
A Harder Number Worth Chasing
I am not saying throw out completion tracking. Keep it where it belongs, as a record of delivery. Just stop letting it stand in for success. It was never built to carry that weight.
The honest truth is that measuring real learning is harder than measuring completion. It takes more design, more follow-up, and more willingness to sit with a messy answer instead of a clean one. But our field exists to change what people can do, not to generate green checkmarks. If our main number only measures the checkmarks, we have quietly accepted a lower bar than the one our work deserves.
So the next time a dashboard hands you a completion rate, treat it as the start of a question, not the answer to one. Ask what actually changed. That is the number that matters, even when it is the harder one to find.
If you want courses built to show real evidence of learning, with meaningful performance measures designed in from the start, that is exactly the kind of work I love to take on. You can always reach out for help with your next custom eLearning project.
