The training line nobody budgets
It is a small number on a project plan and the largest single cause of a good system going unused.
Budget for the hours your team spends learning, not just for the trainer, and count the slower weeks after launch as part of the cost. A system that people avoid returns nothing, whatever it cost to build.
The cost is your team's time, not the session
The trainer's fee is the visible part and usually the smaller one. Suppose twelve people spend four hours in training and roughly eight hours over the following weeks being slower than they were. That is around 144 working hours, and it is a real cost whether or not it appears in a budget.
Putting it in the budget is not pessimism. It is the difference between a launch that is planned around a slow fortnight and one that is scheduled on top of the busiest week of the quarter.
What people actually need
Very little of what is usually delivered. A single walkthrough of everything the system can do is the format that fails most reliably, because people retain the parts they use the next day and nothing else.
- The five things each role does daily, and nothing else on day one
- A one-page reference for each role, not a manual
- A named person to ask, for the first month
- A second short session two weeks in, when the real questions have appeared
- A written answer to what happens when it goes wrong
The month after launch is the expensive part
Productivity dips after any system change. The dip is normal and its size is a choice: a team that knows the five things it needs recovers quickly, and a team handed a manual works around the system instead.
Working around is the outcome to watch for. Once a parallel spreadsheet appears, the data in the system stops being trustworthy, and that is much harder to reverse than the original training gap.
Who trains the next person
Staff turn over. If training exists only as an event that happened at launch, the fourth person to join after that event learns from a colleague's approximation, and the approximation drifts.
The cheap fix is to record the sessions and keep the one-page references somewhere findable and owned by a named person. It costs an afternoon at launch and removes a recurring cost that nobody ever attributes to the project.
The signal that training failed
Not complaints. Complaints mean people are using it. The signal is silence combined with unchanged behaviour: the old process still running, the new system used for the minimum required, and the reports quietly not adding up.
Check usage a month after launch by role rather than in total. One enthusiastic department can hide an entire team that never started.
What to take from this
- 01Count learning hours and the slower weeks, not just the trainer's fee
- 02Teach the five daily actions per role, not the full feature set
- 03A parallel spreadsheet is the first evidence that adoption failed
- 04Record the sessions so the next hire is not trained by rumour
Ask the question directly
- Should the supplier deliver the training?
- For the first session, usually yes, because they know the system. The lasting version should be owned internally, because the internal person knows why your process is the way it is.
- When should training happen?
- Close enough to launch that it is still remembered, which in practice is the few days before. Training a month early is a cost with most of its value already expired.
- What if staff resist the new system?
- Ask what the old process did that the new one does not. Resistance is often correct and specific, and treating it as attitude rather than information is how a genuine gap becomes permanent.
Related answers
AI transformation
Most AI projects fail because they add a chat box next to the problem instead of removing the step that costs the hours. We start from the workflow, and from the systems and the data underneath it.
Growth transformation
Organic accounts, reputation, lifecycle and conversion run as one programme, with fractional leadership above it for the companies that need the seniority before they can justify the salary.
Bring the decision you are stuck on
A call, forty five minutes, no deck. We will tell you if we are the wrong firm.