Change management and adoption
Switching a feature on in 320 stores takes minutes. Getting 1,920 people to change how they work takes months, and most internal tools that fail, fail here. This lesson shows you why frontline staff resist a new way of working, how champions and one-page SOPs win them over, when to mandate and how to retire the old way, how to size rollout waves from the trainers and support you really have, and how to track adoption store by store.
By the end you can
- Diagnose why a group isn't adopting with the ADKAR model, and pick the action that fixes the first missing step
- Set up a champion network and write a one-page SOP staff will actually use
- Decide when to earn adoption and when to mandate it, and plan the retirement of the old way
- Size rollout waves from trainer, support desk and device capacity, and see the trade-offs in a simulator
- Track adoption depth per store and run a playbook for the stores that lag
The everyday picture
A city replaces cash fares on its buses with tap cards. Some riders switch in the first week because tapping is faster than counting coins. Others keep paying cash, because nobody told them where to buy a card, or the machine at their stop is broken, or they don't trust that the card will work. For the first month, helpers in bright jackets stand at the busiest stops and show people how to tap. A picture sign at each stop shows the three steps.
The city doesn't switch every route on the same day, because the phone line for lost cards would be flooded. It goes route by route, fixing what the first routes teach it. And at some point it announces a date after which drivers stop taking cash. That is a rollout: people who must be convinced, helpers on the spot, simple instructions where the work happens, waves sized to what support can handle, and a date when the old way ends.
Why people resist, and what to do about each reason
Resistance to a new tool is usually rational. The new way is slower at first. Nobody asked the people who do the job. A new audit trail feels like being watched. The old workaround also did a job nobody noticed, such as the chat group where the area manager thanks staff for a good week. The store manager is measured on something the change makes worse. Or the last "new system" failed them during a rush and they had to redo everything on paper.
A useful way to find the real reason is Prosci's ADKAR model. It describes five things a person needs, in order, for a change to stick: Awareness of why it is happening, Desire to take part, Knowledge of how, the Ability to do it in real conditions, and Reinforcement so it lasts. Its practical use is diagnosis: find the first missing element for a group, and fix that one. Training (Knowledge) does nothing for staff who don't see why the change is happening, or for staff who know exactly how but have no signal at the dock (Ability).
| Element | Sign it's missing in a store | What to do |
|---|---|---|
| Awareness | "Head office changes the system every year" | Explain the why in their terms: no more retyping, fewer corrections that come back to the store |
| Desire | Staff know why but prefer paper; the manager is lukewarm | Show what's in it for them, use a respected colleague as champion, address the fear directly ("the audit trail protects you when a delivery is disputed") |
| Knowledge | Staff try it and get stuck on exceptions | A one-page SOP, 10 minutes of hands-on practice with a real delivery, help from the champion |
| Ability | Staff know how, but it fails in the cold room or at the dock | Fix the condition: Wi-Fi, glove mode, a second handheld, a slower first week (pm-36) |
| Reinforcement | Good first weeks, then paper creeps back | The area manager reviews coverage weekly, the old forms stop arriving, good stores are recognised |
Two other well-known guides point the same way. In Switch (2010), Chip and Dan Heath describe three things to work on: give people's reasoning side clear direction ("script the critical moves"), give their emotional side a reason to move ("shrink the change" so it feels doable), and shape the path so the right way is the easy way, for example by not sending paper pads any more. John Kotter's 1995 Harvard Business Review article "Leading Change: Why Transformation Efforts Fail" lists eight common errors. Two matter most in rollouts: under-communicating the vision, which he puts at a factor of ten, and declaring victory too soon.
Expect a productivity dip. For the first days, the new way is slower than the old way the person has done a thousand times. Plan for it: lighter deliveries in a store's first week on the new flow, the champion on the same shift, and never a first week that lands in a festival rush.