Change Management: 6 Moves to Overcome User Resistance

What is Change Management?

The technical side of a transformation matters, but the human side usually decides its fate

Change management is how you move an organization from where it is today to where it wants to be, and how you do it deliberately rather than by luck. The technical work is real, but the hard part is almost always the people.

Change management covers the following areas:

• Individual change: Adaptation of employees to new processes, systems, and behaviors
• Organizational change: Transformation of structures, processes, and culture
• Resistance management: Understanding and guiding natural human resistance
• Communication: Getting across why and how the change will happen
• Training and support: Building new competencies
• Reinforcement: Making the change stick

Why is it Important?

Project management focuses on technical deliverables: Is the system installed? Do the functions work? Are the integrations complete? Change management asks a different set of questions: Are employees actually using the new system? Has productivity gone up? Or has everyone quietly drifted back to the old way?

Representative data sums it up:

• Success rate of projects applying change management: 70-80%
• Success rate of projects not applying change management: 30-40%
• Difference: 40+ points

Project Management vs. Change Management

The two disciplines lean on each other:

• Project management: Delivery of the technical solution on time, within budget, and within scope
• Change management: Adoption, utilization, and realization of benefits from the solution

Without project management, the technical delivery collapses. Without change management, the delivered solution sits on the shelf. You need both; neither is enough on its own.

The ADKAR Model: 5 Stages of Individual Change

ADKAR names the five stages a person goes through while adapting to change

The ADKAR model, developed by Prosci, looks at change one person at a time. The idea behind it is simple: organizations don’t change, people do. What we call organizational change is really just the sum of a lot of individual changes.

ADKAR has five stages, and every individual moves through them in order:

A – Awareness

The stage of understanding why the change is necessary. The employee needs answers to a few questions:

• Why are we changing?
• Why is the current state insufficient?
• What are the risks of not changing?

Note: You can’t move to the later stages until awareness is there. Push ahead without a convincing answer to “Why are we changing?” and resistance is guaranteed.

D – Desire

The willingness to take part in and support the change. If awareness is “understanding,” desire is “buying in.” The employee asks:

• Do I support this change?
• What do I gain from this change?
• Do I want to participate in the change?

Critical point: Desire can’t be forced. Motivation, involvement, and the WIIFM (What’s In It For Me) question all have to be addressed.

K – Knowledge

The stage of knowing how to change. An employee may want to change, but if they don’t know how, they can’t:

• How does the new system work?
• What are the new process steps?
• What skills do I need to acquire?

Application: This is where training programs, user manuals, and on-the-job learning come in.

A – Ability

The skill to put knowledge into practice. Knowing and doing are two different things:

• Being able to use the new system in real transactions
• Solving problems while applying new processes
• Handling error situations

Time factor: Ability takes time to build. Nobody walks out of training an expert; practice, support, and patience are what get you there.

R – Reinforcement

The stage of making the change permanent, and heading off the slide back to old habits:

• Celebrating and recognizing successes
• Performance measurement and feedback
• Providing continuous support and resources
• Structures that prevent regression

Warning: Without reinforcement, change is temporary. Slipping back to old habits within 3-6 months is one of the most common things you’ll see.

Kotter’s 8-Step Change Model

Kotter breaks organizational change into eight steps that build on one another

John Kotter’s 8-step model is one of the most widely used frameworks for managing organizational change. Where ADKAR zooms in on the individual, Kotter works at the level of the whole organization.

Step 1: Creating a Sense of Urgency

Spell out clearly why the change is needed “now”:

• Share market data and competitive analysis
• Make the risks of the current situation tangible
• Make the crisis or opportunity visible

Goal: To get employees and managers to genuinely feel that “we have to change.”

Step 2: Building a Guiding Coalition

Form a strong team to lead the change:

• Influential leaders from different departments
• Both formal and informal leaders
• Individuals with decision-making authority
• Credible and respected figures

Critical: Change dumped on IT alone, or on any single department, will fail. A broad-based coalition is essential.

Step 3: Developing a Vision and Strategy

Describe where the change is heading in a way that is both clear and inspiring:

• What will the future state look like?
• What will successful change look like?
• How will we get there?

Test: You should be able to explain the vision in five minutes, and the people listening should walk away understanding it.

Step 4: Communicating the Change Vision

Communicate the vision constantly, consistently, and through more than one channel:

• Bring up the vision at every opportunity
• Repeat it in different formats
• Upper management must model it
• Answer questions and concerns

Rule: When communication falls short, people fill the gaps themselves, and usually with the worst-case interpretation.

Step 5: Removing Obstacles for Broad-Based Action

Clear away whatever is stopping employees from moving toward the vision:

• Remove old systems and processes
• Address managers who resist change
• Align organizational structures
• Provide necessary resources

Step 6: Generating Short-Term Wins

Plan and celebrate early successes:

• Visible results within 6-18 months
• Proof that the change is working
• Recognizing and rewarding those who succeed

Why it matters: Long-term change is exhausting; short-term wins keep motivation alive.

Step 7: Consolidating Gains and Producing More Change

Use the momentum from early successes to widen the change:

• Analyze what worked
• Scale successful applications
• Move to more comprehensive changes
• Launch new projects and initiatives

Step 8: Anchoring New Approaches in the Corporate Culture

Turn the change into the “new normal”:

• Integrate new behaviors into performance systems
• Link promotions and rewards to new values
• Make success stories part of the company history
• Onboard new employees into this culture

Stakeholder Analysis and Mapping

Stakeholder analysis lists everyone the change touches and sets a plan for each of them

Stakeholder analysis is where you list out every person and group that either affects the change or is affected by it, then figure out how to work with each one. Good change management starts right here.

Stakeholder Identification

First, list all stakeholder groups:

• Internal stakeholders: Employees, managers, departments, unions
• External stakeholders: Customers, suppliers, business partners, regulators
• Project stakeholders: Sponsor, project team, consultants

Stakeholder Assessment Criteria

Weigh the following factors for each stakeholder group:

1. Level of Influence

How much the stakeholder can affect the success of the change. High-influence stakeholders take priority.

2. Level of Impact

How much the change will affect the stakeholder. Heavily impacted groups need more support.

3. Current Attitude

The stakeholder’s attitude toward the change: supportive, neutral, resistant.

4. Target Attitude

The attitude you need to move the stakeholder toward.

Stakeholder Matrix

Stakeholder Communication Strategy

Build a separate communication strategy for each stakeholder group:

• High Influence + High Impact: Close collaboration, frequent communication, involvement in decisions
• High Influence + Low Impact: Keep satisfied, regular updates
• Low Influence + High Impact: Provide support and training, pay attention to concerns
• Low Influence + Low Impact: Minimum effort, general communication is sufficient

Communication Planning

Well-run communication is the backbone of change management

Communication is the most critical component of change management. Weak or muddled communication can sink even the best-planned change. Leave a gap, and people will fill it with their own assumptions, usually the negative ones.

Communication Plan Components

1. Target Audience

Define a specific audience for every message. Talk to everyone at once and you reach no one.

2. Key Messages

Tailor the core message to each audience:

• Upper management: Strategic goals, ROI, risk mitigation
• Middle management: Team impact, role expectations, support
• End users: What will change in daily work, how to get support

3. Communication Channels

Match the channel to the message and the audience:

• Face-to-face meetings: Critical announcements, complex topics, emotional messages
• Email: Official updates, documentation
• Intranet: Resource sharing, FAQ, continuous updates
• Visual materials: Infographics, videos, posters
• One-on-one meetings: Resistance management, special cases

4. Timing

Line communication up with the project schedule. Too early and you create anxiety; too late and you leave room for rumors and misinformation.

5. Sender

A message lands harder when it comes from the right person. Strategic decisions should come from the CEO, operational details from the project manager.

Communication Principles

• Start early: Begin on day one; silence breeds uncertainty
• Repeat often: Saying it once isn’t enough; repeat it in different formats
• Be consistent: Conflicting messages from different sources erode trust
• Keep it two-way: Don’t just inform; collect feedback
• Be honest: If you don’t know, say “I don’t know”; don’t make something up
• Be concrete: Give real examples, not abstract promises

Resistance Management Strategies

Resistance is a natural reaction; the job is to understand and guide it, not crush it

Resistance is the psychological or behavioral reaction people show against change. It looks like a bad sign, but it’s actually proof that people are taking the change seriously and feeling its weight. No resistance at all often means indifference, which is the more dangerous state.

Sources of Resistance

Individual Sources

• Fear of the unknown: Uncertainty about the new situation
• Fear of loss of competence: The worry that “I won’t be able to learn the new system”
• Comfort zone: The current situation being familiar and comfortable
• Past experiences: Previous failed change initiatives
• Personal loss: Loss of status, authority, or relationships

Organizational Sources

• Culture: The “we’ve always done it this way” mindset
• Political reasons: Power balances, departmental interests
• Lack of resources: Not enough training, time, or support
• Wrong timing: Too much change piling up at once

Resistance Management with 6 Moves

Move 1: Early Involvement

Bring people in early. Make it feel like something done “with them,” not “to them”:

• Participate in needs analysis
• Provide ideas for solution design
• Take part in the testing process

Move 2: Identify Champions

In every department or team, pick change champions to carry the message:

• Individuals respected by their peers
• Those with a positive approach to change
• Individuals with strong communication skills

Move 3: Open and Continuous Communication

Uncertainty is what feeds resistance most. Close the information gap fast:

• Share what you know
• Say plainly what you don’t
• Answer questions quickly

Move 4: One-on-One Intervention

Give special attention to individuals showing high resistance:

• Organizing individual meetings
• Listening to their concerns
• Providing specific support and training

Move 5: Creating Early Wins

Produce concrete results that show the change works:

• Success stories from pilot applications
• Measurable improvements
• Putting successful users in the spotlight

Move 6: Consistent Consequences

If resistance drags on, apply consequences that are consistent and fair:

• Clarifying expectations
• Including it in performance evaluations
• As a last resort: position or duty change

Field Example: Change Management Case Study

Real Case (Unbranded)

Situation

A machinery manufacturer with 180 employees is swapping its 15-year-old legacy system for a new ERP. A software change attempt three years earlier had flopped, so a “here we go again” mood hangs over the staff. The sales team is the most dug in of all: “Our Excel works just fine.”

Change Management Steps Applied

1. Weeks 1-2: Stakeholder analysis completed. 5 critical resistance points identified: Sales (high), Warehouse (medium), Accounting (low), Production (medium), Procurement (low).
2. Weeks 3-4: Kotter Step 1 – the CEO sent a video message to all employees: “We are falling behind the competition; change is essential.” Urgency created with concrete data.
3. Weeks 4-6: One champion selected from each department (8 people total). Champions received 2 days of dedicated training.
4. Weeks 6-10: Weekly “Change Bulletin” launched. Each week carried one success story, one FAQ, and one tip.
5. Weeks 10-14: One-on-one meetings with the sales department. Dedicated sessions with the 3 most resistant individuals. Concerns were heard and a special training plan was drawn up.
6. Weeks 14-18: Pilot started in Sales. First win after two weeks: order entry time dropped 40%. That result was shared across the whole company.
7. Weeks 18+: Full rollout. Champions handled first-line support. An adoption survey was run 30 days after go-live.

Results (Representative)

• Active usage rate 30 days post go-live: 84% (target: 75%)
• Number of critical errors: 3 (expectation: 8-12)
• Employee satisfaction survey: 3.8/5 (previous project: 2.1/5)
• Rate of return to Excel: 12% (previous project: 65%)
• Order entry time improvement compared to the old system: 35%

Key Success Factors

• CEO visibility and consistency
• Early and correct selection of champions
• Special attention to the most resistant group
• Rapid sharing of early wins
• Continuous measurement and feedback

7 Most Common Change Management Mistakes

1. Neglecting Change Management

The assumption that “everyone will use it once the system is installed.” The technical project gets managed, but change management never makes it into the budget or the plan. Result: a flawless system that nobody touches.

2. Starting Too Late

Remembering change management two weeks before go-live. It should run in parallel from the very start of the project. Squeeze training and communication into the final stretch and both fall flat.

3. Lack of Upper Management Participation

The CEO or GM shows up at the kickoff and then vanishes. The message employees take away is clear: “This project isn’t that important after all.” Sponsor visibility is critical.

4. One-Size-Fits-All Communication

Sending the same message to everyone, through the same channel, at the same frequency. Middle management and field staff need very different information. Segmentation is a must.

5. Ignoring Resistance

The “resistant people will leave anyway” or “they’ll get used to it eventually” approach. Failing to engage resistance head-on breeds silent sabotage and poisons the culture.

6. Keeping Training Too Short

A two-hour session, a 200-page manual, and “call IT if you get stuck.” What you actually need is practical, repeated training built around how adults learn.

7. Skipping Reinforcement

Declaring “the project is done” and scattering right after go-live. The first 90 days are the ones that matter most. Without support, follow-up, measurement, and rewards, people slide back to old habits fast.

Spotting the common mistakes is the first step to avoiding them

Adaptation Metrics Table

Track the metrics below to gauge change management success. You can’t improve what you don’t measure:

Measurement schedule: Baseline values before go-live, 30-60-90 day measurements after go-live, and follow-up measurements at 6 and 12 months should be conducted.

Change Management Checklist

Frequently Asked Questions (FAQ)