Topic 8.1 — Change Management

In one sentence: Technology and process changes only deliver benefit when the people affected understand, want, are able to make, and sustain the change — so lead the human transition as deliberately as you lead the technical delivery.

Why this matters in health and care#

Most digital health and care programmes that fail do not fail on the technology. They fail because clinicians work around the new system, care workers quietly revert to paper, or the promised benefits never materialize because behaviour never actually changed. The system was delivered; the change was not.

In health and care the stakes are unusually high. Frontline staff are stretched, safety-conscious, and rightly sceptical of change imposed from above — they have seen systems come and go. A poorly led change can compromise patient safety directly (through workarounds and errors), demoralize a fragile workforce, and destroy the trust needed for the next change. Public money spent on a system nobody adopts is money wasted twice.

Change management is the discipline that closes the gap between a solution being available and it being adopted, embedded, and sustained. It is the essential partner to phasing in innovation (see Topic 8.0 — Phasing in Innovation) and to organizational development (see Topic 7.5 — People & Organizational Development). This topic gives you the frameworks and the practices to lead people through change without breaking them.

Core concepts#

Kotter's 8 steps. John Kotter's model, from Leading Change, is a top-down, leadership-driven sequence for large organizational change: (1) create a sense of urgency, (2) build a guiding coalition, (3) form a strategic vision, (4) enlist a volunteer army, (5) enable action by removing barriers, (6) generate short-term wins, (7) sustain acceleration, and (8) institute change in the culture. Kotter's strength is programme-level structure and momentum.

Prosci ADKAR. ADKAR is a people-centred model describing the five things an individual must experience for change to stick: Awareness of the need, Desire to participate, Knowledge of how, Ability to do it, and Reinforcement to sustain it. Its power is diagnostic — if adoption is stalling, you can identify which element is missing for a given group and target the fix. Kotter structures the programme; ADKAR guides the person-level communications, training, and coaching. The two are complementary, not competing.

Bridges' Transition Model. William Bridges distinguishes change (the external event) from transition (the internal, psychological process people go through). His three phases — the Ending (letting go of the old way, with its associated loss), the Neutral Zone (a disorienting in-between where the old is gone but the new is not yet fluent), and the New Beginning — remind leaders that resistance is often grief, and that the Neutral Zone is where performance dips and needs the most support.

Stakeholder analysis. A structured map of who is affected, their influence, their interest, and their current stance, used to target engagement effort. Not everyone needs the same treatment: high-influence, currently-sceptical clinicians need very different handling from low-influence, already-enthusiastic staff.

Benefits realization. Change is not done when the system goes live; it is done when the intended benefits are measurably achieved. Benefits realization links each change to a named benefit, an owner, a baseline, and a tracking cadence — closing the loop that phasing in innovation opened.

Best practices#

1. Establish a genuine, honest case for change. Kotter's urgency must be real, not manufactured. Articulate the problem in terms frontline staff recognize — patient safety, their own workload, waiting times — with evidence, and be candid about what is not working today. Fabricated urgency is quickly detected and breeds cynicism.

2. Build a guiding coalition that includes clinical and frontline credibility. A change sponsored only by executives and IT will be seen as done to staff. Recruit respected clinicians, nurses, care workers, and administrators as visible advocates — Kotter's "guiding coalition" and "volunteer army" — because peers persuade peers far more effectively than hierarchy does.

3. Engage frontline staff early, as co-designers not recipients. The people who will use a system daily know where it will break. Involve them in design and testing before go-live, and act visibly on what they tell you. Early, authentic engagement converts potential resisters into owners and surfaces safety issues while they are still cheap to fix.

4. Diagnose resistance with ADKAR before you respond to it. Resistance is information, not defiance. Use ADKAR to locate the true blocker: is it awareness (people don't understand why), desire (they understand but won't), knowledge (they want to but don't know how), or ability (they know but can't in their real workflow)? Each demands a different intervention; blanket "more communication" wastes effort on the wrong gap.

5. Manage the transition, not just the change. Use Bridges' model to name the loss honestly, support people through the Neutral Zone with extra help, floorwalkers, and tolerance of a temporary productivity dip, and mark the New Beginning. Expect performance to fall before it rises, and resource for it rather than panicking.

6. Communicate relentlessly, in both directions. Repetition and multiple channels beat a single grand announcement; people need to hear a message several times, from several sources, before it lands. Equally, build listening channels — staff surveys, drop-ins, feedback loops — so communication is dialogue, not broadcast.

7. Generate and celebrate short-term wins. Long change programmes lose energy. Deliberately engineer early, visible, credible wins — a ward that saves time, a clinician who champions a real improvement — to prove the change works and sustain momentum, exactly as Kotter prescribes.

8. In unionized and partnership environments, change with staff, not around them. In the NHS, work through the social partnership model: engage trade unions and staff-side representatives early via the Social Partnership Forum approach, so that service change is co-created rather than imposed. Partnership working is not a constraint to route around — it is a route to more durable change and it is a statutory and cultural expectation.

9. Embed and sustain — plan reinforcement from the start. The ADKAR "R" and Kotter's step 8 are about permanence: update policies, job descriptions, training induction, and audit so the new way becomes "how we do things here". Withdraw the old system decisively; a live fallback guarantees reversion. Assign a named owner for sustainability past go-live.

10. Close the loop with benefits realization and adoption metrics. Measure adoption directly — logins, feature use, workaround rates, staff and patient experience — against the baseline, and track the benefits the change promised. Report them honestly, including where benefits are behind plan, so the organization learns and the next change is better led.

Questions to discuss with your team#

1. When adoption of our last big system stalled, which ADKAR element was actually missing — and did we diagnose it, or just send more communications? This question turns an abstract framework into an honest post-mortem of your own track record, which is where the real learning sits. In health and care, resistance from stretched, safety-conscious frontline staff is easy to mislabel as defiance and answer with yet more awareness messaging — posters, town halls, a fresh email — when the true blocker is often ability, because the new system slows clinicians during a ward round or does not fit the real workflow. The discussion should force the team to distinguish awareness (people do not understand why), desire (they understand but will not), knowledge (they want to but do not know how), and ability (they know but cannot in practice), and to be specific about which one bit last time. A good answer draws on actual evidence — staff surveys, workaround observations, super-user feedback — rather than leadership assumption, and it accepts that blanket "more communication" is usually effort spent on the wrong gap. The most valuable version of this conversation identifies a current change where the team is about to make exactly that mistake again, and redirects the intervention to the element that is genuinely missing.

2. Are we honestly planning and resourcing for the productivity dip, or are we quietly assuming go-live is the finish line? Bridges' Neutral Zone — the disorienting period after the old way is gone but the new is not yet fluent — is where performance predictably falls, and in a safety-critical care setting the temptation to panic, blame staff, or reach for the old system is dangerous. The tension to debate is uncomfortable because it means budgeting explicitly for a temporary drop in output: floorwalkers, extra staffing, lighter caseloads in the first days, and tolerance from leaders who are themselves under pressure to show immediate benefit. A serious discussion confronts whether the organization treats go-live as victory — declaring success at deployment while behaviour has not yet changed — and whether there is a named owner for adoption and benefits past the launch date. It should also examine the decommissioning question: is the old system being decisively retired on an agreed date, or left running as a fallback that guarantees reversion? An honest answer names the expected dip, resources it, resists blaming the frontline for early slowness, and commits to tracking real adoption metrics rather than assuming the system delivers benefit merely because it is live.

3. Are we changing with our staff and their representatives, or around them — and would they agree with our answer? In the NHS and wider care system, partnership working with trade unions and staff-side representatives is a statutory and cultural expectation, not a courtesy, and a change imposed from above by executives and IT will be seen as done to the frontline. The debate should test the honesty of the coalition: does it include respected, practising clinicians and care workers as visible advocates, or is it sponsored only by the board and the CIO? It should confront whether staff are engaged early as co-designers who can surface where a system will break and where safety risks hide, or consulted late once decisions are effectively made. There is a genuine trade-off to discuss — early, authentic engagement and partnership are slower and can feel like ceding control, but they convert resisters into owners and produce far more durable change than hierarchy can impose. A good answer is candid about which groups feel change is happening around them, engages staff-side through the social partnership model before rather than after key decisions, and is willing to be judged by whether frontline staff themselves would call the process genuine.

4. How many simultaneous changes are we asking the same frontline team to absorb right now, and who is looking at the total load rather than each programme in isolation? Every programme tends to believe its own change is the priority, but the clinician or care worker on the ward experiences the cumulative weight of all of them at once — a new ePMA system, a restructured rota, a fresh safety mandate and an estates move can land in the same quarter, and change fatigue is a genuine cause of adoption failure that no single Kotter sequence will fix. The tension worth surfacing is organizational: change is usually governed programme-by-programme, so nobody owns the aggregate demand on a given team, and the honest question is whether anyone in the room can even name the full portfolio hitting the frontline this year. A serious discussion weighs sequencing and pacing against the pressure to deliver everything now, and asks whether some changes should be deliberately slowed, bundled, or stopped to protect the capacity of the people expected to adopt them. It should also examine who holds the authority to say "not yet" across programmes, because without that role the default is overload. An honest answer maps the real change load on key groups, accepts that prioritizing means some worthwhile initiatives wait, and names an owner for the cumulative pace rather than assuming each programme's local plan adds up to something humane.

5. When frontline staff build workarounds to our new system, do we treat them as a compliance problem to stamp out or as a safety signal to learn from? Workarounds are one of the most reliable pieces of intelligence a change programme receives, because they show precisely where the designed workflow collides with the reality of care — yet the instinctive response is often to police them as non-compliance rather than to ask what unmet need they solve. In a safety-critical setting this instinct is dangerous: a nurse who keeps a paper list beside the electronic system may be compensating for a genuine gap that, left unexamined, becomes the root cause of a medication error. The discussion should confront the uncomfortable trade-off between standardization and local adaptation — some workarounds are drift that erodes safety and must be closed, while others are frontline wisdom that should be designed back into the system — and the team needs an honest way to tell the two apart rather than defaulting to either blanket enforcement or blanket tolerance. It should ask whether there is a real, blame-free channel for staff to report why they are deviating, and whether anyone acts on what comes back. A good answer treats workaround rates as a leading adoption metric, investigates the reasons before judging them, and can point to at least one case where a workaround changed the design rather than triggering a reprimand.

6. What happens to this change when the programme funding ends and the dedicated team disbands — who owns it as business as usual? Change programmes are resourced as temporary endeavours, but adoption has to be sustained indefinitely, and the moment of greatest risk is often not go-live but the quieter point when the project team moves on, the backfill money stops and the change has to survive on the ordinary operational line. The ADKAR "R" and Kotter's eighth step both point here, yet reinforcement is the element most easily cut when budgets tighten, so the honest question is whether the new way is genuinely embedded in policy, job descriptions, induction, audit and appraisal, or whether it is still being propped up by champions whose protected time is about to vanish. The tension to debate is that sustainability work is unglamorous and competes with the next exciting programme for attention and money, so it is chronically under-resourced despite being where benefits are actually retained or lost. The team should identify who the named operational owner is once the programme closes, and whether that person has the authority and capacity to hold the line. A good answer can point to concrete mechanisms that outlast the funding — the old process decommissioned, the new one written into how people are trained and assessed — rather than relying on goodwill and heroics that fade within a year.

In practice: a health & care example#

An acute trust is replacing paper drug charts with electronic prescribing and medicines administration (ePMA). The programme director knows the technology is the easy part.

She builds a guiding coalition co-chaired by a respected consultant and the chief nurse, not the CIO alone, and creates a network of ward-based "digital champions" — practising nurses and pharmacists given time to support peers. A stakeholder analysis identifies night-shift staff and locum doctors as high-risk, low-engagement groups, so extra effort is targeted there.

Using ADKAR, early staff surveys reveal the blocker is not awareness (everyone knows paper charts cause errors) but ability — clinicians fear the new system will slow them during ward rounds. The response is workflow-specific training and floorwalkers at go-live, not more posters. Bridges' Neutral Zone is planned for explicitly: the trust accepts and staffs for a two-week productivity dip, keeps prescribing volumes light in the first days, and resists the temptation to blame staff for early slowness.

Change runs in partnership: staff-side representatives are engaged from the outset on shift and workload impacts through the trust's partnership forum, avoiding a dispute that could have derailed go-live. Early wins — a ward reporting fewer transcription errors within a fortnight — are publicized. Paper charts are formally retired on an agreed date so there is no fallback to revert to. Afterwards, benefits realization tracks medication error rates and administration timeliness against baseline, and the results feed the trust's wider digital roadmap.

Sector lenses#

Startup#

In a small digital-health company the "change" being managed is usually your customer's, not your own: your product lands on a ward or in a GP practice, and its adoption depends on how well the buying organization leads its people through Kotter's steps and the ADKAR journey. The startup's leverage is design and enablement — build the change into the product (in-app guidance, low-friction onboarding, floorwalker-ready training materials) so that Awareness, Knowledge, and Ability are cheap for the adopter to reach. With no in-house change team and thin margins, founders often have to coach the customer's champions directly and treat implementation support as part of the offer, not an add-on. Internally, the startup's own change is fast and informal, but it should still name the loss when it pivots, because even a ten-person team hits Bridges' Neutral Zone. The trap is shipping software and assuming behaviour follows; a stalled adoption at a reference site is both a lost renewal and lost evidence.

Small business#

An established small provider — a GP practice, a community pharmacy, a care home, a domiciliary-care agency or a single-site clinic — has to lead the same human transition as a large trust but with none of the apparatus: no change manager, no training team, often no dedicated IT at all, and a partner or registered manager running the change on top of a clinical or operational day job. The frameworks still apply, but they must be radically compressed: the "guiding coalition" may be the practice manager and one enthusiastic nurse, and the ADKAR journey has to be led in staff-meeting slots and over shoulders rather than through a communications plan. Cash is tight and every hour a receptionist or carer spends learning a new system is an hour taken from patients, so the Neutral Zone dip is felt immediately on the bottom line and there is little slack to absorb it — sequencing the change to a quieter period and leaning hard on the supplier's onboarding support matters more here than anywhere. The same regulatory and safety duties (CQC expectations, information governance) apply as to big organizations, without the resources to meet them, so a small provider should be ruthless about adopting supplier defaults and proven templates rather than designing its own. The advantage is intimacy: with a handful of staff who all know each other, resistance is visible early and a credible owner can carry the whole team through the change personally.

Enterprise#

A large trust or ICS is where the full apparatus earns its keep: a guiding coalition with clinical credibility, a formal stakeholder analysis, structured ADKAR diagnosis, planned Neutral-Zone support, and measured employee engagement all matter because the change touches thousands of staff across professions and sites. Scale brings resources (dedicated change managers, training teams, communications functions) but also inertia, competing programmes, and change fatigue from too many simultaneous go-lives. Accountability is formal — a senior responsible owner, a benefits-realization plan, board-level reporting — and partnership working with trade unions is a genuine statutory and cultural expectation, not a courtesy. The enterprise's risk is treating change as a workstream owned by the programme office rather than by operational leaders, so adoption is "managed" on paper while the frontline works around the system. Its advantage is that, done well, it can sustain and embed change through policy, audit, and induction in a way smaller organizations cannot.

Government#

A national or local public body — NHS England, DHSC, a devolved administration, or a local authority — rarely manages change at the level of an individual ward; it shapes the conditions under which hundreds of organizations manage their own. Its instruments are policy, funding, national communications, standards, and the social-partnership machinery (the Social Partnership Forum) that keeps system-wide change legitimate with staff and unions. Accountability runs to ministers, Parliament, and the public, so government-led change is highly visible, politically sensitive, and slow to reverse — a botched national rollout damages trust for years and invites audit. It must lead change across a federated system it does not directly line-manage, relying on incentives, mandates, and persuasion rather than command, which makes coalition-building and honest cases for change even more important than inside a single trust. Its proper role is to reduce the friction of local change — funding backfill for training, publishing reusable playbooks, and protecting the time frontline transformation needs.

Common failure modes#

• Go-live treated as the finish line. Declaring victory at deployment, before behaviour changes. Avoid it by owning adoption and benefits past go-live.
• Manufactured urgency. A burning platform staff don't believe in, breeding cynicism. Avoid it by grounding the case for change in evidence staff recognize.
• Executive-only sponsorship. Change seen as done to the frontline. Avoid it by building a clinically credible coalition and champions.
• Treating all resistance the same. Answering an ability gap with more awareness messaging. Avoid it by diagnosing with ADKAR first.
• Ignoring the Neutral Zone. Panicking at the inevitable early dip and blaming staff. Avoid it by planning and resourcing the transition dip.
• Bypassing partnership. Imposing change without unions/staff-side, triggering disputes. Avoid it by engaging via the social partnership model early.
• A live fallback to the old way. Leaving the old system running so staff revert. Avoid it by decommissioning the old process on an agreed date.

Maturity model#

Checklist#

• The case for change is honest, evidenced, and framed in terms staff recognize.
• A guiding coalition includes credible clinical and frontline voices.
• A stakeholder analysis targets engagement by influence and stance.
• Frontline staff co-design and test the change before go-live.
• Resistance is diagnosed with ADKAR before interventions are chosen.
• The Bridges Neutral Zone (productivity dip) is planned and resourced.
• Communication is two-way, repeated, and multi-channel.
• Short-term wins are engineered and celebrated.
• Unions/staff-side are engaged early through the social partnership model.
• Reinforcement (policy, training, audit) and a sustainability owner are in place.
• The old system/process is decommissioned on an agreed date.
• Adoption metrics and benefits realization are tracked against baseline and reported.

Key sources#

• John P. Kotter, Leading Change — the 8-step model for organisational change.
• Prosci, ADKAR model — Awareness, Desire, Knowledge, Ability, Reinforcement (prosci.com).
• William Bridges, Managing Transitions — change vs transition and the three-phase model.
• Social Partnership Forum — partnership working and staff engagement in NHS service change (socialpartnershipforum.org; gov.uk).
• NHS Employers — staff engagement and its link to organisational effectiveness and patient care (nhsemployers.org).
• Managing Successful Programmes (MSP) — benefits management and realisation within programme delivery.
• The King's Fund — leadership and organisational change in health and care (kingsfund.org.uk).
• See also Topic 8.0 — Phasing in Innovation, and Topic 7.5 — People & Organisational Development.

References#

1. Change management — Wikipedia — https://en.wikipedia.org/wiki/Change_management
2. John Kotter — Wikipedia — https://en.wikipedia.org/wiki/John_Kotter
3. William Bridges (author) — Wikipedia — https://en.wikipedia.org/wiki/William_Bridges_(author)
4. Stakeholder analysis — Wikipedia — https://en.wikipedia.org/wiki/Stakeholder_analysis
5. Benefits Realisation Management — Wikipedia — https://en.wikipedia.org/wiki/Benefits_realisation_management
6. Electronic prescribing — Wikipedia — https://en.wikipedia.org/wiki/Electronic_prescribing
7. Trade union — Wikipedia — https://en.wikipedia.org/wiki/Trade_union
8. Employee engagement — Wikipedia — https://en.wikipedia.org/wiki/Employee_engagement
9. Leading Change — John P. Kotter, Harvard Business Review Press (2012), ISBN 978-1422186435
10. The Prosci ADKAR Model — Prosci — https://www.prosci.com/methodology/adkar
11. Managing Transitions: Making the Most of Change — William Bridges & Susan Bridges, Da Capo Press, ISBN 978-0738219653
12. Social Partnership Forum — https://www.socialpartnershipforum.org/
13. Staff engagement — NHS Employers — https://www.nhsemployers.org/topics/retention-and-staff-experience
14. Managing Successful Programmes (MSP) — Axelos/PeopleCert — https://www.axelos.com/certifications/propath/msp-programme-management
15. Leadership and organisational change — The King's Fund — https://www.kingsfund.org.uk/