Change Management: 6 Moves to Overcome User Resistance

What is Change Management?

Change management manages the human dimension of technical transformation

Change management is the process of managing an organization’s transition from its current state to a targeted future state in a structured and systematic manner. It encompasses the human dimension—perhaps more importantly—alongside technical changes.

Change management includes 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: Effective transmission of why and how the change will occur
• Training and support: Acquisition of new competencies
• Reinforcement: Making the change permanent

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 different questions: Are employees using the new system? Has productivity increased? Is there a return to old habits?

Representative data summarizes the situation:

• 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

These two disciplines complement 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, technical delivery fails. Without change management, the delivered solution is not used. Both are necessary; neither is sufficient on its own.

The ADKAR Model: 5 Stages of Individual Change

ADKAR defines the 5 stages every individual goes through during the change process

The ADKAR model, developed by Prosci, is a framework that explains individual change. The core idea is simple: organizations don’t change, people do. Organizational change is the sum of individual changes.

ADKAR consists of five stages, and every individual passes through these stages sequentially:

A – Awareness

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

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

Note: It is impossible to move to other stages without providing awareness. If we proceed without a satisfying answer to the question “Why are we changing?”, resistance is inevitable.

D – Desire

The desire to participate in and support the change. While awareness is “understanding,” desire is “acceptance.” 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 cannot be forced. Motivation, participation, and the WIIFM (What’s In It For Me) questions must be addressed.

K – Knowledge

The stage of knowing how to change. Even if an employee wants to change, they cannot if they don’t know how:

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

Application: Training programs, user manuals, and on-the-job learning come into play at this stage.

A – Ability

The skill to apply knowledge in practice. Knowing and doing are different things:

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

Time factor: Ability development takes time. An employee does not become an expert immediately when training ends; practice, support, and patience are required.

R – Reinforcement

The stage of making the change permanent. Preventing the risk of returning to old habits:

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

Warning: Without reinforcement, change remains temporary. Returning to old habits within 3-6 months is a common occurrence.

Kotter’s 8-Step Change Model

Kotter’s model structures organizational change in 8 sequential steps

John Kotter’s 8-step model is one of the most widely used frameworks for managing organizational change. While ADKAR focuses on individual change, Kotter addresses change at the organizational level.

Step 1: Creating a Sense of Urgency

Clearly state why the change is necessary “now”:

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

Goal: For employees and managers to feel the sentiment that “we must change.”

Step 2: Building a Guiding Coalition

Form a powerful 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 left only to IT or a single department will fail. A broad-based coalition is essential.

Step 3: Developing a Vision and Strategy

Define where the change is leading in a clear and inspiring way:

• What will the future state look like?
• What will successful change look like?
• How will we reach this vision?

Test: We should be able to explain the vision in 5 minutes, and the listeners should understand it.

Step 4: Communicating the Change Vision

Communicate the vision continuously, consistently, and through multiple channels:

• Talk about the vision at every opportunity
• Repeat it in different formats
• Upper management must be role models
• Answer questions and concerns

Rule: When communication is insufficient, people fill in the gaps—usually with negative assumptions.

Step 5: Removing Obstacles for Broad-Based Action

Eliminate elements that prevent 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 maintain motivation.

Step 7: Consolidating Gains and Producing More Change

Expand the change by building on early successes:

• 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

Make the change the “new normal”:

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

Stakeholder Analysis and Mapping

Stakeholder analysis identifies all groups affected by the change and determines their strategy

Stakeholder analysis is the process of systematically identifying, analyzing, and managing all individuals and groups affected by or influencing the change. Effective change management starts with stakeholder analysis.

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

Evaluate 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 stakeholder will be affected by the change. Highly impacted groups require more support.

3. Current Attitude

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

4. Target Attitude

The attitude the stakeholder needs to be converted to.

Stakeholder Matrix

Stakeholder Communication Strategy

Develop a specific 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

Effective communication stands as the backbone of change management

Communication is the most critical component of change management. Insufficient or incorrect communication dooms even the best-planned change to failure. When there is a communication gap, people fill it with assumptions—usually negative ones.

Communication Plan Components

1. Target Audience

Define a specific target audience for every message. One-size-fits-all communication remains ineffective.

2. Key Messages

Determine customized core messages for each target 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

Choose the appropriate channel for the message and 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

Synchronize communication with the project schedule. Communicating too early creates anxiety; too late provides ground for rumors and misinformation.

5. Sender

A message from the right person is more effective. Strategic decisions should come from the CEO, while operational details should come from the project manager.

Communication Principles

• Start early: Begin communication on day one; silence creates uncertainty
• Repeat frequently: Saying it once is not enough; repeat in different formats
• Be consistent: Conflicting messages from different sources erode trust
• Keep it two-way: Don’t just inform; gather feedback
• Be honest: If we don’t know, say “I don’t know”; do not provide false information
• Be concrete: Give concrete examples, not abstract promises

Resistance Management Strategies

Resistance is a natural reaction; we must understand and guide it rather than suppress it

Resistance is the psychological or behavioral reaction shown against change. Although resistance seems negative, it is actually a sign that people are taking the change seriously and feeling its impact. A lack of resistance might indicate indifference, which is more dangerous.

Sources of Resistance

Individual Sources

• Fear of the unknown: Uncertainty about the new situation
• Fear of loss of competence: Anxiety 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: Deficiency in training, time, or support
• Wrong timing: Too much change at the same time

Resistance Management with 6 Moves

Move 1: Early Involvement

Involve people in the process early. Make them feel that the change is something “done with them,” not “done to them”:

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

Move 2: Identify Champions

Select change champions in every department or team to advocate for the change:

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

Move 3: Open and Continuous Communication

Uncertainty is the biggest feeder of resistance. Fill the information gap quickly:

• Share what we know
• State what we don’t know
• Answer questions rapidly

Move 4: One-on-One Intervention

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 showing that the change works:

• Success stories from pilot applications
• Measurable improvements
• Promotion of successful users

Move 6: Consistent Consequences

Applying consistent and fair consequences if resistance persists:

• Clarifying expectations
• Including it in performance evaluations
• Last case: position or duty change

Field Example: Change Management Case Study

Real Case (Unbranded)

Situation

A machinery manufacturing firm with 180 employees is replacing its 15-year-old legacy system with a new ERP platform. A previous software change attempt 3 years ago failed; a perception of “it won’t work again” prevails among employees. The sales team is particularly resistant: “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.” Created urgency with concrete data.
3. Weeks 4-6: 1 champion was selected from each department (8 people total). Champions received 2 days of specialized training.
4. Weeks 6-10: Weekly “Change Bulletin” launch. Each week, one success story, one FAQ, and one tip were shared.
5. Weeks 10-14: One-on-one meetings with the sales department. Special sessions with the 3 most resistant individuals. Concerns were heard, and a special training plan was made.
6. Weeks 14-18: Pilot implementation started in Sales. First success after 2 weeks: order entry time decreased by 40%. This result was shared across the company.
7. Weeks 18+: Full rollout. Champions provided first-line support. An adaptation survey was conducted 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.” Change management is not included in the budget or plan while technical project management is being done. Result: a perfect system that no one uses.

2. Starting Too Late

Remembering change management 2 weeks before go-live. However, change management should be run in parallel from the start of the project. Last-minute training and communication remain insufficient.

3. Lack of Upper Management Participation

The CEO or GM only appears at the project kickoff and then disappears. Employees get the message: “This project isn’t that important.” 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 employees need different information. Segmentation is a must.

5. Ignoring Resistance

The approach of “resistant people will leave anyway” or “they’ll get used to it over time.” Not actively dealing with resistance leads to silent sabotage and cultural poisoning.

6. Keeping Training Too Short

A 2-hour training, a 200-page manual, and the approach of “call IT if you have questions.” Practical, repetitive training suitable for adult learning principles is required.

7. Skipping Reinforcement

Declaring “the project is over” and dispersing after go-live. However, the first 90 days are critical. Without support, follow-up, measurement, and rewards, a rapid return to old habits begins.

Recognizing common mistakes is the first step to preventing them

Adaptation Metrics Table

Track the following metrics to measure change management success. Improvement cannot be made without measurement:

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)