01 — The situation
Training scattered everywhere.
Our client is a group with many business units. Each ran its own training — some in person, some as files sent by email, and some existing only in the head of whoever had been there longest.
What they asked for wasn't another online classroom. It was one official place, so that training across the group had the same shape, could be followed from anywhere, and left a record.
02 — The problem
What kills these systems is rarely the technology.
A learning platform is easy to build and easy to kill. What kills it is almost always the same thing: nobody fills it.
If adding a class requires the technical team, the system stops being fed within three months. All that remains is the original material, and people stop opening it.
The second problem: different business units assess people differently. Forcing one scheme onto all of them sends some units quietly back to their old way of working.
Learning systems don't die from missing features. They die when they stop being fed.
03 — What we did
Making it run without us.
Four decisions, all pointing the same way: reduce the dependence on the technical team.
- 01
Classes and material created by their own team
Adding a class, uploading material, ordering the lessons — all done through the console, without a line of code. This was the decisive one: the moment adding material has to go through us, the system stops growing.
- 02
Assessment configurable per unit
The assessment scheme isn't fixed. Each business unit sets its own components, so nobody has to change how they work merely to fit the system.
- 03
Built light enough for a phone
Many people take training between tasks, not at a desk. Pages are kept light so they open on a poor connection, and resume from where they stopped if the connection drops.
- 04
Reports written for whoever signs them
The people who need reports aren't the instructors — they're HR and unit heads. So reports arrive in a form you can act on: who has finished, who hasn't, which unit is behind. Not a pile of raw numbers.
04 — The outcome
Adopted as the official training channel.
It became the official home of internal training across the group, and the material kept growing — run by the client's own team.
When the build was finished the system was handed over together with its documentation. That was the point from the start.
05 — What keeps it standing
What we handed over wasn't only the software.
An internal system only its builder can change stops growing the day the contract ends. So what we handed over included the client team's ability to run it themselves.
The measure of a system like this isn't how many features it has, but how long it keeps being fed after we leave.