The most expensive sentence in corporate technology is: we already trained them on that.
The licences are paid for, the course was delivered, the certificates were issued, and nothing about how anyone works has changed. The organisation concludes the software was a bad investment. Usually the training was.
Diagnose before you design
Generic curricula fail because they answer a question nobody asked. Before writing a single slide we assess capability against the tasks each role is actually expected to perform.
That produces a gap map per department — which is a fundamentally different document from a course outline. It says: these people can do this, cannot do that, and the work requires both.
The syllabus is then built from the gaps. Content that addresses something the team already does gets cut, however standard it is in the vendor's courseware.
Teach on the live environment
Training delivered on a sandbox that looks nothing like production transfers poorly, because the learner has to translate everything twice: once from sandbox to production, and again from demonstration to their own task.
Where at all possible we train on the organisation's real configuration, with real records where they can be used safely, against the workflows the team runs daily.
This is more work to prepare and dramatically more effective. The learner leaves having completed their actual job in the actual system.
Every session produces something finished
The design rule: nobody leaves a session without having completed a real task.
Not watched a demonstration. Not taken notes. Completed something — a record created, a report generated, a workflow configured, a document produced to standard.
This constrains session length and cohort size more than most organisations expect. Four hours with twelve people produces more completed work than a full day with forty.
Cohort size is a quality decision
Large cohorts are cheaper per head and worse in absolute terms. In a group of forty, the confident participants ask the questions and the quiet ones leave with the same gaps they arrived with.
We cap technical cohorts at twelve and hands-on tool training at fifteen, with one facilitator and, above eight learners, an assistant who circulates.
If budget forces larger numbers, split into more cohorts rather than filling one. The total delivery hours are similar; the outcome is not.
Measure before and after, with the same instrument
A post-training satisfaction survey tells you whether people enjoyed it. That is worth knowing and worth almost nothing.
Measure capability twice with the same assessment: before the programme and at the end. Score against defined tasks, not self-reported confidence.
Then measure again at ninety days without announcing it as an assessment. The drop-off between day one and day ninety is the number that tells you whether the training stuck, and it is the number almost nobody collects.
The 30 and 90 day clinics
Capability decays without use, and the first month after training is when habits either form or dissolve.
We schedule two refresher clinics as standard: thirty days out, when the initial problems have surfaced, and ninety days out, when the organisation can see what has genuinely changed.
These are short, they are driven by the questions participants bring, and they cost a fraction of the original delivery. They are also where most of the durable value is created.
Manager involvement is not optional
If a participant's manager does not know what was covered and does not expect the work to change, the training will not survive contact with the next deadline.
We brief managers before each cohort on what their people will be able to do afterwards, and we ask them to assign a task that requires the new capability within two weeks.
That last part matters most. A skill with no immediate application is a skill that gets forgotten.
Write down what will stop
Every training programme makes some existing practice redundant. If nobody says so explicitly, both continue — the new process partially adopted, the old one kept as a safety net, and staff doing the work twice.
Naming what stops, and when, is uncomfortable and necessary. It is also how you convert training into the efficiency saving that was supposed to justify it.
What to report to leadership
Replace attendance with:
- capability score change, pre to post, by department
- percentage completing a defined real task unaided at ninety days
- count of parallel or legacy processes retired
- hours saved per week, estimated from the task measurements taken during diagnosis
- adoption metrics from the systems themselves, where they exist
Those five numbers describe an investment. Attendance describes an event.
Applying this to your own organisation?
We would rather diagnose your situation than sell you a product. Book a call and we will tell you honestly whether this is worth doing now, later, or not at all.