Most transformations have a launch date: a go-live, a moment when someone declares the project done and the team moves on. That moment is usually where the real work begins, and where most of the value is quietly lost.
A system that is live is not a system that is used. A tool that is installed is not a tool that is adopted. The gap between those two is where budgets disappear, not in the build.
What we have seen
We once switched 29 stores, a quarter of a country's turnover, to a new system on a single date, with a ten-year service guarantee and zero lost sales. The changeover was not the hard part. Making sure every team trusted the new way on day one, that was the hard part, and it was planned for months.
On another engagement we inherited a support backlog that had built up over a month. We cleared it to two hours. Not with new tooling: with ownership, presence on the floor, and a team that decided the backlog was theirs to kill. Adoption is a human result before it is a technical one.
A system that is live is not a system that is used.
Why launches get celebrated and adoption gets skipped
A launch is visible. It has a date, a demo, a slide. Adoption is slow, unglamorous and hard to put in a steering-committee deck. So the incentive is to declare victory at go-live and leave the floor to cope. The people who sold the project are gone; the people who have to live with it are just starting.
How we treat it
We do not consider a job done when it ships. We consider it done when the organisation has adopted it and the number has moved. That is why landing is built into how we work, not sold as a follow-on. If it does not get used, it did not work, and if it did not work, neither did we.
The unglamorous truth: most of the return on a transformation is earned after the launch nobody remembers, by the people nobody thanked. Plan for that part first.