How to Handle an Employee Who Resists Workplace Changes
Begin with curiosity, not a label
A change to working hours, software or a customer process can unsettle someone who has been successful under the old arrangement. The first mistake is to describe that reaction as a bad attitude before understanding it. A person may agree with the objective but worry that the new method will slow down customers, increase errors or make their own experience seem less valuable. Some concerns will be misplaced; others may expose a problem the project team has missed.
Arrange a private conversation rather than challenging the employee in front of colleagues. Explain what you have observed: “You have raised concerns about the new booking process at our last two meetings. I'd like to understand what is worrying you.” This is more useful than asking why they are being difficult.
Separate the decision from its implementation
Explain what has already been decided and what remains open to adjustment. For example, the organisation may have committed to a new system, while training dates, reference materials and the sequence of rollout can still be influenced. If the decision is final, do not pretend the employee can vote it down. Equally, do not invite feedback and then dismiss every suggestion without explanation.
Ask the employee to identify a specific risk. “Which step will cause a problem, and what would happen next?” A concrete example can be checked. If the employee predicts that customers will wait longer, test a typical transaction together. If they cannot explain the concern, ask what evidence would help them feel confident.
Check whether support is missing
Resistance sometimes reflects a skills gap that someone is embarrassed to admit. An experienced colleague may find a new digital tool harder to learn than a new starter does. Offer a demonstration, a short practice session or a written guide without making the support feel like a punishment. Ask whether workload or competing deadlines leave enough time to learn the change properly.
Consider a limited trial where practical. A two-week review of error rates, turnaround times and customer feedback can replace argument with evidence. Agree in advance who will collect the information and when the team will discuss it. Do not promise that the change will be reversed if that is not an option.
Explain expectations and follow through
Listening and making reasonable adjustments do not remove the need to carry out legitimate instructions. Once concerns have been considered and appropriate support provided, be clear about the expected behaviour: which process must be used, from what date, and where exceptions should be reported. Make the instruction specific enough to assess fairly.
If the employee continues using the old method, distinguish a mistake from a deliberate refusal. Check whether the new process is accessible, safe and properly explained. Record relevant facts and follow your organisation's established procedures for persistent conduct or performance issues. Seek HR advice where appropriate; avoid inventing disciplinary rules in the moment.
Keep the wider team informed
Other employees may share the concern but remain silent. Without naming the individual, tell the team what feedback has been received, what has changed as a result and what remains non-negotiable. That demonstrates that speaking up is worthwhile even when the overall decision stands.
The objective is not to win an argument. It is to implement a necessary change with fewer avoidable problems, while treating employees as people who may have useful information. A calm conversation, a practical test and clear expectations usually achieve more than repeated instructions to “get on board”.
Further reading: Browse the free management guides for related background. Where relevant, explore the management books.