Embedding change
Why embedding is a separate step
- The teaching guide lists embed change as its own element, because most failed changes are not rejected — they are implemented and then quietly reversed.
- A change is embedded when it survives without management attention: when the people who arrive after the change have no idea it was ever done differently.
- The dangerous period is the months after the launch, when management moves on to the next project and the old habits are still available.
What makes a change stick
- Remove the old way. As long as the old system, form or machine is still there, some people will keep using it under pressure. Turning it off is the single most effective embedding action.
- Change the measures. People do what they are measured on. If the reports, targets and bonuses still reflect the old way, the old way wins.
- Change the job descriptions and training. New staff must be trained into the new way as the only way, not taught the new way and told what people used to do.
- Make managers model it. A supervisor who quietly authorises the old method whenever a deadline is tight tells everyone the change is optional.
- Show early results. Publishing the improvement — waste down, complaints down, time saved — converts the people who complied without believing.
- Recognise the people who made it work, so the change is associated with success rather than with being pushed around.
- Follow up on a schedule. Reviewing at one, three and six months keeps the change visible while the habit forms.
- Fix the things that do not work. A change that is defended rigidly against genuine problems teaches staff that management is not listening, and they revert.
Signs a change has not embedded
- Two systems running in parallel — the official one and the real one.
- Staff describing the change as "the new system" a year later.
- Data quality falling once monitoring stops.
- Exceptions being granted routinely.
- New employees being trained informally in the old method by colleagues.
How this interacts with the other internal factors
- Quality. A total quality management system is exactly a change that must be embedded; if management drops quality the first time a deadline is tight, the culture collapses.
- Innovation. An innovation is only worth its development cost if the new process is actually adopted, so an innovation project without a change plan tends to fail at the last step.
- Investment appraisal. The forecast savings that justified the investment only appear if the change embeds — which is one reason projects miss the returns their appraisal predicted.