Change Management
Learning Objectives
- Define change management and identify the main types of organizational change
- Explain why employees resist change and how managers should interpret resistance
- Apply Lewin's three-stage model and Kotter's eight-step model to a change scenario
- Use the McKinsey 7S framework to diagnose misalignment during a change effort
- Design a stakeholder-aware communication plan for a change initiative
- Identify what makes new behavior "stick" after a change is implemented
Quick Answer
Change management is the planned process of moving individuals, teams, and organizations from a current state to a desired future state — diagnosing the need for change, designing it, communicating it, reducing resistance, building capability, implementing it, and making it stick. Organizations change constantly because of technology, competition, regulation, growth, or crisis, but most change efforts fail not because the technical plan was wrong, but because the human side was treated as an afterthought. Change management matters because it's the difference between a new system that gets adopted and one that gets quietly abandoned for the old spreadsheet six months later. Good change management treats resistance as useful information rather than disobedience to overcome.
Core Concepts
Types of Organizational Change
Definition Organizational change refers to any shift in an organization's strategy, structure, processes, technology, culture, or people, and it typically falls into one or more of these categories.
Explanation
| Type | Meaning | Example |
|---|---|---|
| Strategic change | Change in direction, markets, or business model | Moving from retail-only to omnichannel selling |
| Structural change | Change in roles, reporting, or departments | Creating regional business units |
| Process change | Change in workflow or operating method | New inventory approval process |
| Technological change | New tools, systems, or automation | ERP implementation |
| Cultural change | Change in values, norms, and behavior | Moving from blame culture to learning culture |
| People change | Change in skills, leadership, staffing, or mindset | Training managers to coach rather than command |
Most major changes combine several types at once — a single technology rollout often forces process, role, skill, and culture change simultaneously, which is why it's harder than it looks on paper.
Example A retailer adopting a new point-of-sale system isn't just installing software (technological change) — it's also changing cashier workflows (process change) and possibly store manager reporting lines (structural change).
Real-World Example A manufacturing company introducing an ERP system to integrate purchasing, inventory, production, and finance discovers the technical installation succeeded, but employees kept using spreadsheets anyway — because the "simple" technology change actually required process, skill, and trust changes the rollout plan never addressed.
Why It Matters Misclassifying a change as "just a technology upgrade" when it's really also a culture and process change is one of the most common planning failures — it leads teams to budget training and change resources far too low.
Common Misunderstanding Students often think change types are mutually exclusive categories to pick one from. In practice, identifying all the types embedded in a single initiative is what makes a change plan realistic.
Resistance to Change
Definition Resistance to change is the reluctance or active opposition employees show toward a planned change, driven by identifiable and often legitimate causes rather than simple stubbornness.
Explanation Employees resist because they don't understand the reason for the change, fear job or status loss, lack skills for the new system, distrust leadership, remember past changes that failed, face increased workload during the transition, are still incentivized toward old behavior, face pressure from informal groups, or feel the change threatens their professional identity. Managers should treat resistance as diagnostic information — it often reveals a real design flaw in the change plan, not just a people problem.
Example Warehouse staff resist a new barcode scanning system not because they dislike technology, but because their pay is currently based on units-picked-per-hour, and the new system is slower during the learning curve — the incentive structure, not the technology, is the actual source of resistance.
Real-World Example In the ERP rollout example, employees kept reverting to spreadsheets because they feared mistakes in the new system would be punished, and their supervisors were still requesting the old spreadsheet reports — resistance rooted in fear and misaligned incentives rather than technophobia.
Why It Matters Treating resistance as disobedience leads managers to push harder through mandates, which increases anxiety and drives resistance underground (silent workarounds) rather than resolving it. Listening to resistance often surfaces the exact design fix needed for adoption to succeed.
Common Misunderstanding A common mistake is assuming vocal resisters are the main risk. Often the bigger risk is quiet compliance — employees who never object but simply revert to old habits the moment attention shifts elsewhere.
Lewin's Change Model
Definition Kurt Lewin's model describes change as three sequential stages: unfreezing, changing, and refreezing.
Explanation
| Stage | Meaning | Managerial Action |
|---|---|---|
| Unfreezing | Prepare people to leave old behavior | Explain need, create readiness, challenge old assumptions |
| Changing | Move to new behavior | Train, support, communicate, experiment, solve problems |
| Refreezing | Stabilize the new behavior | Align rewards, systems, routines, and culture |
The model is simple but durable precisely because it names the two stages most change efforts skip: many organizations announce a change without unfreezing first (skipping straight to "changing"), or move on to the next initiative before refreezing, so the new behavior never stabilizes.
Example Before rolling out a new expense-approval process, a finance director spends two weeks showing teams data on how much time the old process wastes (unfreezing) before introducing the new tool.
Real-World Example The ERP company's mistake was effectively skipping refreezing: the technical rollout ("changing") succeeded, but reporting routines, punishments for errors, and manager behavior never shifted to reinforce the new system, so behavior reverted to the old spreadsheets — a textbook failure to refreeze.
Why It Matters Lewin's model explains why "the change didn't take" even when training was completed and the new tool technically works — it's usually a refreezing failure, not a training failure.
Common Misunderstanding Students often treat "changing" as the whole process. In fact, unfreezing and refreezing are where most change management effort should go — the middle stage is often the easiest part.
Kotter's Eight-Step Model
Definition John Kotter's model breaks organizational change into eight sequential steps for building momentum and making change stick.
Explanation
- Create urgency.
- Build a guiding coalition.
- Form a strategic vision.
- Communicate the vision.
- Remove barriers.
- Generate short-term wins.
- Sustain acceleration.
- Anchor the change in culture.
Short-term wins (step 6) matter because change usually feels costly before its benefits appear — visible early progress builds the credibility needed to keep pushing through the harder middle stretch of implementation.
Example A company rolling out a new CRM picks one high-visibility sales team to go live first, publicizes their early productivity gains company-wide (short-term win), and uses that credibility to justify the wider rollout.
Real-World Example In the ERP rollout, a better change plan would have included recognition for the first teams that improved data accuracy — a concrete short-term win — rather than a single company-wide go-live date with no interim milestones to build momentum.
Why It Matters Kotter's steps give managers a specific sequence to audit against when a change stalls: if adoption isn't happening, the diagnosis is often "we skipped step 2 (no coalition) or step 6 (no visible wins)," not "the plan was wrong."
Common Misunderstanding People often treat step 8 (anchoring in culture) as automatic once the other steps are done. It isn't — anchoring requires deliberately updating hiring criteria, promotion decisions, and the stories the organization tells about itself, which is easy to skip.
McKinsey 7S Framework
Definition The 7S framework checks whether seven key organizational elements — strategy, structure, systems, shared values, skills, style, and staff — are aligned around the intended change.
Explanation
| Element | Question |
|---|---|
| Strategy | What direction is the organization pursuing? |
| Structure | How are roles and reporting relationships arranged? |
| Systems | What processes, tools, and routines support work? |
| Shared values | What beliefs guide behavior? |
| Skills | What capabilities are needed? |
| Style | How do leaders behave? |
| Staff | What people and roles are required? |
If a company changes strategy but leaves skills, systems, and rewards unchanged, the change risks becoming symbolic — announced on paper but never actually lived.
Example A retailer announces a "customer-first" strategy, but call-center staff are still measured only on call-handling speed (an unchanged system) — the misalignment between strategy and systems predicts the change will stall.
Real-World Example The ERP company's real-time data strategy failed to change "systems" (supervisors still requested old spreadsheet reports) and "style" (managers didn't visibly use the new ERP data themselves) — a clear 7S misalignment diagnosis.
Why It Matters The 7S framework is a fast diagnostic tool for figuring out why a change effort that looks complete on paper isn't producing real behavior change — it forces a check across all seven elements instead of just the most visible one.
Common Misunderstanding Students often apply 7S only to structural changes. It's equally useful — arguably more useful — for diagnosing why a purely cultural or technological change isn't sticking.
Change Communication and Stakeholder Analysis
Definition Change communication is the ongoing, two-way exchange of information about a change; stakeholder analysis identifies who is affected by a change, what they care about, how much influence they have, and what support they need.
Explanation Effective change communication answers: what is changing, why is it necessary, who is affected, what will not change, what support is available, what is the timeline, how will success be measured, and where employees can ask questions. It is not a one-time announcement — employees need repeated, honest communication throughout the transition. Stakeholder analysis complements this by tailoring the message and support to each group:
| Stakeholder | Possible Concern | Support Needed |
|---|---|---|
| Frontline employees | Workload, skills, job security | Training, clear process, supervisor help |
| Middle managers | Accountability, team resistance | Talking points, authority, coaching |
| Customers | Service disruption | Clear communication and continuity plan |
| Senior leaders | Results and risk | Milestones, dashboards, escalation routes |
| Support functions | System and policy changes | Early involvement and resource planning |
Example Before a merger, HR holds separate briefings for frontline staff (focused on job security and process changes) and middle managers (focused on how to answer their teams' questions), rather than sending one generic all-company memo.
Real-World Example In the ERP case, managers never explained to frontline staff why real-time data mattered — a stakeholder analysis gap that meant frontline employees had no reason to change their behavior beyond compliance, which is a weak motivator.
Why It Matters Change designed from the top without stakeholder analysis routinely misses the daily realities of implementation — the people closest to the work often see problems (workload spikes, incentive conflicts) that leadership doesn't.
Common Misunderstanding Managers often think one well-crafted announcement email counts as "communication." Real change communication is repeated and two-way — it includes listening to questions and concerns, not just broadcasting information once.
Visual Learning
Key Terms
| Term | Definition | Context |
|---|---|---|
| Change management | The planned process of moving people and organizations from a current to a desired future state | Umbrella discipline covering all concepts on this page |
| Unfreezing | Lewin's first stage: preparing people to leave old behavior | Most commonly skipped stage in failed change efforts |
| Refreezing | Lewin's third stage: stabilizing new behavior through systems and rewards | The other commonly skipped stage; without it, old habits return |
| Change agent | A person who actively drives and champions a change effort | Often a member of Kotter's "guiding coalition" |
| Guiding coalition | A cross-functional group of influential people supporting a change (Kotter Step 2) | Needed to give a change credibility beyond one leader's authority |
| Short-term win | Visible, early evidence of progress during a change effort | Builds momentum and credibility (Kotter Step 6) |
| Change readiness | The degree to which people and systems are prepared to begin a change | Includes trust, skills, resources, and emotional willingness |
| 7S framework | McKinsey's model checking alignment of strategy, structure, systems, shared values, skills, style, and staff | Diagnostic tool for why a change effort isn't producing real behavior change |
| Stakeholder analysis | Identifying who is affected by a change and what support each group needs | Prevents change plans designed only from a leadership viewpoint |
| Organizational culture | The shared values, norms, and assumptions guiding behavior in an organization | Anchoring change in culture (Kotter Step 8) is what makes it permanent |
Common Mistakes
-
Misconception: Announcing a change is the same as employees adopting it. Why it's wrong: Adoption requires training, practice, and reinforcement over time — an announcement only creates awareness, not capability or motivation. Correct explanation: Treat the announcement as the start of the unfreezing stage, not the finish line; budget real time and support for the changing and refreezing stages that follow.
-
Misconception: Resistance to change is a discipline problem that should be overridden with authority. Why it's wrong: Resistance frequently points to a legitimate design flaw — misaligned incentives, inadequate training, or valid fears — that mandating compliance doesn't fix and often drives underground. Correct explanation: Treat resistance as diagnostic information first; investigate the cause before deciding whether to adjust the plan or address the concern directly.
-
Misconception: Once a new system or process is technically installed, the change is complete. Why it's wrong: The ERP example shows technical installation succeeding while employees quietly kept using old spreadsheets — the "changing" stage was done, but refreezing (aligned incentives, updated reporting routines, visible leadership use) never happened. Correct explanation: A change is only complete when new behavior is embedded in job descriptions, metrics, rewards, and daily routines — not when the software goes live.
Comparison and Connections
| Model / Concept | Focus | Key Difference | Best Used For |
|---|---|---|---|
| Lewin's 3-stage model | Broad psychological stages of change | Simple, high-level — three phases only | Diagnosing which broad phase a stalled change is stuck in |
| Kotter's 8-step model | Detailed sequence of leadership actions | Granular, action-oriented — gives specific steps to check | Planning and auditing a specific change initiative step by step |
| McKinsey 7S | Structural alignment across seven organizational elements | Diagnostic snapshot, not a sequence — checks alignment at a point in time | Explaining why an announced change isn't producing real behavior change |
| Change management | The overall discipline combining diagnosis, design, communication, and sustaining behavior | Broadest term; the other three are frameworks within it | Umbrella framing for any change initiative |
| Organizational culture change | A cultural shift in values and norms | A type of change (often the hardest and slowest), not a separate discipline | Kotter Step 8 (anchoring) and 7S "shared values" both target this |
Practice Questions
Recall
-
Name Lewin's three stages of change in order. Answer guidance: Unfreezing, changing, refreezing.
-
List four of the eight steps in Kotter's model. Answer guidance: Any four of — create urgency, build a guiding coalition, form a strategic vision, communicate the vision, remove barriers, generate short-term wins, sustain acceleration, anchor the change in culture.
Understanding
-
Explain why "refreezing" is often the most neglected stage of Lewin's model, and what happens when it's skipped. Answer guidance: Organizations move on to the next priority once the visible technical or process change is live; without refreezing (aligned rewards, systems, routines), employees drift back to old behavior, as shown in the ERP example.
-
Why does Kotter emphasize generating short-term wins rather than waiting for the full transformation to show results? Answer guidance: Change usually feels costly (extra training, slower work, disruption) before benefits appear; visible early wins build the credibility and morale needed to sustain effort through the harder middle stretch.
Application
-
A hospital is rolling out a new electronic health records (EHR) system. Nurses have started keeping paper backup notes "just in case." Using Lewin's model, diagnose which stage is failing and propose a fix. Answer guidance: This is likely a refreezing failure (or incomplete unfreezing) — nurses don't trust the new system yet. Fix: address the root distrust (system reliability, error tolerance), align supervisor expectations to stop requesting paper backups, and reinforce EHR-only workflows in performance routines.
-
Using the 7S framework, identify what's misaligned in a company that announces a "collaboration-first" strategy while keeping individual, competitive bonus structures.
Answer guidance: Strategy (collaboration) conflicts with Systems (individual bonuses reward competition), a 7S misalignment that predicts the strategy will remain symbolic until reward systems change.
Analysis
-
Compare a change effort that skips "unfreezing" with one that skips "refreezing." Which failure mode is more likely to look like an initial success and why? Answer guidance: Skipping refreezing looks like success at first — the new behavior/technology is live and adopted in the short term — but reverts later once attention moves elsewhere, as in the ERP example. Skipping unfreezing tends to cause visible resistance immediately, since people haven't been prepared to let go of old behavior.
-
A change management consultant argues that resistance to change should always be minimized as quickly as possible. Evaluate this claim using the concept of resistance as diagnostic information. Answer guidance: A strong answer argues that eliminating resistance quickly (e.g., through mandates) sacrifices the useful information resistance carries — sometimes resistance reveals a genuine flaw (misaligned incentives, inadequate training) that needs fixing rather than suppressing; the better goal is to investigate resistance first, then decide whether to adjust the plan or address the underlying concern.
FAQ
Is Lewin's model outdated compared to Kotter's? No — they operate at different levels of detail. Lewin gives the broad psychological arc (unfreeze, change, refreeze); Kotter gives specific leadership actions within that arc. Many practitioners use both together: Kotter's steps 1-2 map to unfreezing, steps 3-6 to changing, and steps 7-8 to refreezing.
Why do so many change initiatives fail even with good technical plans? Because the technical plan is usually the easy part. Most failures happen in the human elements — resistance not addressed, incentives left unchanged, or the effort declared "done" once the technology is installed but before new behavior is reinforced.
How long should a change effort take before you can call it "sustained"? There's no universal number, but a good signal is whether the new behavior survives a change in attention — if leadership stops actively pushing it and people still do it because it's embedded in metrics, rewards, and routines, it's likely sustained.
Should managers try to eliminate all resistance to change? No. Some resistance reveals legitimate flaws worth fixing. The goal is to understand the source of resistance first — fear, skill gaps, misaligned incentives, valid concerns — and address the cause, not just suppress the symptom.
What's the difference between a change agent and a project manager running a change? A project manager tracks tasks, timelines, and resources for the change initiative. A change agent focuses specifically on building buy-in, communicating the vision, and modeling the new behavior — a project can have both roles, sometimes in the same person.
Quick Revision
- Change management moves organizations from current state to desired future state — diagnosis, design, communication, implementation, sustaining.
- Six change types: strategic, structural, process, technological, cultural, people — most changes combine several.
- Resistance is diagnostic information, not disobedience — common causes: fear, distrust, lack of skills, misaligned incentives.
- Lewin's 3 stages: unfreeze (prepare), change (move), refreeze (stabilize) — refreezing is most often skipped.
- Kotter's 8 steps: urgency, coalition, vision, communicate vision, remove barriers, short-term wins, sustain acceleration, anchor in culture.
- Short-term wins matter because change feels costly before benefits appear.
- McKinsey 7S checks alignment of strategy, structure, systems, shared values, skills, style, staff.
- Change communication must be repeated and two-way, not a single announcement.
- Stakeholder analysis tailors support to frontline staff, managers, customers, leaders, and support functions separately.
- Change sticks only when embedded in job descriptions, metrics, rewards, training, and leadership routines — not when the software just goes live.
- The ERP rollout example shows a technically successful "changing" stage undone by a failed "refreezing" stage.
Related Topics
Prerequisites
Related Topics
Next Topics