Change and Adoption
Not a module anyone ships — a consideration on every programme, and the delivery work that earns the benefits after go-live.
Why it matters
A system that is live but not adopted has cost everything and returned nothing. Adoption is not a training problem; it is a design, leadership and measurement problem that training supports.
Treating it as a module is the mistake that precedes treating it as optional. There is no configuration screen for it and no vendor line item, so it has to be carried as a consideration — assessed on every workstream, in the same way governance or compliance is, rather than delegated to a workstream of its own that the others can ignore.
- Benefits depend on behaviour: The business case assumed people work differently. Nothing else delivers that.
- Capacity is finite: An organisation can absorb only so much change at once, and exceeding it produces regression rather than progress.
- It is a leading indicator: Adoption signals appear before benefits do, which makes them the early warning.
The workflow
- 01
Impact assessment
Who is affected, how their work changes, and what they lose.
- 02
Stakeholder mapping
Influence, impact and what each group needs to hear.
- 03
Readiness baseline
Current ability and willingness, measured rather than assumed.
- 04
Leader activation
Sponsors and managers visibly doing the new thing first.
- 05
Learning pathway
Sequenced so capability arrives just before it is needed.
- 06
Adoption measurement
Actual usage and behaviour tracked after go-live.
- 07
Sustainment
Checked months later, when the programme team has gone.
The strongest predictor of adoption is whether the person's own manager uses the system. Communications campaigns do not compensate for a manager who keeps the old spreadsheet.
What you need in place
- A named benefit owner: Operational, still accountable twelve months after go-live.
- Impact assessed per role: Generic change plans produce generic results.
- Manager enablement: Before the workforce, not alongside it.
- Adoption measures defined before go-live: Usage, exception volume, workaround prevalence.
- Change capacity view: What else is landing on the same people at the same time.
Questions to ask
01Sponsor behaviour
Are leaders visibly using it?
If not, no amount of communication will land.
02Impact
Do we know, by role, what changes?
Without this, training is generic and adoption is accidental.
03Measurement
What will we measure after go-live, and from when?
Decide before, because afterwards there is no baseline.
04Capacity
What else is hitting these people this quarter?
Change capacity is the constraint, not budget.
05Sustainment
Who checks in six months?
Usually nobody, which is when reversion happens.
Metrics and KPIs to track
Adoption rate
Share of target users actually using the new process.
Workaround prevalence
Old-path usage still occurring.
Manager engagement
Leaders completing their own enablement.
Support volume
Queries per user, trending down or not.
Benefit realisation
Measured against the case, twelve months out.
Alongside this