What is Change Management?

The first time I tried to roll out a major process change at one of my companies, I sent a Slack message explaining the new system, gave everyone a week to switch over, and expected things to just work. They didn’t. Three weeks later, half the team was still using the old process, two people had built their own workarounds, and I was fielding daily complaints.

That experience taught me something I now consider obvious: changing systems is easy, but changing how people work is the actual challenge. Every organizational change I’ve led since then, whether it was implementing new HR software, restructuring teams, or shifting company culture, has started with the people side first.

Change management gives you the framework to do that systematically instead of hoping people figure it out on their own.

What Is Change Management?

Change management is the discipline of preparing, supporting, and helping individuals, teams, and entire organizations make a transition from how things work today to how they need to work tomorrow. It covers the tools, processes, and techniques used to manage the people side of change so the organization actually achieves the intended results.

The reason it exists as a formal discipline is straightforward: most organizational changes fail not because the strategy was wrong, but because the people affected weren’t brought along. McKinsey research found that 70% of change programs fail to achieve their goals, and the primary reasons are employee resistance and lack of management support.

In practice, change management sits at the intersection of project management, organizational psychology, and leadership. A project manager handles the technical implementation (new software goes live on March 1st). A change manager handles the human side (the 200 people who need to use that software are trained, motivated, and supported through the transition).

Why Change Management Matters

I’ve seen companies spend six figures on new technology and then get almost no adoption because nobody invested in helping employees actually use it. That’s an expensive lesson in what happens without change management.

When I implemented Deel for international payroll across multiple teams, the technical setup took about two weeks. Getting contractors in four countries comfortable with a new payment system, documentation process, and compliance workflow took three months. The technology was the easy part.

Here’s what I’ve seen go wrong when organizations skip change management:

Employees revert to old processes within weeks. Knowledge workers are especially good at finding workarounds that let them avoid tools they didn’t ask for.

Productivity drops during transitions and never recovers. Without structured support, the dip that naturally comes with any change becomes permanent.

Key talent leaves. People who feel blindsided by changes, or who aren’t given a voice in how changes are implemented, start updating their resumes.

Projects run over budget. The cost of rework, extended timelines, and additional training when change isn’t managed properly almost always exceeds what proper change management would have cost upfront.

Organizations that use structured change management are six times more likely to meet project objectives than those that don’t. That number alone makes the case.

The 4 Most Used Change Management Models

Several frameworks have emerged to structure how organizations approach change. I’ve used elements of all four below, though in practice most teams end up blending pieces from multiple models rather than following one religiously.

1. Prosci’s ADKAR Model

ADKAR stands for Awareness, Desire, Knowledge, Ability, and Reinforcement. It focuses on individual change, which I find makes it the most practical for day-to-day use.

Awareness means the person understands why the change is happening. Desire means they want to participate. Knowledge means they know how. Ability means they can actually do it. Reinforcement means the change sticks over time.

I like ADKAR because it gives you a diagnostic tool. When someone isn’t adopting a change, you can pinpoint exactly where they’re stuck. An employee who understands why a new HRIS is being implemented (awareness) but hasn’t been trained on it (knowledge gap) needs a different intervention than someone who knows how to use it but doesn’t see the point (desire gap).

2. Kotter’s 8-Step Model

John Kotter’s model is the most widely referenced in leadership literature. The eight steps are: create urgency, form a coalition, create a vision, communicate the vision, remove obstacles, create short-term wins, build on change, and anchor change in culture.

This model works best for large-scale organizational transformations. When I was involved in restructuring a team from functional silos to cross-functional pods, Kotter’s emphasis on building a coalition and creating urgency was exactly right. You can’t restructure an organization without executive sponsors who actively champion the change.

The limitation is that Kotter’s model is linear and top-down. Real organizational change is messier than eight sequential steps.

3. Lewin’s Change Model

Kurt Lewin’s model is the oldest and simplest: Unfreeze, Change, Refreeze. You destabilize the current state (unfreeze), implement the new state (change), and then stabilize the new state as the norm (refreeze).

I still find this framework useful as a mental model even though it’s from the 1940s. The ‘unfreeze’ concept is particularly important. People won’t change until their current state feels uncomfortable or insufficient. That’s why the best change leaders start by building the case for why the status quo isn’t working before they introduce the solution.

4. McKinsey 7-S Framework

The 7-S model examines seven internal elements: Strategy, Structure, Systems, Shared Values, Style, Staff, and Skills. The idea is that all seven need to align for change to succeed.

This is less of a step-by-step process and more of a diagnostic checklist. I’ve used it when a change initiative stalls and I need to figure out why. Usually it’s because we aligned the strategy and systems but didn’t address the skills gap, or we changed the structure without adjusting the management style to match.

The Change Management Process: 6 Steps

Regardless of which model you follow, the operational process for managing change follows a consistent pattern. Here are the six steps I use:

1. Assess the Change and Its Impact

Before anything else, you need to understand what’s actually changing and who it affects. Map out every team, role, and process that will be touched by the change. I create a simple impact matrix: rows for each affected group, columns for what changes for them, how significant the change is (low, medium, high), and what support they’ll need.

At this stage I also identify who’s likely to resist and why. Resistance is rational. If a process change makes someone’s job harder or threatens their status, they have a legitimate reason to push back. Understanding that upfront lets you address it proactively.

2. Build a Sponsorship Coalition

Every successful change I’ve been part of had visible, active executive sponsorship. Not passive approval, but leaders who showed up, communicated the ‘why’ in their own words, and visibly used the new tools or processes themselves.

I aim for sponsors at two levels: a senior executive who owns the strategic rationale and a set of mid-level managers who will reinforce the change daily. When I rolled out Rippling as a centralized HR platform, the CEO explained why we were consolidating systems and department heads handled the team-level transition.

3. Develop a Communication Plan

People need to hear ‘why’ before they hear ‘what’ or ‘how.’ My communication approach follows a simple sequence: share the business reason for the change, explain what’s changing (specifically), describe what support is available, and then give people a channel to ask questions and raise concerns.

I’ve learned to communicate earlier and more often than feels comfortable. Most leaders under-communicate change by a factor of 10. Saying something once in an all-hands meeting does not mean the organization has internalized it.

4. Train and Enable

Training is where many change initiatives fail because organizations confuse ‘telling people about the change’ with ‘enabling them to succeed.’ A 30-minute demo is not training. People need hands-on practice, reference materials they can use later, and someone to ask when they get stuck.

When I implemented task-based hiring evaluations to replace resume screening, I didn’t just explain the new approach. I created evaluation rubrics for each role type, walked hiring managers through three practice evaluations, and paired each manager with someone who’d already used the system. The adoption rate was near-complete within two hiring cycles.

5. Manage Resistance

Resistance shows up in predictable patterns: vocal opposition in meetings, passive non-compliance (people nod along but keep doing things the old way), workarounds that circumvent the new process, or sudden disengagement.

The biggest lesson I’ve learned is that resistance is information, not a problem to overcome. When a senior engineer pushes back on a new tool, there’s often a legitimate technical concern underneath the frustration. I address resistance by listening first, acknowledging the disruption, and then problem-solving together rather than mandating compliance.

6. Reinforce and Sustain

This is the step most organizations skip, which is why changes don’t stick. Reinforcement means measuring adoption, celebrating early wins, adjusting based on feedback, and building the new way of working into performance expectations and standard operating procedures.

I set specific adoption metrics for every change I manage. After implementing a new compensation framework, I tracked how many managers used the new salary bands when making offers (vs. going off-script). That metric told me where reinforcement conversations were needed.

Types of Organizational Change

Not every change requires the same level of management. Understanding the type helps you calibrate your approach:

Structural changes involve reorganizations, mergers, acquisitions, or shifts in reporting relationships. These are high-impact because they directly affect people’s roles, teams, and career paths. I’ve found structural changes require the most communication and the longest timelines.

Technological changes cover new software, systems, or tools. The challenge here is adoption, not implementation. I always budget as much time for user enablement as I do for technical setup.

Process changes are modifications to how work gets done: new approval workflows, different meeting structures, revised hiring processes. These seem smaller but can accumulate significant friction if employees don’t understand why their familiar routines are being disrupted.

Cultural changes are the hardest. Shifting organizational values, management philosophy, or how teams collaborate requires sustained effort over months or years. You can’t mandate culture change; you can only model it, reward it, and remove barriers to it.

People-focused changes include layoffs, restructures, leadership transitions, and role redesigns. These are emotionally charged and require careful communication, transparency, and support resources.

Common Change Management Mistakes

After leading and supporting dozens of organizational changes, these are the patterns I see repeatedly:

Announcing the ‘what’ without the ‘why.’ Employees aren’t resistant to change itself. They’re resistant to change they don’t understand. Every time I’ve led with ‘here’s the business problem this solves,’ adoption has been faster than when I led with ‘here’s the new tool.’

Treating communication as a one-time event. One email or one meeting does not constitute communication. People absorb change information at different speeds and through different channels. Plan for repetition across multiple formats.

Ignoring middle management. Front-line managers are where change succeeds or dies. If they’re not equipped to answer their team’s questions and model the new behavior, the change won’t cascade past the leadership layer.

Underestimating the timeline. Organizational change doesn’t happen on a project plan’s schedule. The technical implementation might finish on time, but human adoption takes longer. I’ve never seen a significant change fully adopted in under 90 days, and most take 6-12 months.

Declaring victory too early. Just because the new system is live doesn’t mean the change is complete. Monitor adoption metrics for at least two quarters after launch before stepping back.

Final Thoughts

Change management isn’t a nice-to-have layer you add on top of projects. It’s the difference between an initiative that delivers results and one that generates resentment and gets quietly abandoned six months later.

The most useful thing I’ve learned is to start earlier than you think necessary, communicate more than feels comfortable, and treat resistance as useful feedback rather than an obstacle. Every change affects real people’s daily work, and respecting that is both the right thing to do and the most effective strategy.

FAQ

Here are the most frequently asked questions about change management.

What is change management in simple terms?

Change management is the structured process of helping people and organizations move from how things work now to how they need to work in the future. It covers communication, training, resistance management, and reinforcement to make sure changes actually get adopted rather than ignored or abandoned.

What are the 5 key principles of change management?

The five core principles are: start with a clear reason for the change, secure active leadership sponsorship, communicate early and frequently, enable people through training and resources, and reinforce the change until it becomes the new normal. These principles apply regardless of which formal model you follow.

What is the most popular change management model?

Prosci’s ADKAR model is the most widely used in practice, particularly for individual-level change. Kotter’s 8-Step model is the most referenced in leadership and academic contexts. Most organizations adapt elements from multiple models rather than following one exclusively.

How long does organizational change take?

Small process changes can achieve full adoption in 30-90 days. Technology implementations typically take 3-6 months including enablement. Large-scale cultural or structural changes take 12-24 months or longer. The technical implementation almost always finishes before human adoption is complete.

Who is responsible for change management?

Responsibility is shared. Executive sponsors own the strategic rationale and visible support. Change managers or HR leads design and execute the change plan. Middle managers reinforce the change with their teams daily. In smaller organizations, these roles often overlap, but the accountability structure matters even when one person fills multiple roles.

What is the difference between change management and project management?

Project management focuses on the technical side: deliverables, timelines, budgets, and milestones. Change management focuses on the people side: adoption, resistance, training, and behavior change. Both are needed for any significant initiative. A project can be delivered on time and on budget but still fail if people don’t adopt the new way of working.