The deck everyone applauded and nobody used
Training fails when it is generic, distant from the real job, and disconnected from consequences. Operators learn by doing under time pressure — design for that, not for auditorium applause. Go-live is not training. If the room reverts to the old spreadsheet in week two, the migration was data, not behaviour change.
A one-hour webinar does not change Tuesday. Habit changes when the tool is the path of least resistance on a busy afternoon — and when bypassing it is visible to someone with authority.
What works on the floor
Train on live-shaped examples: same customer types, same partial deliveries, same approvals your team argues about. Use floor coaches for two weeks — named people on shift who can answer "where do I click" without opening a support ticket. Run short office hours daily in week one, then taper. That is far more effective than one dump of slides before a long weekend.
Track one metric for adoption: jobs closed in-system, quotes sent from the tool, zero shadow sheet edits. Pick one leadership will notice. And make sure an executive sponsor is visible when someone bypasses the tool — not angry, but genuinely curious about what broke in the process.
What to stop doing
Training that covers every module nobody uses in phase one is wasted time — phase one scope covers why. Training owned by IT alone with no ops voice means the floor will smell the irrelevance. PDF manuals nobody opens. Punishing mistakes without fixing the underlying UX or permissions — people will route around pain regardless of how many sessions you run.
The first month sets the habit for the year. The first 30 days after a build guidance is directly relevant here. And if only one trainer knows the workaround, you have rebuilt hero dependency — exactly the problem covered in handover when one person holds the truth.
Change management beyond the slide
Name what stays manual on purpose — exceptions are fine if they are owned. Publish who to ask and the expected response time. Celebrate small wins publicly: first week with no parallel spreadsheet, first month-end run from the new report. If the bypass route is dropping truth back into email threads, email is not a workflow covers why that matters.
Permissions and UX are part of training
If the tool forces six clicks for the common path, people will bypass it regardless of what the slides say. Fix defaults, templates, and role permissions before you blame culture. Floor coaches should log friction — that list feeds phase two or a quick build fix.
Executives must use the tool for the status they ask others to use. If leadership only reads status aloud in meetings, the floor correctly reads that talking is the real system. Sponsorship is visible behaviour, not a kickoff speech.
Measure habit, not attendance
Attendance sheets prove nothing. Track jobs closed in-system, quotes sent from the tool, and support tickets asking "how do I". A rising bypass rate is an early warning — investigate before month-end shame. That metric connects directly to first 30 days after a build.
Go-live care beats a big bang training day. System care exists because habits rot when nobody tends them in busy quarters.
Book a review. Care for post-go-live habit — systems rot when nobody tends them in busy quarters. Teesside and the North East when the room needs presence, remote when artefacts are clear.