Mohamed A. Adel.

Change Management

Topic 6 of 12 · In Process Improvement · September 9, 2026

⏱ 1-2 WeeksIntermediate

Master Kotter's 8-step model, ADKAR, Lewin's change model, stakeholder analysis, communication strategies and resistance management for sustaining process improvements.

++++FREE LEARNING PATHPROCESS IMPROVEMENTPROCESS IMPROVEMENT · PHASE 2 · INTERMEDIATECHANGE MANAGEMENTMaster Kotter's 8-step model, ADKAR, Lewin's change…· 2 / 3INTERMEDIATE1-2 WEEKSmotif / archookarcpayoff8147 · 47 · MODULE 4.2

Overview

The best process improvement in the world is worthless if nobody adopts it. Change management is the discipline of guiding people, teams and organizations through transitions so that improvements stick. Studies by Prosci and McKinsey show that projects with excellent change management are six times more likely to meet objectives than those with poor change management.

This topic covers the three most influential change frameworks — Kotter, ADKAR and Lewin — along with the practical skills every improvement practitioner needs: stakeholder analysis, communication planning, resistance management and measuring adoption. You will learn that process improvement is 40 % tools and 60 % people.

Before You Start

  • Complete Root Cause Analysis first so your improvement projects can be argued from evidence rather than opinion.
  • Choose an improvement you have already designed or plan to make; everything in this topic is applied to it.
  • Have a stakeholder list for that change (managers, staff, IT, customers, suppliers) ready to plot on an interest/influence matrix.
  • Re-read the five ADKAR elements so you can diagnose individual readiness gaps quickly during the lesson.
  • Sketch a 1–5 rating or survey you could use to measure adoption at 30, 60 and 90 days after launch.

Learning Objectives

  • Apply Kotter's 8-step model to structure a change initiative
  • Use the ADKAR model to assess and address individual readiness for change
  • Describe Lewin's change model (Unfreeze → Change → Refreeze) and when to use it
  • Conduct a stakeholder analysis to identify supporters, blockers and influencers
  • Design a communication plan with the right messages for the right audiences
  • Develop strategies to manage resistance at individual and organizational levels
  • Measure change adoption using surveys, behavioral metrics and process metrics
  • Identify techniques for sustaining change and preventing regression

Prerequisites

Complete Root Cause Analysis first. You should understand process improvement tools and be ready to learn how to get people to actually use them.

Why Change Management Matters in PI

Process improvement projects fail most often not because of poor analysis or weak solutions — but because people do not adopt the new way of working. Common failure patterns:

  • Implementation without engagement — leadership mandates a new process without involving the people who do the work
  • No reinforcement — the project team moves on and old habits return within weeks
  • Resistance ignored — legitimate concerns are dismissed as "not being on board"
  • Communication vacuum — employees learn about changes through rumors rather than clear, honest messaging

Change management addresses all of these by treating adoption as a structured, planned activity — not an afterthought.

Kotter's 8-Step Model

John Kotter's Leading Change (1996) defines eight sequential steps for leading successful transformation:

  1. Create urgency — help people see why change is necessary NOW. Use data, customer feedback, competitive pressure.
  2. Form a powerful coalition — assemble a group with enough authority, expertise and credibility to lead the change. Not just leaders — include respected informal influencers.
  3. Create a vision for change — a clear, compelling picture of the future state. The vision should be communicable in under 60 seconds.
  4. Communicate the vision — repeat it often, in every forum. Leaders must model the behavior the change requires.
  5. Remove obstacles — identify and eliminate structural, procedural or cultural barriers. This may include updating policies, reallocating resources or changing incentive systems.
  6. Create short-term wins — plan for and celebrate visible, early successes. They build momentum and silence skeptics.
  7. Build on the change — use the credibility from early wins to tackle bigger, harder changes. Do not declare victory too early.
  8. Anchor in culture — embed the new behaviors in hiring, training, performance reviews and organizational norms so they outlast the project team.

ADKAR Model

The ADKAR model (Prosci / Jeffrey Hiatt) focuses on the individual level — what each person needs to successfully change. ADKAR is an acronym:

LetterElementKey Question
AAwarenessDoes this person understand WHY the change is happening?
DDesireDoes this person WANT to participate and support the change?
KKnowledgeDoes this person know HOW to change — the skills, processes and tools?
AAbilityCan this person actually DO it — has the change been practiced and reinforced?
RReinforcementWill this person SUSTAIN the change over time through recognition, feedback and accountability?

ADKAR is diagnostic: if a person is stuck, the model tells you which element is missing. A person who resists may have an Awareness or Desire gap. A person who tries and fails may have a Knowledge or Ability gap.

Lewin's Change Model

Kurt Lewin's three-stage model (1947) is the simplest and most enduring framework for understanding change dynamics:

  1. Unfreeze — prepare the organization for change by breaking down the existing status quo. Create dissatisfaction with the current state, reduce the forces维持ing it, and build psychological readiness.
  2. Change (Transition) — implement the new process, behavior or structure. This is the messy middle where people learn, experiment, make mistakes and gradually adopt.
  3. Refreeze — stabilize the new state by reinforcing new behaviors through policies, incentives, cultural norms and documentation. Prevent regression to old habits.

Lewin pairs naturally with DMAIC: Unfreeze during Define/Measure, Change during Improve, Refreeze during Control.

Stakeholder Analysis

Every process improvement affects people with different levels of interest and influence. A stakeholder analysis maps these people so you can tailor your approach:

  1. Identify everyone affected by the change — employees, managers, customers, suppliers, regulators.
  2. Assess each stakeholder on two dimensions: interest (how much they care) and influence (how much power they have to affect the outcome).
  3. Plot on a 2×2 matrix:
Low InterestHigh Interest
High InfluenceKeep satisfiedManage closely (key players)
Low InfluenceMonitor (minimal effort)Keep informed

Key players need active involvement in design decisions. Keep-satisfied stakeholders need regular updates but not deep involvement. Ignoring high-influence, low-interest stakeholders is the most common mistake — they can quietly block a project.

Communication Strategies

Effective change communication is structured, honest and multi-directional:

  • What to communicate — the burning platform (why), the vision (where), the plan (how), the impact on each person (what's in it for me), and how to get help.
  • When to communicate — early (before the change), often (throughout), and after (to reinforce). Silence creates anxiety; over-communication builds trust.
  • How to communicate — town halls for broad vision, team meetings for specifics, one-on-ones for personal impact, written documentation for reference. Use stories and examples, not just data.
  • Two-way channels — surveys, Q&A sessions, feedback boxes, skip-level meetings. Listening is as important as messaging.

Managing Resistance

Resistance is not the enemy — it is information. People resist for real reasons:

  • Fear of the unknown — they do not know what the change means for their role
  • Loss of competence — they are experts at the current process and feel like beginners again
  • Misaligned incentives — the current reward system may actually punish the desired behavior
  • Past failed changes — "I've seen this movie before; it won't last"
  • Legitimate concerns — the change may genuinely have negative consequences they can see but leadership cannot

Strategies:

  1. Listen first — understand the concern before addressing it
  2. Involve resisters in design — people support what they help create
  3. Address legitimate issues — modify the plan when resistance is based on valid concerns
  4. Provide training and support — reduce the competence gap
  5. Use peer influence — early adopters and respected colleagues are more persuasive than mandates

Measuring Change Adoption

Adoption is not assumed — it must be measured:

  • Adoption surveys — ask employees whether they understand, support and are using the new process (use ADKAR elements as survey dimensions)
  • Behavioral metrics — track whether people are actually performing the new behaviors (e.g., are they using the new checklist? logging into the new system?)
  • Process metrics — are the improvement targets (cycle time, defect rate, cost) actually being met in production?
  • Qualitative feedback — focus groups, interviews and open-ended survey questions reveal why the numbers are what they are

Sustaining Change

Change decays without deliberate reinforcement. Key sustaining mechanisms:

  • Updated standard work — document the new process and retire old documentation
  • Training and onboarding — new employees must learn the new way, not the old way
  • Incentive alignment — ensure performance reviews, bonuses and recognition reward the new behaviors
  • Regular audits — schedule process compliance checks at 30, 60 and 90 days post-implementation
  • Leadership modeling — if managers revert to old habits, everyone will too
  • Celebrate milestones — recognizing the team's effort reinforces that the change was worth it

Hands-On Practice

Take a process improvement you have made (or plan to make) at work or school:

  1. Identify all stakeholders and plot them on an interest/influence matrix.
  2. For each stakeholder group, assess where they fall on the ADKAR model (which element is weakest?).
  3. Design a communication plan: what to say, to whom, when and through which channel.
  4. Identify at least three sources of resistance and develop a response strategy for each.
  5. Define three metrics you would track to measure adoption at 30, 60 and 90 days.
  6. Write a one-page change management plan using Kotter's 8 steps as your structure.

Deeper Worked Examples

These examples push further than the core content — each one is a complete, step-by-step solution you can follow and then reproduce on your own.

Change plan for a spreadsheet-to-tool migration

Problem. A 60-person finance company is switching from shared spreadsheets to a project-management tool in 8 weeks. Three weeks before launch, a survey shows 55% of staff feel 'uncomfortable' and a further 25% are 'neutral'. The two senior partners strongly back the move, but the head of finance is lukewarm about the disruption.
1

Step 1

Run the stakeholder analysis and plot the groups: the partners are high influence with high interest (manage closely), the head of finance is high influence but low interest (keep satisfied), and the 48 staff are lower influence but high interest (keep informed).
2

Step 2

Use the ADKAR model to diagnose gaps: most staff have awareness but lack desire (fear of losing spreadsheet fluency) and knowledge (how to log daily work in the tool); the head of finance shows a desire gap rooted in a genuine worry about month-end data migration.
3

Step 3

Apply Kotter's first three steps: create urgency with a compliance deadline and the visible cost of version conflicts, form a coalition that deliberately includes the head of finance and two trusted power users, then craft a vision that fits in one breath — 'one source of truth that ends the 4 hours of weekly reconciliation'.
4

Step 4

Draft the communication plan: a town hall for the why-now story, one-to-ones with the hesitant third, weekly two-minute video tips, and a named FAQ channel — never talking about the tool without saying what it does for the listener.
5

Step 5

Turn the head of finance's scepticism into a role: put her in charge of testing the data-migration path, converting a blocker into an early owner.
6

Step 6

Define adoption metrics: percentage of weekly tasks actually logged in the tool at weeks 2, 4 and 8, plus a process metric (time to close month-end), and schedule reinforcement audits at 30 and 90 days.

Common Mistakes

  • Treating change management as a separate workstream rather than integrated into the improvement project
  • Communicating only about the change without explaining why it matters to each audience
  • Ignoring resistance — dismissing concerns as 'resistance to change' rather than investigating them
  • Declaring victory too early — celebrating completion instead of sustained adoption
  • Failing to align incentives — if the old behavior is still rewarded, people will revert
  • Not involving the people who do the work in the design of the new process
  • Skipping post-implementation reinforcement — the 90-day cliff is real

Real-World Usage

A manufacturing company implemented a new quality inspection process that reduced defects by 40 % in pilot. However, within 60 days of company-wide rollout, defect rates returned to baseline. Root cause: the inspection process added 3 minutes per unit, and production managers were still being measured solely on throughput. By re-aligning incentives to include a quality score and retraining managers, the improvement was sustained — but only after the costly lesson that measurement systems drive behavior.

Mini Project

Business problem: A mid-size company is switching from email-based task tracking to a project management tool (e.g. Asana or Jira). Leadership wants the switch completed in 8 weeks. Early surveys show 40 % of employees are neutral or resistant.

Objective: Create a complete change management plan for the tool migration.

1

Task 1

Identify all stakeholder groups (management, team leads, individual contributors, IT support) and map them on an interest/influence matrix.
2

Task 2

Use the ADKAR model to assess the change readiness of each group.
3

Task 3

Write a project charter for the change initiative (Kotter's steps 1–3: urgency, coalition, vision).
4

Task 4

Create a communication plan with specific messages, channels and timelines for each stakeholder group.
5

Task 5

List the top 5 anticipated resistance points and develop a response strategy for each.
6

Task 6

Design an adoption measurement plan: surveys at weeks 2, 4, 8; behavioral metrics (tool usage logs); process metrics (task completion time).
7

Task 7

Define reinforcement activities at 30, 60 and 90 days post-launch.
DeliverableWhat it proves
Stakeholder matrixYou can identify and prioritize stakeholders
ADKAR assessmentYou can diagnose individual readiness gaps
Kotter's steps 1–3 planYou can structure the front end of a change initiative
Communication planYou can plan targeted, multi-channel messaging
Resistance response strategiesYou can proactively address barriers
Adoption measurement planYou can track whether the change is actually working
Reinforcement planYou can sustain change beyond the initial launch

Key Takeaways

  • Change management increases the likelihood of improvement projects meeting objectives by up to 6×
  • Kotter's 8 steps provide a sequential framework for leading transformation
  • ADKAR diagnoses individual change readiness across Awareness, Desire, Knowledge, Ability and Reinforcement
  • Lewin's Unfreeze → Change → Refreeze model explains the dynamics of any transition
  • Stakeholder analysis maps interest and influence to prioritize engagement effort
  • Communication must explain WHY it matters to each individual, not just WHAT is changing
  • Resistance is information — listen, involve and address legitimate concerns
  • Measure adoption with surveys, behavioral metrics and process metrics
  • Without reinforcement at 30, 60 and 90 days, most changes revert within 90 days

Key Terms & Glossary

The vocabulary this topic uses, defined the way a working professional would.
TermMeaning
Kotter's modelAn 8-step sequence for leading transformation: create urgency, form a coalition, create a vision, communicate it, remove obstacles, create short-term wins, build on the change, and anchor it in culture.
ADKARProsci's individual change model — Awareness, Desire, Knowledge, Ability, Reinforcement — used to diagnose which element is missing for each person who must change.
Lewin's change modelThe three-stage Unfreeze, Change, Refreeze model describing how the status quo must be loosened, the transition lived through, and the new state stabilised.
Stakeholder matrixA 2x2 plot of interest against influence that sorts people into manage closely, keep satisfied, keep informed and monitor, so engagement effort is spent where it matters.
Burning platformThe compelling, data-backed reason why the change must happen now, without which urgency never forms.
90-day cliffThe research finding that most process changes revert to the old way within about 90 days without deliberate reinforcement such as audits, incentives and updated training.

Learning Resources

These curated sources go deeper than this module: official docs, books, interactive practice, and full courses. Mix them into your routine to go from comfortable to professional.

Leading Change — John Kotter

The foundational book on Kotter's 8-step model and organizational transformation.

Open resource ↗

ADKAR: A Model for Change in Business — Jeffrey Hiatt

The definitive guide to the individual change model used by Prosci worldwide.

Open resource ↗

Prosci Change Management Resources

Research, tools and best practices from the leading change management research organization.

Open resource ↗

Change Management Foundations (LinkedIn Learning)

Practical course on leading and managing organizational change.

Open resource ↗

Switch: How to Change Things When Change Is Hard — Chip & Dan Heath

An accessible, research-backed guide to making change stick at the individual and organizational level.

Open resource ↗

Chapter Quiz

Put this lesson to work: answer the questions below, get instant feedback and a pass/fail score. Score 70% or higher before you move on — that is your gate to the next topic.

Chapter Quiz — Change Management

Kotter's 8 steps, ADKAR, Lewin's model, stakeholder analysis, communication, resistance and the 90-day cliff.

0 / 5

Question 1 of 5

In the ADKAR model, an employee who does not want to change has a gap in which element?

Knowledge Check

Create urgency, form a powerful coalition, create a vision for change, communicate the vision, remove obstacles, create short-term wins, build on the change, and anchor in culture.
A Desire gap means the person does not want to change — they are not convinced it is worth it. A Knowledge gap means they are willing but do not know how. The intervention for Desire is different (engage, show benefits, address concerns) from the intervention for Knowledge (train, provide resources, coach).
When leaders celebrate the launch of a new process rather than its sustained adoption, the reinforcement mechanisms (audits, incentives, training) are not put in place. Without reinforcement, old habits return within 90 days and the improvement is lost.
Resistance often reveals legitimate concerns — the change may have negative consequences for a group, the incentives may not be aligned, or the person may lack the skills needed. Listening to resistance and addressing the root cause is more effective than mandating compliance.
Refreeze corresponds to the Control phase of DMAIC — standardizing the new process, updating documentation, training staff, implementing control charts and aligning incentives to sustain the improvement.

End-of-Topic Exam

Hint: Assign each group a likely interest and influence first, then choose the quadrant-specific treatment.

Model answer: Senior doctors: low interest in the mechanics but high influence over adoption — keep satisfied with executive-level updates and evidence that record-keeping does not slow ward rounds. Ward nurses: high interest (they enter the data) and moderate-to-high influence through daily usage — manage closely, involve them in screen design and give practical clinics. IT team: high interest and high influence — manage closely, meeting weekly with escalation routes. Patients: high interest in their own care but low influence over the system — keep informed with a plain-language leaflet about how electronic records improve safety and access. The common mistake to avoid is treating patients and doctors like the IT team: each quadrant gets a different channel, message and cadence.

Hint: Locate each person on the A-D-K-A-R ladder before choosing the fix.

Model answer: A person who 'does not want to' has a Desire gap (or possibly an Awareness gap underneath it): they may not accept why the shift pattern is changing, or may fear its effect on their life. The intervention is engagement, not training — one-to-one conversations, surfacing the burning platform, addressing their genuine concerns, and involving them in the rota design. A person who 'tries but keeps making mistakes' is willing (Desire is present) but has a Knowledge or Ability gap: they know it is worth doing but do not yet know how, or cannot yet perform it reliably. The intervention there is training, coaching, standard work and supervised practice until ability forms. Prescribing training to the reluctant employee wastes both efforts; prescribing conversation to the struggling employee never closes the skill gap.

Hint: Ask what was still being measured and rewarded at 60 days.

Model answer: The likely cause is that behaviour is driven by what is measured: production managers were still rewarded purely on throughput, and the inspection step added 3 minutes per unit, so managers quietly skipped it to protect their bonus. The failure was misaligned incentives plus missing reinforcement, not a bad solution. The prevention: update standard work and retire the old documents, change the KPI and bonus scheme to include a quality score, retrain and coach managers, schedule compliance audits at 30, 60 and 90 days, have leadership visibly follow the new process, and celebrate early milestones so the change feels worth defending. Without those, the 90-day cliff reclaims almost every gain.

Hint: Each step removes a different kind of barrier — message, structure or norm.

Model answer: Step 4, communicate the vision, is about repetition and modelling: the leader repeating the 60-second vision in every forum until it is common knowledge. Step 5, remove obstacles, is structural: updating policies, reallocating budgets or changing an incentive system that punishes the new behaviour — for example, removing a rule that requires two managers to approve a simple fix. Step 8, anchor in culture, is lasting: folding the new behaviours into hiring criteria, performance reviews and training so they outlive the project. Skipping step 5 dooms change because no amount of inspiring messaging overcomes a structure that actively penalises the desired behaviour; as long as the old incentive stands, rational people return to the old way and the vision collapses.

Next Step

Congratulations — you just finished Change Management. The next topic is Continuous Improvement (Kaizen). Press on when you are ready: it will build directly on what you practiced here.