The quiet decay
Ask at any industrial organisation when the safety material was last updated, and the answer is rarely a date. It is a story: there was a project, three or four years ago, and a few things have changed since.
That “few things” is usually considerable. An installation extended. A supplier swapped. A procedure tightened after an incident. New regulation worked into the SOP but not into the module that refers to it.
Nobody took a decision about that. There was never a moment when somebody said: we will let this go stale. It happened because every individual change was too small to make a project of, and together they were too big to knock off quickly.
Why nobody updates it
The reason is economic, not organisational.
With traditional production of training material, the cost of a change is nearly as high as building new. The source file sits with an outside party, in a format you cannot edit yourself. There has to be an order, a schedule, a review, a new export, a new upload into the LMS. To change three screens.
So everybody does the same sum: this change is too small to be worth that. That sum is correct per change. It is not correct after twelve changes.
On top of that, the cost of outdated material is invisible until something goes wrong. A module teaching an outdated procedure throws no error. People simply pass it, and learn something that is no longer true.
The shadow procedure
What emerges is a second reality.
The official procedure sits in the system. The real procedure sits in the heads of the people who work with it daily, and gets passed on verbally to new colleagues. Usually that second version is better than the first. It has, after all, been updated by practice.
Until the moment it matters. At an audit, where it turns out nobody works to the documented process. During an incident, where the investigation asks why there was a deviation. Or on the departure of the colleague who was the only one who knew why that one step was in there.
This is also why “more training” is rarely the answer. The problem is not that people learned too little. It is that what they learned no longer matches what is in the system.
Designing for maintenance
The way out sits in the design, not in discipline. Four choices make the difference.
Modular instead of linear. Material built out of separate components can be replaced component by component. A course produced as a single whole has to be redone as a whole.
One source for several formats. When the manual, the e-learning and the work instruction on the tablet all come out of the same material, a change is one action. When they come from three files at three suppliers, it is three, and one always gets forgotten.
Ownership of the source files. If you cannot edit the source, you depend on somebody else for every comma. Arrange that contractually, even when you outsource the updating itself.
A fixed review moment. Not “update when needed”, because that does not happen. Twice a year, an hour per module, tied to a meeting that already exists.
Where to start
Not with everything at once. Start with the inventory nobody ever makes: what material exists, when was it last changed, and which procedures have been amended since?
That list is usually uncomfortable and always clarifying. In practically every organisation a small part of the material turns out to carry the greatest risk, the modules about the operations where things can really go wrong, and they have gone untouched for exactly as long as the rest.
Start there. Not by remaking everything, but by making the part that matters maintainable. The rest follows on its own once updating is no longer a project.
Maintainability is one of the four questions you ask at the start of any training programme. The other three are in the guide on setting up or renewing a corporate academy. What it means for the production side is under AI-assisted development.