Change Management
A new system or structure delivers nothing until people use it as intended. Organisations routinely spend heavily on the implementation and almost nothing on the adoption, then conclude the software was poor when in fact it was never used. Resistance is usually rational: people protect a way of working that has served them, and telling them the change is exciting does not address that.
1
Analyse
Who is affected, how
2
Communicate
Honest and early
3
Train
By role, not en masse
4
Support
Through the transition
5
Measure
Adoption from data
How We Deliver It
01
Stakeholder Analysis
We identify who is affected and how, because the impact varies enormously. A change that is neutral for one department may remove another department reason for existing, and those two groups cannot receive the same message.
- Groups affected identified with the nature of the impact
- Influence and attitude mapped per group
- Individuals whose support is decisive identified
- Sources of resistance understood rather than dismissed
02
Communication Planning
Early and honest, including the parts people will not welcome. Communication that only presents benefits loses credibility at the first difficulty, and once lost it does not come back during the project.
- Key messages per affected group
- Difficult messages addressed rather than avoided
- Timing sequenced so nobody hears it secondhand
- Channel and messenger chosen per audience
03
Training by Role
Training built around what each group will actually do, not a demonstration of every feature. A finance clerk and an approver need different sessions, and combining them wastes the time of both.
- Training designed per role and workflow
- Hands on practice in a test environment
- Quick reference material for the first weeks
- Super users identified and trained first
04
Transition Support
The first weeks determine whether the change holds. Support has to be immediately reachable, because a person blocked for two hours reverts to the old method and frequently never comes back.
- Floor walking and immediate support at go live
- Rapid response to questions in the first weeks
- Common issues identified and addressed centrally
- Workarounds detected and dealt with early
05
Adoption Measurement
Adoption measured from system data rather than assumed from attendance registers. Usage tells you whether the change happened; a training register tells you who was in the room.
- Usage measured from actual system data
- Departments and individuals not adopting identified
- Reasons for non adoption investigated rather than escalated
- Post implementation review against the intended benefit
What You Receive
- Stakeholder analysis with impact and attitude mapped
- Communication plan with messages per affected group
- Role based training material and delivery
- Super user identification and enablement
- Go live support arrangements
- Adoption measured from system data with a post implementation review
Indicative Timeline
Change work runs alongside the implementation rather than after it. Preparation starts four to eight weeks before go live and support continues for four to eight weeks afterwards.
- Stakeholder analysis and planning: two weeks
- Communication: from four to eight weeks before go live
- Training: one to two weeks before go live
- Support and adoption measurement: four to eight weeks after
Where Change Programmes Fail
The same causes recur, and none of them are technical.
No Visible Sponsor
Leadership announces the change then disappears, and staff read the silence accurately.
One Way Communication
Messages broadcast with no route for concerns, so resistance goes underground instead of surfacing.
Generic Training
One session for everybody, pitched to nobody, delivered too early to be remembered.
No Go Live Support
Users blocked in the first week revert to the old method and rarely return.
Unmeasured Adoption
Attendance recorded, usage never checked, so partial adoption looks like success.
Old System Left Running
Where the previous method remains available, a meaningful share of people keep using it.
Frequently Asked Questions
Is change management not just training and emails?
Training and communication are components. The work is understanding why people will resist, addressing it honestly, and measuring whether behaviour actually changed. Sending emails and running a session is what organisations do instead of that.
When should this start?
Before the build finishes, not at go live. People who first hear about a change when it arrives have had no chance to raise concerns, and the concerns then surface as resistance rather than as useful input.
What if leadership will not visibly support it?
Then it will probably fail, and we would say so at the outset. Staff read leadership silence accurately. Visible, repeated sponsorship is the single strongest predictor of adoption and it cannot be substituted.
How do you measure adoption?
From system data: who is logging in, which functions are used, how much activity still flows through the old route. Attendance registers measure attendance, which is a different thing entirely.
What about people who simply refuse?
First establish why, because it is often a genuine gap the design missed. Where it is genuine resistance to a legitimate decision, that becomes a management matter rather than a change management one, and we make that distinction explicit.
Should we keep the old system running in parallel?
Briefly and with an announced end date. Indefinite parallel running guarantees a meaningful share of people never move, and it doubles the effort while halving the benefit.
Related Services
This sits inside our Consulting practice. Related work: Workflow Automation where a new process needs adopting, and Organisational Review and Design where the change is structural.
