The Training That Did Not Survive the Shop Floor
A retail chain is rolling out a new point-of-sale system to 120 stores. Head office ran a two-day classroom course for 240 'store champions', who were then expected to train their colleagues. Three weeks after the first 40 stores went live, average transaction time has risen 22% and queue complaints are up. Store visits show champions trained colleagues in back rooms using slides, but staff cannot find the new 'void item' function under pressure, and the printed quick-reference cards were never distributed because the print run slipped. Managers at busy stores are telling staff to use the old till for peak hours 'just until things settle'. The change lead owns the environment and readiness workstream.
1. Diagnose why the training did not transfer to the shop floor.
Read the worked answer
The training was designed for the classroom, not for the till under time pressure. Several environment factors failed at once:
- Train-the-trainer assumed champions could teach well and had time to; back-room slide sessions do not rehearse the pressured moment where the skill is needed.
- The quick-reference cards, the main on-the-job support, never arrived, so there was no prompt at the point of use.
- Peak-hour fallback to the old till is a rational response by managers protecting queues, but it removes the practice that would build fluency and keeps transaction times high.
- The 22% slowdown is consistent with unfamiliarity plus no job aid, not with the system being wrong.
The change lead's diagnosis should separate a design gap (no point-of-use support) from a behavioural one (fallback), because they need different fixes.
2. What should the change lead do in the next two weeks, before the remaining 80 stores go live?
Read the worked answer
Treat the first 40 stores as a pilot that has told you the readiness approach is wrong, and fix the environment before scaling.
Priority actions:
- Get point-of-use support in place immediately: expedite the quick-reference cards, and in the meantime put a one-page void-item and top-task guide at each till. This is the highest-leverage fix because it addresses the observed failure directly.
- Replace back-room slides for the remaining stores with short, till-side practice on the busiest tasks, run at realistic pace.
- Agree with store managers a clear position on the old till: a defined cut-off date and a named support contact for peak periods, so fallback is time-boxed rather than open-ended.
- Add a floor-walker or peer buddy for the first week at each new store, drawn from champions who are coping well.
- Hold the next wave until the cards are in stores and managers have the new guidance.
The judgement: delaying 80 stores by a week is cheaper than 80 more stores running two systems at once.
3. How should the change lead measure whether the environment is now ready?
Read the worked answer
Measure readiness on leading indicators that predict adoption, not just on go-live completion.
Indicators to track per store:
- Transaction time relative to the pre-change baseline, trending toward parity week on week.
- Proportion of transactions on the new system during peak hours (the fallback rate), which shows whether staff are actually practising.
- Frequency of void-item and other top-task errors, which shows whether the job aid is working.
- A short staff pulse on confidence and 'can I find what I need at the till', plus manager confirmation that cards are physically present.
Set thresholds: a store is ready for its next wave only if fallback is below an agreed level and transaction time is closing on baseline. Review weekly with store managers so the data drives action rather than sitting in a report.
The change lead's point: readiness is a property of the environment staff work in, so measure it where they work, not in the classroom.