Technology Modernisation · 5 min read
Why Change Management Decides Whether a New System Actually Gets Used
The best-built system in the world is worthless if the team using it never adopts it. Here's what adoption actually takes.
A recurring pattern in technology modernisation work: a business replaces a manual, WhatsApp-and-spreadsheet-run process with a real system — properly built, properly tested — and three months later, half the team is still doing it the old way. The software wasn't the problem. Nobody planned for the part where people had to actually change how they work.
Resistance isn't a personality problem
People don't resist new tools because they're difficult. They resist tools that were rolled out to them rather than with them — where the first time anyone on the team heard about the change was the day it went live. Resistance to a new system is almost always resistance to how it arrived, not resistance to the system itself.
What real change management looks like
It starts before the system is built: a kickoff with the people who will actually use it, not just the person who approved the budget, so the change is something that happened with them rather than to them. It continues through implementation with role-specific training — a warehouse team and a finance team need different things from the same system, and one generic training session for everyone is how adoption quietly fails. And it doesn't stop at launch: the first few weeks of real use are when questions surface that no amount of planning would have caught, and that's exactly when support needs to be closest, not winding down.
Why this is an engineering conversation, not just a training one
A system genuinely designed around how a team already works needs far less persuasion to get adopted than one designed around how a process should theoretically work in principle. This is why understanding the actual workflow — not just the request — comes before any technical decision. The system that fits how people already think about their job is the one that survives contact with a busy Tuesday. The system that requires people to think differently in order to use it, however elegant, is the one that quietly reverts to the spreadsheet within a month.