Ask most teams how their training is doing and you'll get a completion rate. 94% finished. Sounds great — except completion measures attendance, not ability. It tells you people showed up. It tells you nothing about whether the work got better.
You don't need a research department to measure what actually matters. You need to pick the right small number of signals and look at them honestly.
Start from the behavior, then work outward
Before building anything, name the change: "After this, people will ___." That sentence is also your measurement plan. If you can't finish it, no amount of analytics will save you — and if you can, the metric usually names itself.
A useful way to think about levels of evidence, from weakest to strongest:
- Did they finish? Completion. Necessary to track, but the floor — not the goal.
- Did they get it? A short, scenario-based check that asks them to apply, not recognize. Far more telling than a recall quiz.
- Did they do it? An observable change on the job — fewer errors, faster ramp, more consistent decisions. This is the one that matters.
- Did it move the number the business cares about? The outcome the training was funded to improve. The hardest to attribute, and the most persuasive when you can.
Completion measures attendance. The question is whether the work got better.
You can measure impact cheaply
Most teams skip impact measurement because they imagine a formal study. You don't need one. A baseline taken before launch and the same measure a few weeks after is enough to see real movement. Ask managers one specific question about observed behavior. Pull the one operational metric that should shift if the training worked. Small, consistent signals beat a perfect study you never run.
Report the story, not the dashboard
"92% of new managers ran their first review conversation without escalation, up from 60%" is a sentence a stakeholder remembers and repeats. "94% completion" is not. Measurement isn't just for proving value after the fact — it's how you find out what to fix next.