Every failed change has a great launch deck. The town hall goes fine. The new process gets a name and a logo. Leadership thanks everyone for their flexibility. And then, quietly, over about a quarter, the old way of working reasserts itself, because the old way still pays.
I have led change work through reorganizations, system migrations, and new operating models, and the pattern is consistent enough to name. Change does not fail at the announcement. It fails in the ninety days after, and it fails in predictable places.
Four conditions decide day 90
Sponsorship is still visible. Not endorsed once from a stage: visibly practiced. When leaders route their own requests through the new intake process, the process is real. When they quietly go around it, everyone notices, and the workaround becomes the process.
Enablement actually works. At the moment of need, can a person find the guide, the template, the training? If using the new way requires remembering a link from an email six weeks ago, the old way wins on convenience alone.
Decisions are logged. Every new model gets tested by a hard case within the first month. What happens next matters enormously. If the ruling is written down and shared, the model gains case law and gets stronger. If it is decided in a hallway, the model gains exceptions and gets weaker.
The feedback loop is trusted. People discover real problems with any new design. If reporting a problem is read as resistance, people stop reporting and start quietly working around. If feedback visibly improves the design, people become co-owners of it.
None of this is glamorous, all of it is buildable
Notice what is not on the list: more communications, better slogans, a bigger launch. Those have their place, but they are the paint, not the load-bearing walls.
The four conditions are systems you can design in advance. A sponsorship plan with named behaviors, not just names. Enablement embedded where the work happens. A decision log with an owner and a rhythm. A feedback channel with a visible response time.
That is the discipline behind the phrase I build my practice around: change that holds. Adoption is designed, not announced. If your last change faded and you are planning the next one, design these four in from the start, or let's talk before the launch deck gets written.