The Training Treadmill
In one quarter, a distribution company ran its workplace conduct training three times. The same module, the same slides, the same quiz. By the third run, attendance was high, completion was at 100 per cent, and the same three mistakes were still happening on the floor: the same informal remarks, the same blurred boundaries in a team chat, the same complaint that had started the whole thing. The training had been delivered three times and nothing had changed.
This is the training treadmill. You retrain the same thing, the same errors return, and the training itself becomes the reason nobody looks at the cause.
Why the same errors come back
Training changes what people know. It does not, on its own, change what people do. Those are different problems, and the second one is almost always the real one.
When the same error returns after training, it is usually because the error was never a knowledge gap. A supervisor who has been told twice not to make a certain kind of remark does not need to be told a third time. He needs the behaviour to carry a consequence, and he needs the environment around him to stop quietly endorsing it. Training cannot supply either.
In other cases the error returns because the process makes it easy. If the only way to get a report out on time is to skip a step, people will skip the step, no matter how many times you train them not to. The training is fighting the process, and the process wins every time.
And sometimes the error is a symptom of something upstream. The team is understaffed, so the boundary-blurring banter that the training addresses is really a pressure valve for a group that is stretched. Training the behaviour while leaving the pressure in place is like painting a wall that is still moving.
How the treadmill gets built
It is built one well-meaning decision at a time. An error occurs. The response is a training session. The session is delivered, logged and closed. The error recurs. The response is another session, this time with stronger language and a stern email. The cycle repeats, and each turn of the wheel produces a paper trail that looks like action.
- The training is chosen before the cause is known.
- Success is measured by attendance and completion, not by whether the error stopped.
- The same module is reused because it exists and is quick to deploy.
- Nobody asks why the error happened the first time.
- The people who made the error are trained, but the conditions that produced it are left alone.
After a few turns, the treadmill is a habit. The company believes it has addressed the problem, because the paperwork says so, while the floor keeps producing the same result.
Why completion numbers lie
On the treadmill, the metric is completion. Completion is the easiest thing in the world to move. Send a link, set a deadline, chase the stragglers, and the number climbs to 100 per cent. It measures that people saw the content, not that anything changed.
We have sat in rooms where a compliance head proudly reported 100 per cent completion of conduct training, and the same head, twenty minutes later, described an incident that the training was supposed to prevent. The two facts sat side by side and nobody connected them. The number had done its job. It had made the problem look solved.
Real measurement is harder and less flattering. It means counting the incidents, the near misses, the complaints, the early warnings, and watching those numbers over months rather than quarters. If the training worked, the incident count falls. If it does not, the incident count stays where it was and the completion number rises. One of those is the truth.
What actually breaks the cycle
The way off the treadmill is to stop treating every recurring error as a training problem.
- Investigate before you train. Find out why the error happened, in the specific case, before deciding what the response should be. The answer is often a process, a pressure or a person, not a gap in knowledge.
- Change the condition, not just the person. If the process makes the error easy, fix the process. If the pressure makes it likely, remove the pressure.
- Attach a consequence. For deliberate behaviour, training without any consequence is a signal that the behaviour is tolerated. The consequence does not have to be harsh, but it has to be real.
- Measure the outcome, not the attendance. Track the thing you want to stop. If it is not falling, the training is not working, whatever the completion sheet says.
- Retrain only when there is a knowledge gap. If people genuinely do not know how to do something, teach them. If they know and are not doing it, teaching is not the tool.
This is harder than scheduling another session. It requires asking why, and the why is often uncomfortable. It may implicate a manager, a target, a deadline or a leader. That discomfort is exactly why the treadmill is so popular. It offers action without the awkward question.
When training is the right answer
None of this is an argument against training. Training is the right answer when there is a genuine gap between what people know and what they need to know. A new law, a new system, a new process, a skill the team has never had: these are real training problems, and training solves them.
The treadmill is what happens when training is used as the default response to every problem, including the ones it cannot touch. The tell is simple. If you have trained the same thing more than once and the same error is still here, the problem was never the training.
We do not guess. We investigate. When a client tells us they have a training problem, we ask for the incident log first, not the training calendar. The log tells us whether we are dealing with a gap in knowledge or a gap somewhere else entirely, and that difference decides what the response should be.