Most transformations don’t fail in the build. They fail in the handover.
Ask anyone who has lived through a major transformation what went wrong, and they rarely point at the technology. The platform went live. The data migrated. The integrations held. On paper, it worked. And yet six months on, people are still running the old spreadsheet alongside the new system, workarounds have quietly multiplied, and the benefits case that justified the whole programme is nowhere to be found.
This is the uncomfortable truth about change. The build is the easy part. The hard part is the handover - the point at which a new way of working has to stop being a project and become, simply, how things are done. That transition is where most transformations quietly come undone.
The reason is straightforward.
Technology is deterministic; people are not. A system does what it is told. A workforce does what makes sense to them under pressure, on a busy Tuesday, when the new process is slower than the old one and the deadline hasn’t moved. If the new way feels harder, people route around it - and every workaround chips away at the benefits the business case promised.
So why does it keep happening?
Because too often change management is treated as a communications workstream bolted onto the end of a delivery plan: a few emails, a training session, a launch poster and a hopeful go-live date. That isn’t adoption. Adoption is a behavioural shift, and behavioural shifts take weeks or months of deliberate, active management - not a single moment in a project plan.
The organisations that get this right tend to do a handful of things differently. They involve the people who will actually use the system in designing it - not a steering committee at arm’s length, but the staff who will live with the change every day. People support what they help to build.
They find the informal influencers, not just the org chart. Every organisation has people whose opinion carries weight regardless of their job title. If they’re sceptical, the change stalls. If they’re convinced, they carry others with them.
They are honest about what gets harder before it gets easier.
Pretending a transition is painless destroys trust the moment reality bites. Naming the difficulty - and supporting people through it - builds the credibility that adoption depends on.
And, crucially, they measure adoption, not just deployment. “The system is live” is not the same as “people are using it as intended.” The first is a technical milestone. The second is the one that pays for the programme.
That last point matters more than any other, because benefits live on the far side of adoption. A flawless build delivers nothing if the people it was built for keep working the old way. The return on a transformation isn’t unlocked at go-live; it’s unlocked when behaviour changes - and that is precisely the part that gets the least attention and the least budget.
It’s why we plan for the handover from the first day of a programme, not as an afterthought in its final weeks.
The people who design the change should be the same people helping the organisation absorb it, because adoption can’t be subcontracted to a training module at the end. And it’s why we judge our own success not by a smooth launch, but by what is still working months after we’ve gone.
