Six months ago you ran the training. You remember it going well. People asked good questions, the room was engaged, someone even said it was the most useful session they had been to in a while. You walked out feeling like a manager who had invested in their team.
Last week you watched someone on that team do the exact thing the training was supposed to fix.
Not out of carelessness. They were trying. They simply did not have the procedure anymore. It had been in their head in November and it was gone by May, and somewhere in between, with no single dramatic moment, “we trained the team on this” quietly stopped being true.
If that has happened to you, here is the first thing to be clear about. It is not a sign that you manage badly, and it is not a sign that your team is weak. It is the most ordinary thing in the world. The reason it keeps surprising us is that nobody ever explained how memory actually behaves.
In the 1880s a researcher named Hermann Ebbinghaus ran a long, patient experiment on himself, memorizing material and testing how much he could recall as time passed. He found something that has held up in every decade since. Without reinforcement, we lose new information fast, and the steepest part of the loss happens right at the start. A day after you learn something, a good portion is already gone. A week later, most of it.
This is the forgetting curve, and it is not a defect in your team. It is a property of being human. Your strongest performer and your newest hire are both subject to it. The training did not fail. It did exactly what one exposure does, which is fade.
Most of how we run workplace training pretends the curve is not there. We treat training as an event with a date on it. It gets scheduled, delivered, attended, ticked off, and then we act as though the knowledge is now installed, the way software is installed. But people are not hard drives. Knowledge in a person is not stored, it is maintained, and the moment the maintenance stops, it begins to drain.
It gets harder in the kind of year most of us are having. When the work itself keeps changing, when the tools and processes and priorities will not hold still, you are not fighting one forgetting curve. You are fighting a fresh one every time something changes. The procedure you trained in November may not even be the right procedure in May. So your team is losing the old thing and being asked to absorb the new thing at the same time, continuously, and the gap between “we covered it” and “they can do it” widens the faster the ground moves.
That gap is where the near-misses live. The missed step, the customer handled wrong, the thing nobody quite remembered. Not because anyone was careless, but because capability drained quietly and no one was watching the level.
So what do you actually do. Not another training day. I have run plenty of those, including a few I was genuinely proud of, and the curve laughs at all of them.
You change the shape of the maintenance. Stop thinking of training as an event and start thinking of it as a rate, the way you would think about topping up anything that leaks. That is abstract, so here is the concrete version, and it is smaller than you expect.
Pick one procedure. Just one. The one that costs you most when someone gets it wrong. Not the whole onboarding binder. One procedure.
Now have your team retrieve it. Not re-read it, not sit through it again. Retrieve it: actually pull it back out of memory and use it, briefly, out loud or on paper, on a regular cadence. Once a week is enough. Five minutes. It can be a question in a standup, a quick “walk me through it” with one person, a small scenario. The mechanism that matters is the act of recall, because retrieving a memory is what tells the brain this one is worth keeping. A re-read does not send that signal. A retrieval does.
It will feel almost too small to count as a management intervention. Good. The training day felt big and did not work. The weekly five-minute retrieval feels like nothing, and it bends the curve. That is the trade, and once you have seen it you cannot unsee it.
There is a second effect, and it is the one that quietly makes you a better manager. When people retrieve a procedure regularly, the gaps show up early, while they are still cheap to fix, instead of showing up during the incident. You start to see who is soft on what, before the world sees it. A manager who knows where their team is weak ahead of time, and can shore it up calmly, is doing the actual work of leadership.
None of this is a hack and none of it is fast magic. It is maintenance. It is unglamorous, and done steadily it is almost invisible. It is also the whole difference between a team that looks trained and a team that is. Pick the one procedure. Start the weekly rep. Keep it small and smooth, and let it run.