If it needs you to stay, it isn't finished.

There is a moment in every engagement where the work looks done. The system is live, people are using it, the metrics are moving. It is tempting to call it a win and move on.

It is also the moment where most of the long-term value is won or lost, because a change that only holds while you are standing over it was never actually finished. It was propped up.

The real test of a transformation is not whether it works while you are watching. It is whether it survives you looking away.

Adoption is a curve, and curves slide back

Getting people to the new way is one thing. Keeping them there, after the attention moves on and the next priority arrives, is another entirely.

Without reinforcement, adoption decays. Old habits have years of muscle memory behind them. The new way has weeks. Left alone, the organization drifts back toward what it knew.

Six months later you are quietly back where you started, with a system nobody fully uses and a team that has learned, again, that change does not stick. The cost of that drift is not just the lost return. It is the credibility you spend that you will need for the next change.

Reinforcement is not a memo either

Sustainment fails the same way readiness fails, by being reduced to communication. A reminder email that the new way is still expected does almost nothing against the gravity of old habits.

What holds a change is structure, not encouragement. The new way has to be the path of least resistance, wired into the systems and routines so that doing it right is easier than reverting.

If reverting is still the easy option, people will revert, no matter how many times you tell them not to.

Embed the cadence

Sustaining a change means building it into the rhythm of how the organization runs. The rituals, the metrics that get reviewed, the management routines that keep the new way visible and expected.

This is the Anchor work, and it is unglamorous on purpose. It is standing reviews, clear ownership, and reinforcement that does not depend on anyone remembering to care.

The goal is to make the new way the default, so that a year from now nobody thinks of it as the new way at all. It is just how things are done.

Measure against where you started

The proof that a transformation is real is not a declaration in a steering committee. It is the baseline you captured at the start, met.

That is why the cost-of-the-status-quo number from the very beginning matters so much at the very end. It is the scoreboard. An actual measured outcome against where you started is a result. Everything else is a story, and stories do not survive a budget review.

If you never baselined, you can never prove you closed the gap, and a change you cannot prove is a change the next leader can quietly walk back.

Then make yourself unnecessary

The final job of anyone leading a change is to transfer the capability to the people who will live with it. The internal team has to be able to run the new way, reinforce it, and troubleshoot it without the person who built it.

A transformation that depends on the advisor, or the project lead, or the one passionate champion to keep it alive is a dependency, not a capability.

The work is not finished when the change is working. It is finished when the change works without you. Anything short of that is a liability dressed up as a success.

Beware the hero dependency

Many changes survive only because one committed person carries them. That looks like success right up until that person leaves, gets promoted, or burns out, at which point the whole thing collapses with surprising speed.

A change held up by a single hero is fragile by design. The point of transfer is to remove that single point of failure, to spread the capability across enough people and structures that no one departure can undo it.

If you can name the one person whose exit would unravel a change, you have found the work that is not yet done.

Build to leave from day one

The best sustainment is not bolted on at the end. It is designed in from the start, with transfer in mind the whole way through. You build the team's ability as you go, so that by the time you step back, there is nothing to catch.

Leaving well is not an afterthought. It is the point. The measure of the work is what stands on its own after you are gone.

So ask the honest question about your own initiatives. If the person who led this walked away tomorrow, would it hold?

If the answer is no, the change is not finished. It is just being carried, and whoever is carrying it cannot do so forever. Finish it by making sure it no longer needs them.