Change management Study Guide

📖 Core Concepts Change Management – A set of practices that prepare, support, and help people, teams, and whole organizations transition to a new way of working. Organizational Change vs. Change Management – Organizational change looks at what must change (processes, structures, strategy); change management focuses on how people adapt to that change. Drivers of Change – Technology shifts, market pressure, crises, mergers, internal reviews, or restructuring that force a new direction. Resistance – Natural human inertia caused by fear, loss of control, or cultural “saving‑face” norms; it shows up as passive push‑back, overt opposition, or change fatigue. Success Factors – Clear, measurable goals; strong executive sponsorship; transparent communication; training/skill‑upgrading; monitoring & quick adjustments; short‑term wins; cultural anchoring. 📌 Must Remember Lewin’s 3‑Step Model – Unfreeze → Change → Refreeze. Kotter’s 8‑Step Process – Urgency, Guiding Coalition, Vision, Communicate Vision, Empower Action, Short‑Term Wins, Consolidate Gains, Anchor in Culture. ADKAR Elements – Awareness → Desire → Knowledge → Ability → Reinforcement (individual‑level). Rogers’ Adoption Attributes – Relative Advantage, Compatibility, Complexity, Trialability, Observability. Four Types of Change (Balogun & Hope Hailey) – Evolution (slow, incremental), Adaptation (stepwise cultural realignment), Revolution (rapid, large‑scale shift), Reconstruction (forced, reactive). Key Failure Triggers – No executive sponsor, lack of urgency, missing short‑term wins, poor communication, undefined metrics, weak governance, change fatigue. 🔄 Key Processes Lewin Unfreeze Diagnose current state → expose gaps → create a compelling “why”. Implement Change (Lewin/Kotter/ADKAR) Deploy new processes, train staff, provide resources, remove barriers. Refreeze / Sustain Embed new behaviors in policies, reward systems, and culture; monitor compliance. ADKAR Flow for an Individual Awareness of need → Desire to support → Knowledge of how → Ability to act → Reinforcement to lock in. Rogers Diffusion Identify adopter categories → tailor communication to each (Innovators → Laggards). 🔍 Key Comparisons Lewin vs. Kotter Scope: Lewin = 3 broad phases (organizational equilibrium); Kotter = 8 detailed steps (leadership actions). Flexibility: Lewin is cyclical, works for stable environments; Kotter is linear, best for large‑scale transformations. ADKAR vs. Classic Models Focus: ADKAR = individual readiness; Lewin/Kotter = whole‑system change. Application: Use ADKAR when you need to diagnose personal resistance; use Kotter for strategic, top‑down initiatives. Evolution vs. Revolution (Change Speed) Evolution: Slow, incremental, low resistance; Revolution: Rapid, high disruption, requires strong urgency (“burning platform”). ⚠️ Common Misunderstandings “Refreeze” means the change is permanent – In agile contexts, refreeze becomes a new baseline that may be revisited. All eight Kotter steps must be completed sequentially – Real projects often iterate; missing a step (e.g., short‑term wins) is a common cause of failure. ADKAR is a project‑management tool – It is a people‑centric model; it does not prescribe scheduling or budgeting. Change control in project management = change management – Change control manages scope tweaks; change management handles human adoption. 🧠 Mental Models / Intuition “Unfreeze = Melt the Ice” – Imagine a frozen lake; you must warm it enough to crack before you can reshape it. “Burning Platform = Fire Under a Ship” – When the deck is on fire, crew members act quickly; a clear crisis creates urgency. “Short‑Term Wins = Fuel for the Engine” – Early victories generate momentum and validate the effort, preventing fatigue. 🚩 Exceptions & Edge Cases Agile/Lean Environments – The classic “refreeze” may be replaced by continuous cycles of Plan‑Do‑Check‑Act; treat refreeze as a temporary stabilization before the next iteration. Highly Regulated Industries – Change may be constrained by compliance; the “unfreeze” phase often requires formal approvals before any behavioral shift. Cultural Resistance Dominates – If cultural norms (e.g., “saving face”) are strong, even a burning platform may not create urgency without trusted internal champions. 📍 When to Use Which | Situation | Recommended Model/Tool | |-----------|------------------------| | Need rapid, organization‑wide shift (crisis) | Kotter’s 8‑Step + “Burning Platform” narrative | | Focus on individual adoption, training, coaching | ADKAR (assess each element) | | Incremental process improvement | Lewin’s 3‑Step (unfreeze → change → refreeze) or PDCA (Plan‑Do‑Check‑Act) | | Introducing a new technology with clear ROI | Rogers’ Diffusion attributes to craft messaging | | Multiple simultaneous transformations (risk of fatigue) | Prioritize short‑term wins, stagger evolution vs. revolution; apply change fatigue monitoring. | 👀 Patterns to Recognize Repeated “no‑go” statements → early sign of hidden resistance. Stakeholder requests for “more data” → may mask fear of loss of control. Absence of a clear sponsor → predicts governance gaps and likely failure. Mentions of “we’ve done this before” → possible structural resistance imprint. High turnover or absenteeism during rollout → flag for change fatigue. 🗂️ Exam Traps Confusing “change control” (project scope) with “change management” (people) – Look for wording about “people adoption” vs. “scope amendment”. Mix‑up of ADKAR order – Remember the exact sequence: Awareness → Desire → Knowledge → Ability → Reinforcement. Assuming “refreeze” is optional – On exams, if a question asks what’s missing for sustained change, “refreeze” (or its modern equivalent) is usually the right answer. Choosing “Rogers attributes” for a purely cultural change – Rogers focuses on innovation adoption; cultural transformation often needs Kotter or ADKAR. Selecting “Evolution” for a high‑urgency scenario – Evolution is slow; a “burning platform” signals you need Revolution or Reconstruction. --- Use this guide for a quick, confidence‑boosting review right before your exam. Focus on the bolded keywords, match the scenario to the appropriate model, and watch out for the listed traps.