Leading change: Making new ways of working stick after the launch
27 Oct 2026
I've seen plenty of change initiatives launch well. The announcement lands, everybody attends the training session and the new process goes live on schedule. Everyone agrees it's an improvement.
Then, six months later, I look closely and find the old spreadsheet still in use, the old approval path quietly back in place and the new system used only when someone is checking. Nothing failed outright. The change simply never became normal.
In my experience, this is one of the most overlooked stages of leading change. The rollout is the start of the work, not the end of it.
Why 'implemented' doesn't mean 'embedded'
Most people who slip back into old habits aren't resisting. Many genuinely supported the change. But three forces work against them every day.
Competing priorities come first. When deadlines bite, people reach for whatever feels fastest, and that's usually the method they've used for years. Unclear reinforcement comes next. If nobody notices whether the new approach is used, people reasonably conclude it's optional. Finally, familiar routines are powerful. Old habits are built into calendars, templates and team rhythms, and they don't disappear because a new process exists.

Reinforcing the new behaviour
Behaviour change sticks when expectations stay consistent long after launch. I make it clear what is now standard practice, not a pilot or a preference.
Managers carry much of this load. I ask them to follow up in their regular one-on-ones and team meetings, asking how the new approach is working rather than whether people are using it. I also make adoption visible with one or two simple measures that teams can see, such as the percentage of requests submitted through the new system.
Then I keep the conversation going. A short monthly discussion of what is and isn't working signals that the change still matters.
Removing what pulls people back
If the old process still exists, someone will use it. I look for anything that contradicts the new approach: legacy forms, duplicate reports, old approval steps or meetings designed around the previous way of working. Then I retire them.
When employees raise practical problems, I treat that as useful information, not resistance. Often they've found a genuine gap the project team missed. Responding quickly and fixing what I can shows people the change is designed to work for them, which makes them far more likely to keep using it.
Recognising progress and staying visibly committed
People repeat what gets noticed. I call out specific examples of the desired behaviour, such as a team that resolved an issue faster using the new workflow. Specific recognition shows everyone what good looks like.
My own behaviour matters most. If I stop asking about the change once the launch excitement fades, my team will notice and conclude it's no longer a priority. If I expect employees to stay committed, I need to keep demonstrating that commitment myself.
Revisit a recent change
Think about a change your department introduced in the past year. Are the desired behaviours still happening consistently, or only when someone is watching?
Start by clarifying what should now be considered standard practice. Remove one obstacle that makes the old habit easier than the new one. Then set up a simple way to review adoption over the next three to six months, whether that's a monthly measure or a standing agenda item.
Lasting organisational change rarely comes from a better launch. It comes from steady leadership after the launch. If you'd like to build these skills with your leadership team, explore ICML's Leading Change course.




