Let me tell you what go-live measures.
It measures whether the technology works. It measures whether the data migrated cleanly. It measures whether the integrations ran as designed and whether the system processed its first transactions without falling over. It measures whether the project team hit the date they committed to, under the conditions they were given, against the plan they wrote eighteen months ago.
It measures, in other words, the technical architecture.
It measures almost nothing about whether the transformation actually happened.
I have been on the ground at enough go-lives to know what the first seventy-two hours look like. There is genuine relief, the kind that comes from a sustained period of enormous pressure finally releasing. There are congratulations. There are bottles of something cold. And underneath it, if you are paying attention, there is already something else beginning.
The workarounds.
Not immediately visible. Not reported in any dashboard. But there, already, in the way a team lead explains the new process to their people and quietly adds: and if that doesn't work, here's what we do instead. In the Excel file that reappears on a shared drive three days after go-live. In the informal WhatsApp group where people share shortcuts around the parts of the system that don't match the way they actually work. In the middle manager who nods in every training session and goes back to their desk and does it the old way, because the old way works and the new way doesn't yet, and they have targets to hit and no time to experiment.
This is not resistance. This is people doing their jobs under pressure with the tools available to them. The workaround is not a failure of will. It is a failure of design, and the design failure happened long before go-live, in the decisions made about how much time and resource and leadership attention to invest in the human side of the programme.
Go-live celebrates the end of the technical project. It is, at best, the beginning of the actual transformation.
The organisations that understand this are the ones that ask different questions. Not: did we go live on time? But: what is the adoption rate at month three? At month six? Are people working the new way because it is genuinely better, or because they have been told to and are being watched? Has the middle layer, the managers who translate strategy into daily behaviour, been prepared for what their role requires now? Do the senior leaders understand what sustained sponsorship looks like after the project team has gone home?
These questions are almost never asked, because the programme is closed by the time they become answerable. The budget has been released. The SI has moved on. The steering committee has disbanded. The transformation director is already being asked what's next.
And in the business, quietly, the workarounds are becoming permanent.
I have seen organisations still running shadow processes eighteen months after a go-live that was reported as successful. Eighteen months of parallel running, of people carrying the cognitive load of two systems, of data that lives in the official system and the real picture that lives somewhere else. The cost of that, in productivity, in data quality, in the slow erosion of confidence in the programme's value is never counted against the project. It happened after the project closed.
Go-live is a milestone. It is an important one. I am not arguing against celebrating it.
I am arguing that treating it as the measure of success is one of the most expensive mistakes an organisation can make and that the organisations still making it are the ones whose next transformation will have exactly the same ending.
The measure is adoption. The measure is whether, six months after the system went live, the people who were supposed to change are actually working differently not because they have to, but because the new way is better and they know it.
That outcome does not happen by accident. It does not happen because the technology worked. It happens because someone, early enough in the programme to make a difference, applied the same rigour to the human architecture as to the technical one.
That is the work. Everything else is just go-live.