There is a practical line between a system that goes live and a system that gets used, and it is drawn by training. Go-live asks "does it run?" Competence asks "can the team run it, across the cases that matter, reproducibly?"
The competence loop
Define required competence. Build exercises from real work. Run the workshops. Measure capability. Find the gaps. Improve the material. Roll out. Monitor.
The loop is unglamorous and it is the entire difference. Each iteration produces evidence instead of impressions.
What to train
Operation of the actual workflows — not generic software tours. Behaviour when input is missing or ambiguous. Escalation: knowing when to stop and whom to ask. Retention: can the team still do it a quarter later, without the trainer in the room?
Competence compounds
A trained team is an asset. It survives software upgrades, process changes and staffing turnover — and it is how a system stays trustworthy across years rather than demos.