A practical guide to people-side change that lands benefits. Models describe individual and organisational journeys. Delivery plans describe what ships when. Keep those ideas joined so you do not run training as a substitute for sponsorship, or declare victory at go-live while habits quietly revert.
MAP-01Change maps
MAP-01
Change maps & methods
Pick the map that matches the adoption problem in front of you.
Civil Service + Universal
Change work mixes individual adoption models, organisational mobilisation methods and benefits discipline. Confusing them creates either endless comms or training dumps. Every framework below answers a different question.
Quiet non-compliance after training: diagnose ADKAR stage before adding more content.
No visible senior energy: fix sponsorship (Kotter coalition) before more emails.
Multi-project transformation: Kotter or MSP at programme level, ADKAR per audience.
Benefits claims without owners: benefits map before more delivery scope.
Government programmes: join readiness and benefits to SRO accountability and Green Book logic.
If a change activity never moves readiness or behaviour, stop performing it.
Titles vary: Change Manager, Organisational Change Lead, Business Readiness Manager, Transformation Partner. The accountability does not. Someone must design the people journey, make sponsorship real, and keep reinforcement alive after launch. If that person is "comms will handle it", you have sponsorship theatre waiting to happen.
Accountability ladder (typical change path)
Coordinator / Analyst: readiness tracking, materials, logistics under coaching.
Change Manager: accountable for adoption plan across impacted groups for a change.
Head of Change / Transformation: owns the profession frame, sponsorship standards and hiring bar.
What you stop and start doing as you grow
You stop doing
Writing every comms email yourself as the only path to quality
Measuring your week by training seats filled
Accepting silent sponsors as normal
You start doing
Coaching sponsors and people managers as the real change network
Publishing readiness and ADKAR diagnostics openly
Measuring your week by behaviour and benefits movement
Three questions to run every day
Is sponsorship visible where resistance is highest? Which ADKAR stage is blocking adoption? What reinforces the new behaviour after go-live?
If any answer is "unclear" for more than a week, that becomes the priority over the next town hall.
Sponsors authorise, prioritise and model. When they are silent, mid-level managers correctly conclude the change is optional. Your job is to make the sponsor role concrete and to escalate sponsorship gaps early.
Sponsor behaviours that move adoption
Behaviour
Looks like
Theatre looks like
Authorise
Removes conflicting priorities in public
Says "this matters" then rewards the old KPI
Align leaders
Coalition tells the same why
Directors give contradictory local messages
Visible support
Shows up in resistance hotspots
Kick-off only, then disappears
Build coalition
Names and backs local champions
Champions unpaid and unsupported
Write a sponsor agreement: decisions they own, cadence, escalation path.
Brief sponsors with options and asks, not essays. Same discipline as Delivery Managers use with SROs.
If sponsorship is weak, say so in readiness reporting. Hiding it is complicity.
In government, connect sponsor duties to SRO accountability so "who owns benefits" is never ambiguous.
Sponsorship theatre is when leaders endorse the change in rooms where nobody can resist, and stay silent where it costs them.
Assess awareness, desire, knowledge, ability, process readiness, data readiness, support readiness and sponsorship strength by audience. Traffic lights without owners are decoration.
Readiness dimensions
Dimension
Strong signal
Weak signal
Awareness
People can explain why in their words
Only the project team knows the narrative
Desire
Managers remove blockers for their teams
Polite nods, no priority shifts
Knowledge
People know what changes for them
Generic "transformation" language only
Ability
Practice in safe environments; support ready
One slideshow the day before go-live
Reinforcement plan
KPIs, recognition and audit aligned
"We'll embed later"
Segment audiences. Global green hides local red.
Every amber/red has an owner, action and date before the next steering group.
Reassess after major delivery shifts; readiness is not a one-off gate.
Share honest readiness with Delivery Manager and Project Manager on one plan.
ADKAR is a diagnostic sequence. People get stuck at different stages. Misdiagnosing the stuck stage wastes money and breeds cynicism. Use it in conversation with managers, not only as a slide label.
Stuck stage to first move
Stuck at
You will hear
First move
Awareness
"I didn't know" / "Why is this happening?"
Clear why from trusted leaders, not only project inbox
Desire
"This won't work" / quiet delay
Address WIIFM, incentives, and sponsor obstacle removal
Knowledge
"I don't know what to do"
Role-based learning, not generic overview
Ability
"I know but I can't"
Practice, coaching, time, usable tools, floor support
Kotter's organisational steps and ADKAR's individual stages rarely sync perfectly. That is normal. Use Kotter for mobilisation energy and ADKAR for precise audience interventions.
Communication builds Awareness and supports Desire. Learning builds Knowledge and Ability. Neither replaces sponsorship. Training-as-change is what happens when the plan is a course catalogue.
Comms altitude
Audience
Lead with
Avoid
Impacted staff
What changes for me, when, support path
Jargon-heavy transformation vision only
People managers
Talking points, FAQs, how to coach resistance
Finding out from their team first
Sponsors / SRO
Readiness RAG, risks, decisions needed
Activity lists without asks
Users / citizens (if public)
Plain language, what works now, where to get help
Internal programme branding
Template · Change comms
Why this, why now: …
What changes for you: …
What stays the same: …
When: … · Support: …
Ask: …
Template · Learning outcome
Role: …
Ability to demonstrate: …
Practice method: …
How we verify Ability: … · Floor support: …
Managers hear before teams. Always.
Prefer short, repeated messages over one giant launch novel.
Build practice into the schedule; watching slides is not Ability.
If the product is hostile, fix UX with design partners; do not train around cruelty.
People resist for rational reasons: workload, identity, broken trust, bad prior changes, missing Desire. Map informal influencers. Bring them in as co-designers where you can. Escalate when resistance is actually a sponsorship or incentive conflict.
Resistance patterns
Surface
Questions in forums
Challenging assumptions
Asking for evidence
Shadow
Polite agreement, no behaviour change
Workarounds protecting the old process
Sarcasm and rumour filling the vacuum
Diagnose ADKAR stage before labelling people difficult.
Use listening sessions with visible response: "you said, we did / we cannot because".
Protect psychological safety for honest amber readiness.
Coalition building is Kotter's early work; do not wait until go-live week.
If the only people excited are the project team, you do not have a coalition. You have an audience.
Reinforcement makes new behaviour easier than old behaviour. Benefits realisation makes outcome claims honest. Without both, the organisation pays for delivery and receives nostalgia.
Reinforcement levers
Lever
Example
Failure mode
Performance measures
KPIs updated to the new process
Old KPIs still rewarded
Recognition
Leaders praise early adopters publicly
Only punish mistakes in the new way
Support & tooling
Floor walkers, office hours, job aids
Support ends on launch day
Consequence design
Old pathway closed on a planned date
Forever dual running with no end
Name benefits owners beyond the delivery team before go-live.
Measure leading indicators of adoption (usage, completion, rework) weekly at first.
Schedule hypercare and a reinforcement review at +30 / +60 / +90 days.
In government, keep benefits evidence aligned to the Management Case and SRO reporting.
Partner with Product Owner and Delivery Manager so backlog after go-live includes adoption fixes, not only new features that ignore reinforcement debt.
Kotter's eight steps describe organisational mobilisation. Bridges' transition model describes the emotional valley as people let go of the old. Delivery managers meet the same dip when transforming ways of working. Name it so sponsors do not abort at the hardest point.
Mobilisation checklist
Urgency is evidence-based, not fear theatre that burns trust.
Guiding coalition has power, credibility and time, not only job titles.
Vision is short enough to repeat; strategies are concrete enough to plan.
Quick wins are real and communicated; fake wins breed cynicism.
Anchor changes in process, systems and culture so they survive sponsor turnover.
In the valley
Expect productivity dips
Increase support and listening
Do not add optional scope
Out of the valley
Celebrate real wins
Close old pathways
Hand reinforcement to BAU owners
The facts do not change between a champion huddle and a board update. The altitude, the framing and the ask do. Change loses trust when it sells false green, or when it dumps anxiety without a path.
Audience calibration
Audience
Detail level
What they want
Impacted teams
High on "me", practical support
Clarity, honesty, time to practice
Managers / champions
Medium, talking points and diagnostics
Tools to lead locally
SRO / board
Low, readiness and benefits risk
Recommendation and a clear ask
Delivery partners
Medium, dependencies and dates
No surprise go-live criteria
Template · Readiness RAG
Status: [RAG] because [single biggest adoption driver]
ADKAR hotspot: audience · stage · evidence
What we are doing: action, owner, date
What we need from you: specific sponsor or decision ask
Template · Sponsor ask
Obstacle: …
Impact on adoption if unresolved: …
Options: A / B / C
Recommendation: … · Decision by: …
Words to drop
Drop
Use
"People are resistant"
"Audience X is stuck at Desire because… First move…"
"Training is done"
"Attendance Y%; Ability verified for Z%; reinforcement plan…"
"We're green for go-live"
"Ready on A/B; amber on C with owner and date; residual risk…"
Under pressure, the instinct is to add more training, more emails or a louder town hall. Diagnose first. Training-as-change and sponsorship theatre are usually symptoms of mis-sequenced ADKAR work or leaders who endorse privately and vanish publicly.
Symptom
Likely cause
First move
Training-as-change
Plan is a course catalogue; Desire unaddressed
Stop adding modules; diagnose ADKAR; fix Desire and sponsorship first
Sponsorship theatre
Leaders endorse in safe rooms only
Write sponsor agreement; put a visible obstacle removal on their calendar this week
Empty training rooms
No Desire, or managers not releasing time
Engage managers; link attendance to priorities sponsors control
Polite green readiness, hostile go-live
Scores softened; shadow resistance
Re-run segmented readiness with anonymity; thank honest amber
Old habits return at +30 days
No Reinforcement; old KPIs still win
Align measures; close dual running; schedule reinforcement review
Benefits not landing
No benefits owner outside project
Name owners and leading indicators before more scope
Delivery and change diverge
Separate plans and RAID
One integrated milestone view with shared go-live criteria
Champions burned out
Unpaid labour, no sponsor backing
Reduce scope; get sponsor recognition and time allocation
Comms ignored
Wrong messenger or too much noise
Switch to trusted local leaders; shorten and repeat
Valley panic from sponsors
Dip not briefed; urgency was fear theatre
Reframe expected dip with data; protect support; freeze optional scope
The one-minute checklist
Name the audience and the adoption risk in one sentence.
Is the pain sponsorship, Desire, Ability, reinforcement or benefits ownership?
Which decision unblocks the most adoption, and who owns it?
Tell the SRO / sponsor before they hear a distorted version.
Protect managers and champions from noise while you sort it.