A 100% course completion rate looks good on a dashboard. It is clean, easy to report, and easy to understand. Everyone who was assigned the training finished it. Job done, all done here, nothing to see anymore…except the job may only be starting.

Completion tells us that an employee reached the end of a learning activity. It doesn’t tell us whether they understood the content, remembered it, changed how they work, or need additional support. That distinction matters because L&D teams are increasingly expected to show more than activity. Leaders want to know whether learning builds capability and whether development connects to the organization’s needs.

Completion itself is not a bad metric – it is simply an incomplete one.

Why completion became the default L&D metric         

Completion rates are everywhere for a practical reason: they are easy to collect. An LMS can usually tell you who enrolled, who started, who finished, and what score they received. These data points help with compliance, administration, and program management. If a certification must be completed by a deadline, completion may be exactly the metric you need.

The problem begins when you use the same metric to answer a different question.

• If the question is “Did employees complete the cybersecurity course?”, completion is appropriate.
• If the question is “Are employees better prepared to recognize and respond to cybersecurity risks?”, completion alone is not enough.

The metric has not failed; we have simply asked it to tell us something it cannot know. Completion measures activity, not necessarily learning, and there is a difference between doing something and developing because of it.

An employee can finish a course quickly while distracted. Another employee can take longer, revisit sections, ask questions, and apply the material immediately. A completion dashboard may treat those two experiences as identical. This is why L&D teams need to distinguish between activity metrics and development metrics.

• Activity metrics tell us what happened inside the learning system: enrollments, attendance, time spent, modules completed, and assessment attempts.
• Development metrics help us understand what may change as a result: knowledge, skill, confidence, behaviour, application, and progress toward a capability.

Both types of data can be valuable. The mistake occurs when we assume one automatically represents the other.

Five questions to ask after a course is completed     

A useful way to move beyond completion is to ask better questions.

1) Did the learner understand the material?

You can explore this through assessments, scenario questions, or practical tasks rather than a simple “next, next, finish” course flow.

 2) Can they remember the important parts later?

A score immediately after training may reflect short-term familiarity. Reinforcement and follow-up activities can give a clearer view of retention.

3) Can they apply what they learned?

Application is where workplace learning becomes useful. Evidence may include a work sample, manager observation, reflection, project outcome, or practical demonstration.

4) Where are the remaining gaps?

Learning should help reveal what still needs attention. That information can guide the next stage of development.

5) What should happen next?

Development rarely ends because one item was completed. The next step may be reinforcement, practice, coaching, advanced learning, or simply more time to apply the skill.

What should L&D measure instead?                

No universal set of perfect L&D metrics exists. The right measures depend on the initiative’s goal.

• If the objective is knowledge, assessments and retention may matter.
• If the objective is skill, practical application and manager feedback may be more useful.
• If the objective is behavior change, teams may need to observe patterns over time.
• If the objective is business performance, connect the learning data carefully to relevant operational measures.

A strong measurement approach usually combines several levels rather than searching for a single magic number.

For example, a leadership program might track participation, assessment results, practice activity, manager feedback, and progress against development goals. A customer-service program might combine training data with quality scores or coaching observations. The key is to start with the outcome you care about and work backward to the evidence that would make sense.

Be careful with vanity metrics   

Learning dashboards can easily become crowded with numbers that look impressive but say very little. Hours of learning, number of courses, average logins, and total enrollments can all be useful operational indicators. More is not always better.

Ten hours of irrelevant learning is not automatically more valuable than one hour of highly targeted development. A large content library does not guarantee that employees can find what they need. High attendance does not guarantee application. Before adding a metric to a dashboard, you should ask yourself: “What decision will this help us make?” If nobody would act differently based on the number, it may be a reporting metric rather than a management metric. That simple question can make L&D reporting much more focused.

How to move from completion reporting to learning visibility   

The transition does not require measuring everything at once. Start with one important program. Define the capability or outcome the program should support. Then identify two or three indicators that would give you a better view than completion alone.

You might add a short follow-up assessment after two weeks. You could ask managers to confirm whether employees are demonstrating a specific behaviour. You could introduce a practical exercise. You might track whether employees continue to engage with reinforcement activities.

Over time, those additional signals can create a richer picture of the learning journey.

The goal is not surveillance. It is visibility: enough information to understand whether the learning experience is helping and where support is needed.

Completion still matters; it just needs context   

There is no reason to remove completion from the dashboard. It remains useful for understanding participation, compliance, and program delivery. The change is to stop treating it as the final answer.

A more mature L&D conversation sounds like this: 92% of the audience completed the program. Assessment results show strong understanding in three areas and a recurring gap in one. We’ve scheduled reinforcement for that topic. Managers are using a practical checklist to support application over the next month. That tells a story.

It moves the conversation from “we delivered training” to “we are managing development.”

At Lerero, this distinction is central to the learning journey. Completion can mark a milestone, but it should not automatically mark the end. The most useful question after someone finishes learning is often the simplest one: what happens next?