The Lab

94% completion. The training worked. Did it? Or did 94% of your workforce learn to click Next fast enough to avoid a follow-up email from HR?

Completion rate is the most commonly reported learning metric in corporate L&D. It is also the least meaningful. It measures a behaviour — opening and finishing a module — not the behaviour you actually care about, which is doing something differently at work.

Here's how completion rates get inflated without anyone lying:

• Slides are skippable. Learners click through at maximum speed.
• Assessments use recognition-based multiple choice. Learners guess. They pass.
• Time-on-task is not tracked — or is tracked but not acted on.
• The "completion" triggers off the final slide being reached, not assessed performance.

I've audited compliance programmes with 90%+ completion rates where the average time on the highest-stakes module was under 3 minutes — for a module designed to take 12. The data was there the whole time. Nobody looked at it.

What to measure instead

• Time-on-task per module — is it plausible? 2 minutes for a 12-minute module?
• Assessment question analysis — which questions have suspiciously high pass rates?
• Pre/post behaviour data — did incidents change? Did conversion rates move?
• Spaced retrieval scores — where does knowledge drop off?

Start tracking one better metric this quarter. Decide in advance what a "good" number looks like, and what you'll do if you see a bad one. That discipline — measure, interpret, act — is what separates a learning function from a content factory.

The most valuable thing I can tell a client is: you don't need training. Half the performance problems I see are process problems, tool problems, or incentive problems dressed up as knowledge gaps.

When a manager says "my team needs training on X," they're usually right that there's a problem. They're often wrong about the cause.

The five real causes of underperformance

• Information: Do people know what's expected? Do they get clear, timely feedback when they do it wrong?
• Resources: Do they have the tools, time, and support to perform correctly?
• Incentives: Is correct performance rewarded? Is incorrect performance penalised?
• Knowledge: Do they actually lack the knowledge or skill to perform? (This is the only cause where training helps.)
• Motivation: Do they want to perform correctly? If not, why not?

Genuine knowledge and skill gaps account for maybe 20–30% of performance problems. The rest are environmental. Training can't fix a bad process. It can't fix a tool that doesn't work.

What to do when training isn't the answer

Say so. Clearly. With evidence. Clients remember the consultant who told them the truth. They trust them for the next project.

A scenario where the wrong answer is obviously wrong teaches nothing. Real decisions are hard because all the options are defensible. If your learner can guess the right answer without reading it, your scenario is decoration.

The three signs your scenario is broken

1. The wrong answers are obviously wrong. If one option is "document everything carefully" and another is "ignore the problem and go to lunch," you haven't built a decision.

2. Failure leads to a "Try Again" button. In real life, mistakes have consequences that unfold over time. Your scenario should do the same.

3. The scenario is generic. Effective scenarios use specific, named characters in recognisable situations. The more specific and real, the more transfer.

What makes a scenario actually work

• Authentic tension — all choices are defensible. The learner has to actually think.
• Consequence fidelity — outcomes match what would actually happen, not an idealised version.
• Reflective debrief — not "here's the right answer" but "here's what different choices set in motion."

Every project I take on starts with the same five questions. Not a needs analysis template. Five questions that separate a training problem from a performance problem.