Change Management in HR: Models, Steps and Pitfalls

Organizational change management is the structured work of helping people move from the current way of working to a new one, so that a reorganization, new system or new policy is actually adopted rather than just announced. HR leads it by building the case for change, mapping who is affected, planning communication and training, equipping managers, and measuring whether people are using the new way of working. Models such as Lewin's three stages, Kotter's 8 steps and ADKAR give you a frame, but the results come from disciplined planning and follow-through.

Key takeaways

• Change management focuses on people, while project management focuses on tasks; you need both for a change to deliver its benefits.
• Lewin, Kotter and ADKAR are guiding frameworks, not proven recipes. A systematic review found no single model was clearly superior.
• A practical HR plan runs from case for change and impact analysis through communication, training, go-live support and reinforcement.
• Measure adoption with usage, proficiency and feedback data, and expect early numbers to be volatile.
• Much of what looks like resistance is a lack of clarity, capacity or direction, which you can often fix.

What is change management in HR?

Change management in HR is the set of practices that prepare, support and equip employees to adopt a change in how they work. It sits beside project management: one delivers the new structure or system, the other makes sure people use it.

The UC Berkeley HR change management toolkit draws the line clearly: project management handles the work tasks, while change management "focuses on ensuring the support of the people." A new HR system can go live on time and still fail if managers keep running approvals by email.

Two key terms: adoption means people are using the new process or tool as intended, not just logging in, and a stakeholder is any person or group affected by the change or able to influence it.

HR is usually the natural owner of this work because it already holds workforce data, runs training and supports managers. In practice, that role means supplying workforce data, recommending human capital solutions and tracking progress toward the new structure, while senior leaders set the tone for the change. For a wider view of HR's place in strategy, see this guide to strategic HR planning from strategy to action.

How do Lewin, Kotter and ADKAR compare?

Lewin describes change as three broad stages, Kotter lays out eight leadership steps for organization-wide change, and ADKAR tracks the five outcomes an individual needs to change. They work at different levels, so many HR teams borrow from more than one.

Lewin's three stages. Kurt Lewin's model, first described in 1947, uses the image of melting and reshaping an ice cube. The Open University summary of Lewin's model explains the stages: unfreezing (people recognize that something needs to change and resistance is reduced), change (new ways of working are tried), and refreezing (new behaviors become stable). Critics call it linear and light on power and politics, though it remains useful for incremental change.

Kotter's 8 steps. John Kotter's model sets out a sequence for leaders: create a sense of urgency, build a guiding coalition, form a strategic vision, communicate the vision, remove obstacles, generate short-term wins, sustain acceleration, and anchor the change in culture. A peer-reviewed review by Appelbaum and colleagues in the Journal of Management Development found literature support for most individual steps, but "no formal studies were found covering the entire spectrum and structure of the model." The authors concluded it works best as a planning tool alongside other methods during implementation.

ADKAR. ADKAR, developed by Prosci, focuses on the individual. It names five outcomes each person must reach in order: Awareness of the need for change, Desire to take part, Knowledge of how to change, Ability to apply the new skills, and Reinforcement to sustain it. If adoption stalls, you can ask which of the five is missing for a given group.

How well do these models perform? A 2021 systematic review in the Journal of Healthcare Leadership by Harrison and colleagues examined 38 studies using 12 change methodologies. Kotter's model appeared in 19 studies and Lewin's in 11, while ADKAR appeared in one. The authors could not determine whether using a model itself caused success, and found models were mostly used as broad guiding principles rather than step by step prescriptions.

Model	Focus	Stages	Best fit	Main limitation
Lewin	Organization	Unfreeze, change, refreeze	Simple or incremental changes; explaining change to managers	Linear; assumes stability; light on politics
Kotter	Leadership and organization	8 steps from urgency to anchoring in culture	Large, organization-wide initiatives that need executive sponsorship	Whole model not formally tested as a unit
ADKAR	Individual	Awareness, Desire, Knowledge, Ability, Reinforcement	Diagnosing where specific groups are stuck	Little published research evidence so far

What are the steps in an HR change management plan?

A workable plan moves from defining the change and who it affects, through communication and training, to go-live support and reinforcement. The steps below combine common elements of the OPM guidance and the Berkeley toolkit.

1. Define the case for change. Write a short statement of what is changing, why now, and what happens if nothing changes. Tie it to specific business objectives and the outcome you expect.
2. Secure a sponsor and a change team. Name an executive sponsor who will speak for the change and a working team that includes HR, the business owner, IT where relevant, and legal counsel.
3. Map stakeholders and impacts. List each affected group, how their work changes, and how much. Use workforce data and surveys to set a baseline, as OPM recommends.
4. Assess readiness. Check capacity, competing changes and manager confidence.
5. Build the communication plan. Decide messages, senders, channels and timing for each group (see the next section).
6. Design training and support. Match training to what each role actually needs to do differently, and plan help for the first weeks after launch.
7. Prepare managers. Give managers talking points, an FAQ and a way to send concerns upward before employees hear the news.
8. Launch and support. Provide visible help at go-live: floor support, office hours, a single place for questions.
9. Measure adoption and adjust. Track the metrics you set up front and fix problems quickly.
10. Reinforce and hand over. Update policies, job descriptions, performance goals and onboarding so the new way becomes normal work.

If the change is a new HR platform, pair this plan with a structured HR software selection process so that adoption planning starts during selection, not after contract signing. For technology-led change specifically, the article on leading people through technology change covers the CHRO's role in more depth.

How should HR handle communication and training?

Communicate early, often and through managers, and train people on the specific tasks that change for them. Repetition is not wasted effort, because stressed people absorb less of what they hear.

The Berkeley toolkit cites research that stress can reduce information processing by up to 80% and advises, "if you think you have communicated enough, communicate 10X more." In practice that means:

• Lead with the why. OPM's guidance says the communication plan should explain the reason for change and tell employees where to get information and help.
• Use managers as the main channel. Employees usually want to hear what a change means for them from their own manager, so brief managers first. See how HR managers adapt to rapid workplace change.
• Do not leave gaps. Rumors fill silence. See how silence in HR communication can help or hurt trust.
• Check legal and labor obligations. OPM notes that communication plans may need legal review, including collective bargaining obligations. This article is general information, not legal advice.

For training, OPM distinguishes reskilling (training people for a new occupation) from upskilling (training people in the same occupation to work in new ways). Most HR-led changes need upskilling: short, role-based sessions close to go-live, job aids, and practice environments. If the change is larger, a structured upskilling plan for your workforce helps you sequence it.

How do you measure change adoption?

Measure adoption by combining behavior data (are people using the new process?) with proficiency and feedback data (are they using it well, and how do they feel?). Set targets before launch so you have something to compare against.

The Berkeley toolkit lists quantitative measures such as adoption rate, speed of adoption, exceptions, usage reports, quality, turnover and operational performance, plus qualitative feedback from one-to-ones, focus groups and surveys. It warns that metrics are often volatile for the first three months while people climb the learning curve, and suggests limiting surveys to about four across a project to avoid fatigue. OPM's guidance adds tracking milestones, collecting employee and customer feedback, and adjusting plans when outcomes fall short.

Useful adoption metrics include:

• Usage: share of target users completing key tasks in the new system or process each week.
• Workarounds: volume of requests still handled the old way (emails, paper forms, side spreadsheets).
• Proficiency: error rates, rework and help desk tickets per user over time.
• Sentiment: short pulse questions on clarity, confidence and support.

Share results with affected employees, not only with leadership.

Why do employees resist change, and what helps?

People resist change when they do not understand it, do not have the time or skill to adopt it, or expect to lose something they value. Treat resistance as information about what your plan is missing.

The Berkeley toolkit observes that "often, what looks like resistance is actually lack of clarity," and that exhaustion and lack of direction are frequent causes. Its practical advice includes finding "bright spots" and celebrating quick wins, breaking the change into achievable milestones, acknowledging feelings without arguing, and engaging allies before opponents. The Harrison review found involving people in decisions improved commitment, and that projects led by the affected staff themselves fared better.

Steps that tend to help:

• Diagnose by group: use ADKAR-style questions to find whether a team lacks awareness, desire, knowledge, ability or reinforcement.
• Involve respected employees in design and testing, so the change is not something done to them.
• Address real losses honestly, such as changes to roles, schedules or status.

Major changes such as mergers carry extra retention risk; the playbook on retaining talent after an acquisition covers that scenario.

Common mistakes in HR change management

• Treating launch as the finish line. Go-live is when adoption work starts, and reinforcement through policies and goals is what keeps it.
• Announcing before managers are briefed. Managers who learn news alongside their teams cannot answer questions and may undermine the change.
• Following a model step by step without adapting it. Research shows models work best as guiding principles fitted to your context.
• Measuring only activity. Training attendance and emails sent do not show adoption. Track behavior and outcomes.
• Labeling questions as resistance. Pushback often points to a real gap in clarity, tools or time.

Frequently asked questions

Which change management model is best?

No model has been shown to be clearly superior. The 2021 systematic review found Kotter and Lewin were most often used, but the value came from using them as flexible guides. Pick the one your leaders will actually use.

Who should own change management: HR or the project team?

Both have roles. The project team owns delivery of the change, an executive sponsor owns the direction, and HR typically owns people-related work such as impact analysis, manager preparation, training design and adoption measurement.

How long does organizational change take?

It depends on scale. A small process change may settle in weeks, while a restructuring or new core system can take many months. The Berkeley toolkit notes that metrics are often volatile for about three months after launch, so plan support for at least that long.

What is the difference between change management and transition?

Change is the external event, such as a new structure or system. Transition, a term from William Bridges' model described in the Berkeley toolkit, is the internal, psychological process people go through to accept it: endings, a neutral zone, and new beginnings.

What to do next

1. Write a one-page case for change for your next initiative, including what happens if nothing changes.
2. Run a stakeholder and impact map with your project team and identify the two or three groups most affected.
3. Choose a model (Lewin for small changes, Kotter for large ones, ADKAR for diagnosis) and agree on how you will use it.
4. Set three to five adoption metrics and baseline them before launch.
5. Brief managers first, then schedule communication and training for each group.
6. Review results at 30, 60 and 90 days and adjust support where adoption lags.

Sources

• UC Berkeley Human Resources: Change Management Toolkit
• Harrison R, et al. Where Do Models for Change Management, Improvement and Implementation Meet? Journal of Healthcare Leadership, 2021
• Appelbaum SH, et al. Back to the future: revisiting Kotter's 1996 change model. Journal of Management Development, 2012
• The Open University (OpenLearn): Lewin's change management model

Last reviewed: November 2026.