How to Sustain Momentum Until the Change Sticks
Most changes are not rejected. They fade. Energy peaks at launch and drains over the following weeks as attention moves on and the team drifts back to what is comfortable. This is the unglamorous work that decides whether a change holds: checking, recognizing, catching slippage early, adapting, and building the change into systems. It is where lasting change is actually won, long after the announcement everyone remembers.
Developing
Start here. Build the foundation.- 1
Put adoption on a standing agenda, a line in your weekly team check-in, so 'is the new way actually being used' is a regular question rather than something you remember to look at months later. Most changes fade not because anyone decided to drop them, but because no one was watching after launch.
- 2
Name the individuals and teams using the new way, specifically and where others can hear it. 'The way this team ran the new handoff this week is exactly it.' Early effort that goes unrecognized quietly stops, and recognition tells everyone what gets noticed here.
- 3
Set a reminder for two weeks and six weeks out to check adoption deliberately, not just by feel. Early adoption is fragile and quiet, and the dip usually comes after the launch energy fades, right when most leaders have stopped looking.
Proficient
Build consistency and rhythm.- 4
When you see the team slipping back toward the old way, name it and correct it while it is small. One quiet word at the first revert is easier than a team-wide reset three months on, once the old way has become the default again.
- 5
When the people doing the work surface a real flaw in how the change was designed, fix that part and tell them what you changed and why. The team seeing their input move the rollout is what keeps the next round of feedback honest. The judgment is telling a real design flaw from ordinary discomfort: adjust the first, hold the line on the second.
- 6
Watch for the change becoming theater, where people perform the new way when you are looking and revert when you are not. That gap is a sign the new way is still harder than the old one, or the reason never landed, and it points you back to friction or the case, not to more reminders.
Mastered
Operate at the highest level.- 7
Bake the change into the systems that run without you: onboarding for new hires, the standard checklists, performance reviews, hiring criteria. You know it is done when the change still holds after you stop reinforcing it, because the systems carry it, not your energy.
- 8
Add the new way to how new people are brought on, so no one learns the old way first. The fastest way to lose a change is to keep hiring and onboarding people into the habits it was meant to replace.
- 9
Build the change into what gets measured and reviewed, so doing it the new way is part of how good work is defined, not a separate initiative. Once the change is simply how performance is assessed here, it has stopped being a change and become the standard.
Common Pitfalls
Avoid the common failure modes.- Treating go-live as the finish line, then discovering the reversion months later, once it has already become the norm again.
- Only speaking up to criticize lapses and never to recognize progress, which drains the will to keep trying.
- Holding rigidly to a plan the team has shown is flawed, which teaches everyone that the feedback you asked for was theater.