Why "Nothing Broke Yet" Is Not the Same as "It Worked"

A garden does not stay planted on its own. Someone plants it, walks away for a season, and comes back to find weeds where the vegetables were supposed to be. Nothing dramatic happened. No storm wiped it out. It simply reverted to what land does by default when nobody keeps tending it.

Organizational change reverts the same way, and most leaders never notice because nothing dramatic marks the moment it starts.

Deloitte's own research states this plainly: only 10 percent of organizations are enacting strategic, systematic change to achieve meaningful, outcome-focused growth (Deloitte, 2026). That means roughly nine out of ten organizations treat change as something they launch and then, implicitly, leave alone. Deloitte titled this research "Change is everywhere, always on," and that phrase alone is the entire argument for why so many transformations quietly fail months after everyone already called them a success.

Here is the assumption that trips up almost every leader running a change effort. If nothing visibly breaks, the change must have worked. Nobody is complaining. The new process is technically still in use. The dashboard still shows adoption. Leadership moves on to the next priority, satisfied that this one is handled.

Silence is not the same as success. It is very often just the sound of something reverting slowly enough that nobody notices until it has already happened. The absence of complaints is not evidence the change stuck. It might just mean people stopped mentioning it, either because they already quietly reverted to the old way, or because they learned nobody was checking anymore, so there was no point flagging the drift out loud.

WHY SUSTAIN GETS TREATED AS THE ABSENCE OF FURTHER WORK

Engage and Transform both come with built-in signals that something is happening. Engage looks like listening sessions, surveys, real conversations. Transform looks like new systems going live, training being delivered, visible activity everyone can point to. Sustain has no equivalent visible marker, which is exactly why it gets treated as the phase where the real work is already finished.

This is a mistake with a very specific mechanism behind it. A new process, a new expectation, a new way of communicating- none of it survives on the momentum of its own launch. Every one of those changes is competing against years of accumulated habit, the old way of doing things that people knew cold and could execute without thinking. The new way requires ongoing attention precisely because the old way does not. Old habits do not politely wait for permission to come back. They return the moment sustained attention stops, the same way weeds return the moment nobody is pulling them.

Engage. Transform. Sustain.™ names this directly, and it is worth sitting with why the framing matters. Sustain asks organizations to do three things well: measure what matters, reinforce what works, and keep learning. Notice that none of those three are passive. Measuring requires someone to actually look. Reinforcing requires someone to actively repeat and model the behavior, not just hope it sticks after the first announcement. Learning requires treating the change as still open to revision, not settled. Deloitte's own framing backs this up almost word for word. Change that holds is "always on," not something you launch once and check on a year later.

THE PATTERN THAT LOOKS LIKE SUCCESS RIGHT UP UNTIL IT ISN'T

Picture the typical trajectory of a change initiative inside almost any organization. Month one, adoption is high, energy is high, leadership is actively reinforcing the new behavior in every meeting. By month four, leadership's attention has genuinely moved elsewhere, because there is always a next priority competing for it. The new behavior is still technically happening, but it's no longer being reinforced, measured, or discussed. By month nine, people have quietly drifted back toward whatever was easiest and most familiar, not out of resistance, but because nobody was actively holding the new standard in place anymore.

Nobody declared the change a failure. There was no single moment where leadership decided to abandon it. It simply stopped being sustained, one unattended week at a time, until the aggregate drift was large enough to notice, usually around the time someone asks why the numbers look like they did before the change ever happened.

This is precisely the gap Deloitte's 10 percent figure is describing. The nine out of ten organizations that aren't doing this well are rarely making one dramatic mistake. They are simply treating Sustain as a phase you complete rather than a discipline you keep practicing, and the drift back to old habits happens exactly as quietly as it sounds. Ask leadership at any of those nine organizations when the change failed, and most will struggle to name a date, because there wasn't one. There was only a long series of ordinary weeks where attention drifted somewhere else, each one individually harmless, collectively fatal to whatever was supposed to be holding.

WHAT ACTUAL SUSTAINING REQUIRES

Real sustaining work means building in a specific, recurring check, months after launch, not just at launch, that asks honestly whether the change is still real. It means leadership continuing to reference and reinforce the new standard in ordinary meetings long after the initial rollout has stopped feeling new or exciting. It means treating a good number six months in as a question worth investigating rather than a result worth simply celebrating and setting aside.

None of this is complicated to describe. It is genuinely difficult to practice, because it demands sustained attention on something that already looks finished, competing against a constant stream of new priorities that all look more urgent than checking on an old one. That is exactly why only 10 percent of organizations actually do it. Not because the other 90 percent don't care about their results. Because nothing about human attention naturally returns to something that looks like it's already working, until it very obviously isn't. That's why Sustain has to be built into a calendar rather than left to memory or good intentions. A recurring check that happens whether or not anyone feels like doing it that week is the only reliable defense against attention drifting exactly where it naturally wants to drift, toward whatever feels most urgent today rather than whatever was declared important six months ago.

THE ACTUAL TAKEAWAY

A garden left alone doesn't stay a garden. It becomes whatever the land defaults to without anyone actively shaping it, and the same is true of any change an organization has worked hard to create. Sustain is not the reward for finishing the hard work of Engage and Transform. It is where the hard work actually continues, quietly, for as long as the change is expected to hold.

Deloitte's own number should be sobering rather than surprising. Ninety percent of organizations are not failing at change because they lack good strategies or good intentions. They are failing because they stopped tending something the moment it stopped looking unfinished, and by the time the drift becomes visible, it rarely looks like the change failed. It looks like it was never real to begin with.