What Is Change Management?
Most organizations don’t stay still for long. New technology gets introduced, a merger reshapes reporting lines, a new strategy calls for a different way of serving customers. The change itself is often the easy part to plan on paper. What’s harder is getting the actual people in the organization to adopt it, rather than quietly working around it or ignoring it altogether. That’s the problem change management exists to solve.
In organizational behavior, change management refers to the structured approach an organization uses to plan, implement, and support a transition, whether that’s a new system, a restructure, a culture shift, or a change in strategy. It’s as much about people and psychology as it is about project timelines.
Defining Change Management
Change management is the process of preparing, supporting, and helping individuals, teams, and an organization as a whole move from a current way of working to a desired future state. It covers both the technical side of a change, like installing new software or redesigning a workflow, and the human side, like communication, training, and addressing resistance.
The human side tends to be where change efforts succeed or fail. An organization can have the best new system in the industry, but if employees don’t understand why it’s happening, don’t trust the reasons behind it, or simply haven’t been trained properly, the change is likely to stall.
Why Employees Resist Change
Resistance to change is one of the most studied phenomena in organizational behavior, and it’s worth understanding why it happens before looking at how to manage it.
People resist change for a range of reasons. There’s fear of the unknown, since a new system or process means giving up a routine that feels safe and familiar. There’s also a fairly reasonable concern about competence: if I’ve spent years getting good at the old way of doing things, will I still be good at my job once the new way arrives? Add to that a lack of trust in leadership’s reasons for the change, disruption to established social relationships at work, and simple inertia, and it becomes clear why change so often meets friction, even when the change itself is a good idea.
None of this means resistance is irrational. Often it reflects genuine, valid concerns that a change process has failed to address. Good change management takes resistance seriously as information, rather than treating it as an obstacle to be pushed past.
Common Models of Change Management
Several models have been developed to guide how organizations approach change. Three of the best known are worth knowing, even in overview.
Lewin’s Change Management Model
Psychologist Kurt Lewin proposed one of the earliest and most enduring change models in the 1940s, describing change as a three-stage process: unfreezing the current state, making the change, and then refreezing the new state so it sticks. The unfreezing stage involves helping people recognize that the current way of doing things needs to change, which is often the hardest part. Refreezing is about reinforcing the new behavior so the organization doesn’t slide back into old habits once attention moves elsewhere. Lewin’s model is covered in more depth elsewhere on this site, but it’s worth knowing as the foundation that later models built on.
Kotter’s Eight-Step Model
Harvard Business School professor John Kotter published his change model in the mid-1990s, based on his research into why so many corporate transformation efforts failed. His model breaks change into roughly eight steps, starting with creating a sense of urgency and building a coalition of people who support the change, moving through developing and communicating a clear vision, removing obstacles, and generating short-term wins to build momentum, and finishing by anchoring the new approach into the organization’s culture so it isn’t abandoned once the initial push fades.
ADKAR
A more individually focused model, ADKAR, was developed by Prosci and focuses on the sequence a single person moves through during change: Awareness of why the change is needed, Desire to support it, Knowledge of how to change, Ability to implement new skills, and Reinforcement to make the change stick. Where Lewin and Kotter tend to focus on the organization as a whole, ADKAR zooms in on what has to happen for each individual employee to actually adopt a change.
These models overlap more than they conflict. All of them recognize that change needs a clear reason, active support from people with influence, a plan for building new habits, and reinforcement so the organization doesn’t drift back to its old ways.
A Practical Example: Rolling Out a New System in a Hospital
Consider a hospital replacing its paper-based patient charting system with a new electronic health record platform. On paper, this looks like a straightforward IT project. In practice, it touches nearly everyone in the building, from doctors and nurses to administrative staff and billing.
If leadership simply announces the new system and expects staff to adapt on their own, the rollout is likely to be rocky. Nurses who have spent years relying on familiar paper charts may worry about slowing down during busy shifts while they learn the new interface. Doctors may resent time spent on training when they’d rather be seeing patients. Without a clear explanation of why the change matters, patient safety improvements, fewer transcription errors, faster access to records across departments, staff may see the system as a bureaucratic burden rather than an improvement.
A hospital applying good change management practice would build in a clear communication plan explaining the reasons for the change, involve respected clinical staff early as champions of the new system, provide hands-on training well before go-live, offer extra support during the first weeks of use, and publicly recognize teams that adapt well. That combination addresses both the technical rollout and the human adjustment, which is exactly where change management earns its keep.
Why Change Management Matters to Managers and Employees
For managers, change management matters because poorly managed change is expensive. Failed implementations waste money, damage trust in leadership, and can leave an organization worse off than if the change had never been attempted. A manager who understands the human side of change is far better placed to anticipate resistance and address it early, rather than being caught off guard by it later.
For employees, good change management means the difference between feeling like something is being done to them and feeling like they’re part of a process they understand and can influence. That distinction affects morale, trust, and how willing people are to support the next change that comes along, since organizations rarely go through only one.
Advantages, Limitations, and Criticisms
Structured change management increases the likelihood that a change actually sticks, rather than fading once initial attention moves elsewhere. It gives leaders a repeatable framework rather than having to improvise every time, and it takes employee concerns seriously instead of treating resistance as simply a problem to be overcome.
- Models can become a checklist rather than genuine practice. An organization can follow the steps of a model in name only, going through the motions of a communication plan without genuinely listening to employee concerns.
- Change fatigue is a real risk. Organizations that go through constant, overlapping changes can wear out their employees’ capacity to adapt, no matter how well each individual change is managed.
- No model guarantees success. Even a well-run change process can fail if the change itself is a poor decision, or if external conditions shift partway through.
- Different situations call for different approaches. A small, urgent change may not need the full weight of an eight-step model, while a major cultural shift may need more time and structure than any single framework provides.
So change management isn’t a guarantee, but organizations that take it seriously tend to have a better track record of making change stick than those that treat it as an afterthought.
Conclusion
Change management is the discipline of helping people, not just systems, move from an old way of working to a new one. It matters because the technical part of a change is rarely the hardest part. The harder part is addressing the very human fear, uncertainty, and resistance that any meaningful change tends to bring with it.
Models like Lewin’s unfreeze-change-refreeze approach, Kotter’s eight steps, and ADKAR all offer useful structure, but none of them replace the basic work of explaining why a change matters, listening to concerns, and reinforcing new behavior once the change is in place.