Change Management Models: 7 Frameworks and When to Use Them

Key Takeaways

• Organizational change comes in three types, developmental, transitional, and transformational, and the right model depends on which one you're managing.
• Lightweight models like PDCA and Lewin's fit small, contained changes. McKinsey 7-S and ADKAR fit system or process replacements. Kotter's, Satir's, and the Kübler-Ross curve fit large-scale, identity-level transformations.
• No single model is universally best. Many transitions combine models that address different aspects of the same change, such as pairing an organizational model with an individual-adoption model.
• A shared system for tracking change plans, tasks, and outcomes matters as much as the model itself, especially once an initiative spans multiple teams.

Organizational change falls on a spectrum: from small process tweaks to company-wide transformations. Where a change sits on that spectrum determines how much management it needs. The level of management, by extension, determines the change management framework teams use to manage it.

This guide helps you choose the right framework to manage change at your organization. It maps seven widely used change management models to the three types of organizational change they fit best: developmental, transitional, and transformational. For each model, you'll find what it does well, where it falls short, and how to apply it in practice. A comparison table and guidance on combining models cover projects that don't sit neatly in one category.

What Are Change Management Models?

Change management models are structured frameworks that guide how an organization plans, implements, and sustains change.

Some lay out steps in order, like Kotter's 8-step process or Lewin's unfreeze-change-refreeze sequence. Others describe how people react to change or diagnose where it will meet friction. All of them help leaders move people and processes from a current state to a desired one.

Organizations use these models for the same reason they use any framework: consistency. Without one, change happens unevenly. One team communicates well and gets buy-in; another rolls out the same initiative with no warning and spends months managing the fallout. A shared model gives every project the same baseline discipline, so no team has to improvise its own response.

The Three Types of Organizational Change

Most organizational change falls into one of three types: developmental, transitional, or transformational. The types differ in scope, frequency, risk, and how much resistance they create, and those differences decide which change management model fits.

Developmental change

Developmental change is an incremental improvement to an existing process or procedure. It's sometimes called adaptive change, and teams encounter it more often than the other two types. Because it builds on systems people already rely on, it carries low risk and meets little resistance. Most day-to-day process improvement falls into this category.

Example: A distribution company adds automated reorder alerts to its existing inventory system. The warehouse team keeps working the same way and sees fewer stockouts. Nothing gets replaced, so there's little to push back on.

Transitional change

Transitional change replaces an existing system, process, or structure with something new. The organization's purpose stays the same, but how the work gets done changes, often requiring new tools, new skills, or both. It happens less often than developmental change and creates more friction, because people have to give up something familiar before the new way has proven itself.

Example: A professional services firm moves project tracking from spreadsheets to a centralized platform. Client work continues, but managers need training, reporting has to be rebuilt, and the old spreadsheets must be retired so the team doesn't end up running two systems in parallel.

Transformational change

Transformational change redefines what an organization does or how it operates. It often reshapes strategy, structure, and culture at once, and few systems come through unchanged. It's the rarest of the three types, the most disruptive, and the riskiest.

Example: In 1998, Amazon expanded beyond books into music and video, the first step toward selling almost everything. People who joined an online bookstore had to become e-commerce generalists, and the company's systems, supply chain, and identity changed along with them.

Developmental vs. transitional vs. transformational change

Developmental, transitional, and transformational change each need a different level of structure, which is why the models below are grouped by type.

Best Change Management Models for Developmental Change

Frequent, low-risk changes call for models that move quickly and don't require a full organizational mobilization.

PDCA (Plan-Do-Check-Act)

Overview: PDCA originated in quality management and was popularized by W. Edwards Deming. It's a four-stage cycle for testing and refining a change before rolling it out fully: plan the change, do it on a small scale, check the results, and act on what you learned, either standardizing the change or adjusting and cycling through again.

Best use cases: PDCA fits developmental change better than almost any other model here because it's built for exactly that: small, iterative, low-risk adjustments to an existing process. NIST's Manufacturing Extension Partnership, which works directly with small and midsize manufacturers on process improvement, reports that continuous improvement and cost reduction remain the most commonly cited operational challenge among the manufacturers it serves. That's the ongoing, incremental work PDCA is built to support.

Strengths and limitations: The cycle is fast, low-risk, and easy for teams to run repeatedly without executive sponsorship. It isn't designed for changes that require cultural buy-in or coordination across departments, since you can't practically test a restructuring on a subset of employees the way you'd test a production line.

Practical application: A manufacturer tests a new inspection checkpoint on one production line, tracks defect rates for two weeks, then decides whether to scale it plant-wide based on what the data shows. The scale stays small until the data supports expanding it.

Lewin's Change Management Model

Overview: Kurt Lewin, a pioneer of organizational psychology, described change in three stages: unfreeze, change, and refreeze. Unfreezing means building the case for why the current state can't continue. Change is the transition itself. Refreezing means reinforcing the new state so people don't drift back to old habits.

Best use cases: Lewin's model fits developmental change well because it's simple: there's no coalition to build or vision to communicate, just three stages a single team can move through on its own for a contained process fix.

Strengths and limitations: Its simplicity is a strength here: a team can unfreeze, change, and refreeze a small process without much overhead. That same simplicity is a limitation for complex transformations, where refreezing can oversimplify what's often a longer, less linear process of sustaining change, which is why very large transformations often pair it with a more detailed framework.

Practical application: Take a construction company standardizing how field crews log daily safety checks (for more on applying change management in the field, see our guide to construction change management). There's no need for a formal coalition or vision statement: unfreeze by showing crews why the paper log causes problems, make the change by rolling out a digital log on one job site, and refreeze by making the new log the default before crews drift back to the old paperwork.

Best Change Management Models for Transitional Change

A system or process replacement means managing both the practical mechanics of the swap and the resistance that comes with asking people to give up something familiar.

McKinsey 7-S Model

Overview: Developed by McKinsey & Company consultants, the 7-S model maps seven interdependent elements of an organization: strategy, structure, systems, shared values, skills, style, and staff. It isn't a step-by-step process. It's a diagnostic: you assess how these elements currently align and where a planned change would create friction with the ones you're not actively changing.

Best use cases: The model suits transitions where a new system affects more of the organization than it first appears. Replacing a CRM, for example, obviously touches systems, but it also touches skills, structure, and leadership behavior: can the team actually use it, does reporting need to change, and will leaders visibly work inside the new system instead of falling back on the old one. In a 2023 McKinsey survey, respondents whose organizations aligned employee incentives with the transformation's goals were 2.6 times more likely to report outperforming peers. Incentives are one of the systems 7-S checks against strategy, and a new tool rarely sticks when people still get rewarded for the old way of working.

Strengths and limitations: Its strength is comprehensiveness: it catches misalignments other models miss because it doesn't focus only on the mechanics of the change itself. Its limitation is that it flags misalignments without saying which to fix first or how, so it's typically paired with a model that sequences the work, such as Kotter's or ADKAR.

Practical application: Say a professional services firm is switching from spreadsheet-based project tracking to a dedicated platform. Before rollout, the firm could use 7-S to check for gaps: whether the team has the skills to configure it, whether the reporting structure needs to change to use the new visibility, and whether leadership will actually use the new data instead of defaulting back to the old spreadsheets. Without that check, firms often end up with a new tool nobody fully adopts.

Prosci ADKAR Model

Overview: ADKAR operates at the individual level, sequencing change into five outcomes: awareness of why change is needed, desire to support it, knowledge of how to do it, ability to implement it, and reinforcement to sustain it.

Best use cases: ADKAR tracks individual adoption, not organizational structure, which makes it a strong fit for transitions like software rollouts or new operating procedures, where the change succeeds or fails based on whether each person actually adopts the new way of working.

Strengths and limitations: That individual focus is also its main limitation: ADKAR doesn't address organizational structure or systems on its own, so larger transitions often pair it with a model like 7-S for the organizational view.

Practical application: In Prosci's own benchmarking research, change initiatives with highly effective sponsors were about three times more likely to meet their objectives than those with ineffective sponsors. That finding has a direct application for a field service company rolling out a new work order system: get frontline supervisors visibly bought in before training starts, not just informed after the fact.

Best Change Management Models for Transformational Change

Large-scale, identity-level change requires both the mechanics of mobilizing an entire organization and an understanding of what people experience while it happens.

Kotter's 8-Step Model

Overview: Harvard professor John Kotter built this model around a finding from his 10-year study of more than 100 companies attempting major change: transformations tend to stall at the same predictable points, from failing to create urgency to declaring victory too soon. The eight steps address each failure point in sequence, from creating urgency and building a coalition through to anchoring the change in how the organization operates.

Best use cases: Kotter's model fits this scale of change because it supplies the coalition-building, communication, and momentum a business-model shift needs and a small team-level fix doesn't. Its first step, creating urgency, has strong research behind it: in the same McKinsey survey, respondents whose transformations explained why the change was necessary were 3.1 times more likely to report outperforming peers.

Strengths and limitations: The sequence is comprehensive and gives leaders a checklist that's hard to skip a step on. Its main limitation is the same thoroughness: eight steps take real time and coordination, which is overkill for anything smaller than an organization-wide shift.

Practical application: Take a distribution company moving from a regional wholesale model to direct-to-consumer e-commerce. That kind of shift touches sales, warehousing, and technology at once, which is where Kotter's sequence earns its complexity: building urgency around the market shift, assembling a coalition of department leads rather than mandating the change top-down, and treating the first profitable direct-to-consumer week as a visible win to build momentum before scaling further.

Satir Change Model

Overview: Developed by family therapist Virginia Satir, this model tracks how a team's performance shifts across five stages: late status quo, resistance, chaos, integration, and new status quo. Performance drops through resistance and chaos, then climbs during integration and ideally settles at a higher level than where it started.

Best use cases: Satir's model is most useful for helping leaders anticipate a temporary performance dip during transformation, rather than reading it as a sign the change is failing.

Strengths and limitations: Its strength is a realistic timeline: leaders can plan for the dip and protect critical deadlines during it. Its limitation is that it predicts when performance will drop without giving leaders any actions to shorten the dip.

Practical application: A nonprofit is consolidating three regional program teams into one national structure. Satir's stages help leadership set expectations early: staff can be told upfront that a dip in output during the chaos stage is expected, which reduces the chance that a temporary slowdown gets mistaken for the change not working.

Kübler-Ross Change Curve

Overview: Originally developed by psychiatrist Elisabeth Kübler-Ross to describe the stages of grief, the model has since been widely adapted to organizational change. It maps five emotional stages: denial, anger, bargaining, depression, and acceptance.

Best use cases: It's most useful for anticipating individual emotional reactions to a transformation that carries a personal cost, such as a merger, restructuring, or role elimination, where people are processing a loss rather than just learning a new process.

Strengths and limitations: Its strength is naming reactions leaders often mistake for resistance or a performance problem, which makes it easier to respond with support instead of frustration. Like Satir's model, it guides how a manager responds to individuals without laying out a plan for the change itself, so both are typically paired with a prescriptive model like Kotter's.

Practical application: During a merger that consolidates two departments into one, some employees will initially deny that reporting lines are really changing, get frustrated once it's confirmed, try to negotiate exceptions for their team, disengage for a period once those options run out, and eventually settle into the new structure. Recognizing which stage someone is in helps a manager choose between giving more information, more patience, or having a direct conversation.

Change Management Models Compared

How to Choose the Right Change Management Model

Consider the scale of change. A process tweak affecting one team calls for a lightweight model like PDCA or Lewin's. A shift affecting the whole organization's structure or culture calls for something built for that scale, like Kotter's.

Evaluate organizational readiness. Teams with prior experience managing change can move faster through a model's stages. Teams with little change experience benefit from a more structured, step-by-step approach, even for a moderate-sized change.

Account for culture and stakeholder resistance. Models built around the psychology of change, like Satir's or the Kübler-Ross curve, directly address resistance rooted in cultural norms or a personal sense of loss. An adoption-focused model like ADKAR is the better fit when resistance is mainly practical, like people not knowing how to use a new tool.

Align the methodology with business goals. A model should serve the outcome you actually need, not the other way around. Fast individual adoption of a new system doesn't call for a heavier organizational framework just because it's more comprehensive.

Know when to combine models. Change management models do one of three jobs. Kotter's, ADKAR, PDCA, and Lewin's prescribe actions in order. Satir's and Kübler-Ross describe what people go through. McKinsey 7-S diagnoses where a change will collide with the rest of the organization. Most transitions need more than one job done, so pairing a prescriptive model with a descriptive or diagnostic one covers the gap.

Organizations can combine models that address different aspects of the same change: for example, 7-S can assess organizational alignment while ADKAR addresses individual adoption, or Kotter's sequencing can run alongside Satir's or Kübler-Ross's stages to manage both the mechanics and the emotional experience of a transformation.

Tools and Systems for Managing Organizational Change

Even the right model breaks down without a way to track it. Change plans, task ownership, and dependencies often live across email threads, spreadsheets, and slide decks, so when one team's timeline slips, the teams depending on it are often the last to know.

A centralized system changes what leaders can see. A shared view of tasks, milestones, and ownership replaces scattered updates with one picture of what's been done, what's pending, and who's accountable for it. That visibility matters most in transitions and transformations, where a single initiative usually spans multiple teams that don't otherwise share a workflow.

The same system that tracks the change can also track its outcomes. Teams can monitor adoption and performance as the change rolls out and adjust before small issues compound, rather than waiting for a post-mortem to find out whether it worked.

Quickbase is one example of a platform built for this kind of cross-functional coordination. Teams use it to centralize change plans, assign and track tasks across departments, and maintain visibility into a transformation's progress without stitching together a patchwork of disconnected tools.

Frequently Asked Questions

What are the main change management models?

The most commonly used include Lewin's unfreeze-change-refreeze model, Kotter's 8-Step Model, Prosci's ADKAR model, the McKinsey 7-S framework, the Satir Change Model, and the Kübler-Ross change curve. PDCA (Plan-Do-Check-Act) is also widely used for smaller, iterative improvements. Each fits a different type and scale of change, from a single team's process fix to a full organizational transformation.

What is the difference between a change management model and a methodology?

A model describes the general pattern of change, such as Lewin's three stages or ADKAR's five outcomes. A methodology is the fuller structured approach built around one or more models, including assessments, processes, and tools, such as the Prosci Methodology. In practice, the distinction rarely changes which approach an organization should use.

Can organizations use more than one change management methodology?

Yes. Combining models that address different aspects of a change, such as pairing an organizational model like McKinsey 7-S with an individual-adoption model like ADKAR, is a reasonable approach for anything beyond a small developmental change.

What is the ADKAR model?

ADKAR is Prosci's model for individual change, built around five outcomes: awareness of why change is needed, desire to support it, knowledge of how to do it, ability to implement it, and reinforcement to sustain it. It's built for transitions where success depends on each person actually adopting the new way of working, such as software rollouts or new procedures.

How do Agile teams approach change management?

Agile teams tend to favor iterative models like PDCA over linear, multi-stage frameworks, since Agile's short cycles already build in a plan-test-adjust rhythm. That doesn't rule out heavier models for larger organizational shifts; day-to-day process changes just usually move through faster, smaller cycles instead.

How do you measure whether a change initiative is successful?

Most models point to a mix of adoption metrics (are people actually using the new process or system) and outcome metrics (did the change produce the result it was meant to). Both matter, since a change can be technically implemented without being genuinely adopted.

Who should lead a change management initiative?

Ownership varies by scale. A developmental change is usually led by a team or department manager. Transitional and transformational change typically need an executive sponsor, since resistance and cross-functional coordination both increase with the scope of the change.

Which change management model is best?

There isn't one best model; there's a best model for the type of change you're managing. A model built for individual technology adoption won't address a full cultural transformation, and a heavy transformation framework is overkill for a small process fix. The match between model and change type, as outlined above, matters more than picking the most popular one.