Leaders can reduce employee resistance to change by finding out what people are concerned about, involving them in decisions they can influence, and removing practical barriers. Explain the business need honestly, provide time to learn, and follow through on feedback. Repeating the announcement is not enough.
Employee resistance to change means reluctance or opposition to a proposed way of working. It can reflect uncertainty, competing demands, or a valid concern about the design. This guide from Praevion Consulting Inc, a Toronto-based consulting firm, helps Canadian leaders choose a useful response rather than label people as difficult.
In this article
What causes employee resistance to change?
Employee resistance to change does not have one cause. People may question the purpose, worry about their role, lack confidence in the proposed solution, or struggle with the workload. Leaders should investigate the concern before deciding whether the answer is explanation, support, or a different design.
Prosci’s research-based guidance identifies unclear reasons, changes in job roles, uncertainty, weak trust in leaders, and exclusion from decisions as common causes. These are useful diagnostic prompts, not a test that proves why a particular employee is reluctant.
Ask: “Which part of this change makes your work harder or creates a risk?” Then request an example. A missed training session may indicate a scheduling conflict; continued spreadsheet use may reveal a missing system function.
6 practical responses to employee resistance to change
Reducing employee resistance to change requires a response matched to the underlying barrier. The six actions below combine clear communication with participation, practical support, and accountable follow-through. Use them within a change management plan, adapting the effort to the people affected and the consequences of getting the transition wrong.
1. Explain the need without hiding the trade-offs
Explain the business problem, the expected benefit, and the specific effect on people’s work. Separate confirmed decisions from matters still under discussion. If jobs, responsibilities, or schedules may change, do not promise stability that leadership cannot genuinely guarantee.
Give managers a consistent explanation, but leave room for questions. A credible message can include “we haven’t decided yet,” provided it states who will decide and when employees will hear more.
2. Give employees a real part in the design
Invite affected employees to influence the parts of the change that remain open. Be clear about those boundaries before asking for input. Participation should improve decisions, not create the appearance of consultation after every meaningful choice has already been made.
The CIPD’s employee voice guidance stresses that people need ways to express views and influence matters affecting their work. Combine team discussions with private conversations and representative channels where relevant. One survey will not reach everyone.
3. Remove workload and process barriers
Check whether employee resistance to change reflects a workable objection to an unworkable plan. Observe the task, test the handoffs, and review competing deadlines. When a new process adds duplicate entry or leaves exceptions unresolved, correct the design before asking for greater commitment.
The Canadian Centre for Occupational Health and Safety identifies unclear roles, poor change management, and insufficient staffing as workplace stress hazards. Build time for learning into schedules and decide what existing work will stop or wait.
4. Build ability through supported practice
People need a safe opportunity to practise unfamiliar work before being expected to perform it independently. Use realistic tasks, short job aids, and accessible support. Separate a skills gap from disagreement: a person who supports the change may still need help carrying it out.
For example, practise a difficult customer return rather than only the simplest transaction. Ask the employee to demonstrate the task and explain where they get stuck. Training completion alone does not establish readiness.
5. Make managers part of the solution
Managers should understand the change, have time to support their teams, and know where to escalate unresolved problems. Employee resistance to change is harder to address when supervisors privately discourage the new approach or continue rewarding the old way of working.
Check managers’ own concerns first. Agree what they will explain, coach, and monitor. Where departments give conflicting instructions, require executive sponsorship to resolve the conflict rather than leaving employees to choose which rule to ignore.
6. Close the feedback loop and check progress
Tell employees what happened to their concerns, including suggestions that were not accepted and why. Review whether the response removed the barrier. Managing employee resistance to change is ongoing work; a listening session without follow-through provides little evidence that leadership takes concerns seriously.
CIPD distinguishes employee voice from silence and notes that people may stay quiet when speaking up feels risky. Do not interpret fewer complaints as success. Compare feedback with correct process use, errors, unresolved issues, and service results.
How should leaders match the response to the concern?
Leaders should record the specific concern, check the evidence, and assign an owner to the response. This diagnostic table helps separate common barriers. It is a management aid, not a psychological assessment or a basis for judging an employee’s intentions.
| Concern | Check first | Useful response |
|---|---|---|
| “I don’t see the need.” | Understanding of the business problem | Explain the reason with concrete evidence |
| “I can’t do this yet.” | Skills, access, and practice | Provide coaching and task-based support |
| “This takes longer.” | Actual workflow and duplicate work | Fix the process or adjust capacity |
| “Nobody listens.” | Unanswered issues and past promises | Respond visibly and honour commitments |
In an illustrative Ontario distributor, staff might avoid a new order screen because it cannot handle partial deliveries. Repeating its benefits misses the problem. Test that exception, repair the workflow, and then reassess use. This is an example, not a reported client result.
Frequently asked questions
Employee resistance to change should prompt investigation, not automatic blame. These answers distinguish useful challenge from unresolved adoption problems and explain how to assess progress. The aim is reliable, supported work, not a team that stops asking difficult questions.
Is employee resistance to change always harmful?
No. A concern may expose missing functionality, unsafe workload, or an unrealistic assumption before it causes wider problems. Evaluate the evidence and address the issue rather than assuming that disagreement reflects a poor attitude.
How do leaders know their response is working?
Check whether the original barrier has been removed and employees can perform the new work correctly. Use operational measures alongside employee feedback, because attendance, logins, and fewer complaints do not by themselves demonstrate successful adoption.
For the wider approach, read what organizational change management involves. To address adoption barriers in your organization, contact Praevion Consulting Inc.
Praevion leadership
Mehrzad Verdizadegan, PhD
CEO, Praevion Consulting Inc
References: Prosci, Understanding Why People Resist Change; CIPD, Employee Voice; CCOHS, Taking Action on Workplace Stress.
Photos: FORTYTWO, Antenna, KOBU Agency, Jo Szczepanska on Unsplash.
