A completion rate tells you who finished, not who learned

My claim is that a completion rate is a floor and not a result. It tells you how many people reached the end of the material. It does not tell you what they took from it, what they do differently or whether the course was worth the hours. A course can have a high completion rate and teach nothing, as compliance training that passes and teaches nothing describes.

I still care about completion. The gap between live and recorded formats is real, and I have written about it in why recorded training does not get finished, where I cite the ranges reported by course platforms. Someone who drops out at the third module cannot use the fifth. So I treat completion as the first test and never the last.

Because the software gives it to you for free. A learning platform records starts, finishes and time on page without anyone asking. The number arrives in a dashboard, and dashboards invite reports. A metric that needs no extra work gets used, whether or not it answers the question.

It also makes the training function look busy and in control. A rising completion rate is easy to present to a sponsor. A change in how managers run their meetings is harder to collect, so it stays out of the report. I understand the pull, and I think it leads people to optimize the wrong thing.

Courses get designed to be finished, not to teach. Modules get shorter, quizzes get easier and the content shrinks to what a person can click through during a lunch break. The completion rate rises and the learning falls. Why nobody finishes security awareness training looks at the opposite failure, but the root is the same: the design does not respect the person doing the course.

A target on a number changes the behavior of the people who produce it. If you ask for 100 percent completion and nothing else, you will get people who finish quickly, and you will not find out whether they learned.

I look at three things next to completion: a behavior, a question and a decision.

• One behavior that should be different, chosen before the session is built, and observed by someone other than the trainer.
• One question learners answer at the end, written to test judgment and not recall, such as “what would you do in this case?”
• One decision the report will inform, such as whether to repeat the course, change it or retire it.

How to measure whether training worked goes through how to choose the behavior and when to check it. The point here is the order: decide what you will do with the information, then measure what informs that decision.

Make the session worth finishing, and make finishing mean something. Live, interactive formats help with the first part because people are part of a group and expected to take part. Recorded content can help with the second if it includes a task that produces evidence.

Compare the formats by what each does best, not by one number. Virtual instructor-led training vs eLearning sets out the differences. I use recorded material for reference and live sessions for practice, then count completion for the live part and behavior for the whole.

A sponsor who receives a completion rate can ask better questions than the number invites. Here are the ones I hope to hear.

• What did people do differently afterward, and who saw it?
• Which people stopped before the end, and what did they say about why?
• What would we change if we ran it again?
• What decision does this report help us make?

These questions turn the report into a conversation. They also protect the training team, because a team that reports only completion can be held to a number it did not choose. A team that reports behavior and decisions can defend the work on its merits.

A small organization has fewer people and fewer tools, which makes the problem easier to see. With twenty people in a course, you can ask each participant one question and look at one behavior without a dashboard.

Here is a hypothetical case, built only to show the logic. A team of thirty finishes a recorded module on handling customer complaints. Completion is high. A month later, the manager listens to a sample of calls and counts how many open with the agreed sentence. The count is low. The module was finished, and the behavior did not change. A live practice session follows, with the same sentence rehearsed aloud, and the count is rechecked. The change in the count is the evidence. The completion rate was not going to show it.

For a small team, this is a few hours of work and it replaces guesswork. A learning and development strategy for under 150 employees describes how to fit this kind of check into a modest budget.

It matters most when the completion is the requirement. Some training has a legal deadline, and a missed date is a problem regardless of what people learned. For those programs, completion is a compliance number, and I treat it as one.

Even there, I do not stop at the number. I plan the dates, the make-ups and the follow-up, as described in how to get required training finished on schedule, and then I use the live session to teach something people can use. The deadline gets met, and the session is worth the hour. Doing both is harder than doing either alone, and it is the work I think is worth doing.

Put completion first, since it is the floor, then report the behavior, then the decision. Say plainly what the completion number does not show.

A report might read: “Most registered learners finished. Of those who finished, supervisors reported the new check-in habit in about the number of teams we predicted. We will repeat the live session and retire the recorded module.” That is a hypothetical example, written to show the order. It tells a sponsor what to do next, which a completion rate alone does not.

My advice: keep the completion number, move it down the page and put a behavior beside it. You will get a better course and a better conversation with whoever pays for it.

Want a second read on your numbers?

Bring your current training report to a free consult. In twenty minutes we pick the one behavior to put beside completion.