District managers and team leads who own an already-failed rollout
Our team went back to the old process. What do we do now?
Do not relaunch. A second launch of the same system reads as noise and burns the credibility you have left. Find out whether the old path is still open, whether the new way is genuinely slower for the individual, and whether anyone noticed when people stopped. Fix whichever of those is true, then reintroduce quietly to one team.
Why relaunching makes it worse
A relaunch tells everyone the first announcement did not mean anything, which is precisely the belief you need to reverse. It also spends attention you will need later.
The second attempt has to be smaller and quieter than the first, not louder.
Diagnose before you do anything
Is the old path still open? Most reversion is not defiance. It is a door that was left unlocked.
Is the new way actually slower for the person doing it? Time both, honestly, with a real user rather than a champion. Organizations routinely deploy systems that are faster in aggregate and slower per individual, then wonder about compliance.
Did anyone notice when people stopped? If reversion carried no consequence and no conversation, the system taught everyone that it did not matter.
Reintroduce to one team, not the whole region
Pick the team most likely to succeed, close the old path for them specifically, and check in during week three. Let their numbers do the arguing.
A single team that visibly stuck with it is more persuasive to the rest of the org than any mandate from above.
The part nobody names
The mechanism underneath all of this has a name. Dr. Noah St. John calls it taming the caveman in your brain, and it is not a metaphor for laziness. A 200,000-year-old survival instinct is making decisions about 2026 software. It treats an unfamiliar system as a threat, it prefers the known path, and it fires before anyone consciously chooses anything.
That is why the fix is behavioral rather than technical, and why it holds once it is installed. Dr. Noah has spent 29 years on this specific gap, with $3 billion in documented client results across 150+ countries and 27 books in print.
Common questions
Should we relaunch a failed software rollout?
Not in the same form. Diagnose why it reverted, fix that specific cause, then reintroduce quietly to one team rather than announcing a second company-wide launch.
How do you get a team to stop using the old spreadsheet?
Close it. If the legacy path still works it will keep winning, because it is faster for the individual even when it costs the organization more.
Want your team’s number instead of a general answer?
Twelve questions, about three minutes. It scores your team on the four places execution actually leaks and gives you a dollar figure for what the friction is costing you a year.
FIND MY HIDDEN FRICTION