Your last change programme was declared a success. Eighteen months later, nobody does it any more.
Nobody investigated. The team had disbanded, the budget had closed, and the scorecard stopped measuring on the day everything looked best.
This is the most expensive pattern in organisational life, and almost no framework addresses it. Kotter, ADKAR and every model on the shelf tell you how to make change happen. None of them tell you why it evaporates afterwards, or what would have held it in place.
Loop Zero is a model of what happens after the launch event.
It starts from an assumption most organisations never examine: that change is absolute. That once you change something, it stays changed. It does not. Change reverts because nothing holds it, gets circumvented because the new way is harder than the old one, and quietly disappears because it was rolled out rather than grown, so within two years nobody left knows what changed or why.
Underneath all three sits an arrow nobody manages. Results teach beliefs, continuously and automatically, whether or not anyone intends it. Your last three initiatives have already taught your organisation what to expect from this one. That arrow is Loop Zero, and it decides what any new change is walking into.
What you get
- A four-layer model of how organisations actually run, and the three depths at which any intervention can be aimed
- The anchor grid: nine concrete places to hold a change, and the drift signal that appears when each one is left empty
- Three tests that verify whether belief has genuinely shifted, instead of declaring it at a town hall
- How to read a failure backwards to the exact anchor that was missing
- Why more anchoring is not better, and how good controls harden into rules nobody can explain
- How to tell an organisation that is drifting from one that is correctly refusing a change that deserves to fail
- Four procedures you can run on Monday: designing a change, diagnosing one in trouble, auditing one already declared finished, and triaging a whole portfolio
- A worked case, ending undecided rather than in a tidy victory, because the twelve-month test has not come due
Written for the operations lead, HR director, transformation manager, continuous improvement practitioner or executive sponsor who has personally watched a well-run programme dissolve, has a suspicion about why, and has never had the vocabulary for it.
By a global talent and people leader with over two decades across Fortune 500 organisations in Asia Pacific, Europe and the Americas, who has designed, launched, inherited and buried more change programmes than he can now reconstruct.
The final chapter states what this model predicts and exactly what would prove it wrong. Very few business books will do that, and it is the reason to trust the rest.
Change is not a state you arrive at. It is a position you hold.