What is change management? Definition, process and models

Change management is defined as the structured approach organizations use to move people, teams, and processes from a current state to a desired future state. It covers how you plan a change, communicate it, help employees adopt it, and make it stick. Companies restructure, adopt new software, and shift strategies all the time. Whether those changes succeed depends less on the change itself and more on how well people are guided through it. That’s what change management does.

Change Management Definition: What Exactly Is It?

Here’s a working change management definition: it’s the discipline of preparing, supporting, and equipping individuals, teams, and organizations to make a transition, from where they are today to where the business needs them to be.

Notice the three levels in that definition:

• Individuals. One person learning a new tool, a new role, or a new way of working.
• Teams. Groups adjusting how they collaborate, report, and make decisions.
• Organizations. The company as a whole shifting its structure, culture, or strategy.

Change management works on all three at once. A new CRM rollout is a technical project, sure. But it fails if individual salespeople keep using spreadsheets, if teams don’t change their pipeline reviews, and if leadership doesn’t reinforce the new behavior. Frameworks like Prosci’s ADKAR were built precisely because organizational change only happens when individual change happens first.

Change management sits inside the broader discipline of running projects and operations. If you want the full picture of how structured work gets done in a company, start with What is Project Management? and come back. The two fields overlap constantly.

Why Managing Change in Organizations is Critical

Most change initiatives fail. Not some. Most. McKinsey research on change programs has long pointed to the same uncomfortable number: around 70% of transformation efforts fall short of their goals. The technology usually works. The strategy usually makes sense on paper. What breaks is the human side.

When it comes to change management, managing the people side is the part leaders skip most often. Here’s what that looks like in practice:

• Resistance goes unaddressed. Employees don’t resist change for fun. They resist because nobody explained why the change matters or what it means for them.
• Strategy and adoption drift apart. Executives approve a new direction. Middle managers half-communicate it. Frontline teams keep working the old way. The strategy exists in slides, not in behavior.
• Project managers get blamed for adoption problems. A project can hit every deadline and still fail, because delivery is not adoption.

The fix isn’t complicated, but it is deliberate: treat the human transition as a workstream with its own owner, plan, and metrics. Leaders who manage the emotional and practical journey of their people close the gap between business strategy and employee adoption. Leaders who don’t end up with expensive software nobody uses.

The Essential Change Management Process

A good change management process turns a vague ambition (“we need to modernize”) into a sequence of concrete steps. Gartner’s insights on organizational change back this up: employee-centered, open-source approaches to change dramatically outperform top-down mandates. The five steps below are the backbone most successful initiatives share.

1. Prepare the Organization for Change

Before you change anything, people need to understand why the current state can’t continue. This step is about building awareness and urgency. Share the data behind the decision. Name the risks of standing still. Talk to the people most affected before the announcement, not after. If employees first hear about a major change through a company-wide email, you’ve already lost ground.

2. Craft a Vision and a Project Plan for Change

Urgency without direction just creates anxiety. So the next step is a clear roadmap: what the future state looks like, which milestones get you there, who owns what, and how you’ll measure success. Treat it like any serious initiative and build a real project plan, with scope, timeline, resources, and success metrics defined up front. Vague goals like “improve collaboration” don’t survive contact with reality. “Reduce average ticket resolution time from 48 to 24 hours by Q3” does.

3. Implement the Changes

Execution is where communication has to shift from broadcast to dialogue. Keep messaging constant and honest, including about what’s not going well. And empower employees to act: give them training, decision-making room, and quick wins they can point to. People support what they help build. If every adjustment needs executive sign-off, adoption slows to a crawl.

4. Embed Changes Within Company Culture

This is the step most organizations skip, and it’s why changes quietly reverse six months later. To prevent backsliding, wire the new way of working into the company’s DNA:

• Update onboarding, job descriptions, and performance reviews to reflect the new processes.
• Recognize and reward the behaviors you want repeated.
• Retire the old tools and workflows. If the old system stays available “just in case,” people will use it.

5. Review Progress and Analyze Results

Finally, measure. Compare results against the metrics you set in step 2: adoption rates, performance indicators, employee feedback. Be honest about what didn’t land. Post-implementation reviews aren’t about assigning blame; they’re about adjusting the change while it’s still fresh and capturing lessons for the next one. A change you don’t measure is a change you can’t defend, or improve.

Top Change Management Models You Should Know

You don’t have to invent your approach from scratch. Several proven change management models give you a ready-made structure. Think of them as maps: none of them is the territory, but each one keeps you from getting lost. Here are the three every project manager should know.

Prosci’s ADKAR Model

ADKAR focuses on the individual, because organizations don’t change; people do, one at a time. The acronym stands for:

• Awareness of the need for change.
• Desire to participate and support it.
• Knowledge of how to change.
• Ability to apply new skills and behaviors.
• Reinforcement to make the change stick.

It doubles as a diagnostic tool. If adoption stalls, walk through the five elements and you’ll usually find exactly where a person or team got stuck.

Kotter’s 8-Step Process

Developed by Harvard Business School professor John Kotter, this classic model is all about leadership and momentum. It starts by creating a sense of urgency, then builds a guiding coalition of influential people, forms a strategic vision, enlists a volunteer army, removes barriers, generates short-term wins, sustains acceleration, and finally anchors the change in culture. It works best for large, top-down transformations where visible leadership makes or breaks the effort. Speaking of which, how leaders show up during change matters enormously; our guide to leadership styles in team management breaks down which styles fit which situations.

Lewin’s Change Management Model (Unfreeze, Change, Refreeze)

Kurt Lewin’s model is the foundation most others build on, and its power is its simplicity:

• Unfreeze. Challenge the status quo and prepare people to let go of old habits.
• Change. Make the transition, with heavy communication and support.
• Refreeze. Stabilize the new state so it becomes the new normal.

Critics say “refreezing” feels outdated in fast-moving industries where change never stops. Fair point. But as a mental model for any single initiative, it’s still hard to beat.

Integrating Change Management with Project Management

Here’s the truth every experienced project manager learns the hard way: a delivered project without adoption is a failed project. You can hit scope, schedule, and budget, and still watch the deliverable gather dust because nobody changed how they work.

That’s why modern project management standards treat change as core, not optional. The PMBOK Guide in its latest edition includes adaptability and organizational change among its guiding principles. And Agile methodologies were practically built for it; short iterations, constant feedback, and incremental delivery give people time to adapt instead of hitting them with one massive switch.

In practice, integrating the two disciplines means:

• Adding change management activities (communication, training, stakeholder readiness) directly into the project schedule.
• Measuring adoption alongside delivery. Track usage and proficiency, not just milestones.
• Assigning clear ownership of the people side, whether that’s the PM, a change manager, or a sponsor.

For project managers, this is also a career skill. Organizations increasingly expect PMs to lead through volatility, not just administer plans. If that’s the direction you’re heading, an Agile Leadership Certification builds exactly the skills for guiding teams through constant change. And if you’re formalizing your project management career more broadly, PMP Certification Training covers change management as part of the full body of knowledge.

Change is going to happen either way. The only question is whether you manage it, or it manages you.