What is a Change Model?
A change model is a structured framework that guides an organization through a planned transformation, from naming the problem to embedding the new way of working. Models like Lewin, ADKAR, Kotter, and McKinsey 7-S each prescribe a sequence of steps, roles, and checkpoints designed to reduce resistance and lift the probability of a successful rollout.
- Definition first: A change model is a repeatable, step-by-step framework that takes an organization from current state to a stabilized new state.
- Four dominate practice: Lewin (3 steps), ADKAR (5 individual stages), Kotter (8 organizational steps), and McKinsey 7-S (alignment of 7 elements) cover most enterprise rollouts.
- Failure is the baseline: Roughly 70% of change initiatives fall short of their goals, and a model is the single biggest lever to shift those odds (McKinsey, 2015).
- Pick by change type, not popularity: Use ADKAR for behavior change, Kotter for transformational shifts, Lewin for discrete process changes, and 7-S for structural realignment.
Definition: A change model is a framework or methodology that guides organizations through the process of organizational change. These models provide structured approaches and best practices to ensure successful transformation.
Why change models raise the odds of a successful rollout
Change models raise success rates by replacing improvised launches with a sequenced plan that names sponsors, milestones, and feedback loops.
McKinsey research published in 2015 found that 70% of change programs fail, with employee resistance and lack of management support cited as the top two drivers (McKinsey, 2015). A model attacks both directly: it forces leaders to align stakeholders early, communicate the why, and stage the rollout in checkpoints that surface resistance before it compounds.
The pressure is not easing. In a July 2024 Gartner survey of 473 HR leaders, 73% said their employees were fatigued from change and 74% said their managers were not equipped to lead it (Gartner, 2024). A model gives both groups a shared vocabulary and a predictable cadence, which is what reduces fatigue more than the change itself.
The four change models most enterprises actually use
Four change models cover the vast majority of enterprise rollouts, and each is designed for a different type of change.
The differences are not stylistic; they determine whether the model fits your situation.
Model | Number of steps | Primary focus | Best fit for |
|---|---|---|---|
Lewin's Change Management Model | 3 (Unfreeze, Change, Refreeze) | Process and state transition | Discrete process or policy changes |
ADKAR Model | 5 (Awareness, Desire, Knowledge, Ability, Reinforcement) | Individual behavior change | People-driven adoption, training rollouts |
Kotter's 8-Step Model | 8 (Urgency → Anchoring) | Organization-wide transformation | Large-scale strategic shifts and culture change |
McKinsey 7-S Model | 7 elements (Strategy, Structure, Systems, Shared Values, Style, Staff, Skills) | Organizational alignment | Restructuring, M&A integration, strategy execution |
- Lewin's Change Management Model: Three steps, Unfreeze, Change, and Refreeze, that emphasize preparation and stabilization. Originally proposed by Kurt Lewin in 1947, it remains the conceptual base for most newer models.
- ADKAR Model: Awareness, Desire, Knowledge, Ability, and Reinforcement. Created by Prosci founder Jeff Hiatt in 2003, ADKAR is built on the premise that organizations only change one person at a time.
- Kotter's 8-Step Change Model: Eight sequential steps from creating urgency to anchoring change in the culture, drawn from John Kotter's 1995 HBR article and 1996 book Leading Change. It pairs with a clear vision and visible coalition.
- McKinsey 7-S Model: Assesses and aligns seven elements: strategy, structure, systems, shared values, style, staff, and skills. Best used as a diagnostic before picking a process-oriented model.
What every effective change model includes
Every effective change model, regardless of step count, includes six recurring components. If your chosen framework lacks one, treat that as a gap to fill rather than a deliberate omission.
- Vision: A specific picture of the future state, not a slogan.
- Leadership: Named, visible sponsors who carry the change in calendars and budget decisions, not just speeches.
- Communication: Transparent, repeating communication calibrated to each stakeholder group.
- Stakeholder engagement: Active involvement of affected parties in shaping the change, not only receiving it.
- Training and support: Resources for new skills, plus accessible help during the transition.
- Measurement and evaluation: Leading and lagging indicators tied to the original vision, reviewed on a fixed cadence.
Where change model rollouts typically break
Change model rollouts most often fail at four predictable points, and the model itself is rarely the cause.
The breakage is in how it is applied.
- Resistance to change: Employees default to skepticism when the "why" is unclear. ADKAR's Awareness and Desire stages exist for exactly this reason and are the most-skipped steps in practice.
- Absentee leadership: Sponsors who delegate visible advocacy to a project team rather than carrying it themselves. Kotter's Step 2 (building a guiding coalition) directly addresses this.
- Single-broadcast communication: A launch email and one all-hands does not equal communication. Effective rollouts repeat the core message at least 7 to 10 times through varied channels.
- Resource starvation: Time, budget, and headcount allocated to "business as usual" while the change runs as a side project.
- Cultural collisions: A change that contradicts existing core values or rituals without naming the contradiction will be quietly resisted regardless of executive support.
How to apply a change model in practice
To apply a change model successfully, six practices consistently separate the rollouts that stick from those that revert.
- Lock in executive sponsorship before launch. A sponsor who only signs the budget is not a sponsor. They need to show up in town halls and unblock decisions.
- Build a guiding coalition. A cross-functional group with formal authority and informal credibility, scaled to the size of the change.
- Translate vision into a concrete plan. Pair the picture of the future state with the milestones, owners, and metrics that will get you there. OKRs are a natural fit for tracking transformation goals.
- Communicate often, in multiple formats. Repeat the why, the what, and the what-changes-for-you. Use written, spoken, and visual channels.
- Equip people, then trust them. Training before the change goes live, supported by accessible help during the transition.
- Run a tight feedback loop. Weekly or biweekly retros during the change window, with explicit permission to adjust tactics without abandoning the vision.
How three large companies used change models
The named examples below illustrate which model fits which type of change, based on widely reported case material.
- Procter & Gamble: Applied Kotter's 8-Step Change Model to consolidate operations and integrate new technologies, treating the rollout as an organization-wide transformation rather than a series of departmental projects.
- Microsoft: Used the ADKAR Model during its shift from packaged software to cloud services, leaning on the model's individual-adoption focus to manage employee transition into new product and engineering practices.
- General Electric: Has historically applied Lewin's Change Management Model across multiple strategic shifts, using the Unfreeze-Change-Refreeze framing for repeated discrete transitions in business unit structure.
Picking a change model for your next initiative
The right model depends on the type of change, not on which framework is most cited. As a starting heuristic:
- Behavior or adoption change (new tool, new process for end users) → ADKAR
- Discrete state transition (org structure tweak, policy update) → Lewin
- Large-scale strategic or cultural transformation → Kotter
- Diagnosis before restructuring or post-merger integration → McKinsey 7-S
Most mature transformation programs combine two: McKinsey 7-S as a diagnostic, then Kotter or ADKAR as the execution framework.
Pair whichever you pick with a strategy execution cadence so the change shows up in quarterly planning, not only in a separate "change management" workstream. Treat it as a living plan: as digital, hybrid-work, and data-driven realities reshape how teams operate, expect to revisit the model's assumptions every cycle and combine it with more adaptable approaches when the context demands.
