Most technology projects that disappoint don't fail technically. The system works. What's missing is the change in how people work: staff keep their spreadsheets, processes drift back to the old way, and the benefits in the business case never arrive.
Change management is how you close that gap. Here's a practical approach for technology projects of any size.
Start at the beginning, not at go-live
Change management is often left until just before go-live, when there's little time to do anything but send an announcement and run a training session. Starting during discovery is cheaper and far more effective, because understanding who is affected shapes the design itself.
Understand who is affected, and how much
A change impact assessment looks at each group of people and asks what will be different for them: their tasks, tools, skills and responsibilities. Some groups will barely notice the change, others will see their daily work transformed. Your effort should go where the impact is greatest.
Equip leaders and champions
People take their cues from their own managers, not from project announcements. Make sure managers understand the change, why it matters and what to say to their teams. A network of change champions, respected people in each team who get early access and help their colleagues, makes support available where it's needed.
Explain why, not just what
People are far more willing to change when they understand the reason. Explain the problem the change solves, what it means for each team and what support is available. Communicate early, consistently and through the channels people actually use.
Train close to go-live, by role
Training delivered months before go-live is forgotten by the time it's needed. Train people close to when they'll use the new system, focused on the tasks they actually do, and give them short guides they can return to.
Support people through go-live
The first weeks after go-live decide whether a change sticks. Make help easy to reach, fix early problems quickly, and listen to feedback. Visible support at this stage builds confidence.
Measure adoption
Agree up front how you'll know the change is working, then track it. Useful measures include:
- Usage of the new system or process
- Tasks completed the new way
- Fewer workarounds and duplicate spreadsheets
- Support requests over time
- Staff feedback and confidence
Reinforce, and retire the old way
If the old system or spreadsheet is still available, many people will keep using it. Plan when old tools are retired, recognise teams that adopt the change, and keep reinforcing it until the new way is simply how work is done.
A note on AI adoption
AI brings its own change challenges. Some staff worry about their jobs, some distrust AI outputs, and many simply don't know where it would help. Successful AI adoption needs honest communication about why it's being introduced, clear rules for safe use, examples relevant to each role, and leaders who use it themselves.
Change management checklist
- Change management planned from the start of the project
- Impact assessed for each affected group
- Managers briefed and champions in place
- The reason for the change clearly communicated
- Role-based training scheduled close to go-live
- Go-live support arranged
- Adoption measures agreed and tracked
- Old tools and workarounds retired
Change management doesn't need to be complicated. It needs to be planned, owned and measured, just like the technology itself.