Why Do Employees Resist Change in the Workplace?

Why Do Employees Resist Change in the Workplace?

A new process is announced on Monday. By Friday, people are still using the old spreadsheet, quietly bypassing the new system or questioning every detail in the meeting. Why do employees resist change? Usually, it is not because they are difficult, lazy or unwilling to improve. It is because the change has created uncertainty, risk or extra pressure that has not yet been properly addressed.

For managers, this matters. Resistance can delay a worthwhile project, damage morale and create an unhelpful divide between ‘the people making decisions’ and ‘the people expected to make it work’. But resistance also contains useful information. If you listen properly, it can show you where the plan is weak, where communication has failed and what your team needs to move forward with confidence.

Why Do Employees Resist Change at Work?

People do not experience organisational change as a strategy document. They experience it in their workload, relationships, routines, confidence and sense of job security. A new customer service standard, rota, reporting line or technology platform may look sensible to senior leaders, but employees are likely to ask a more immediate question: what will this mean for me?

That question is reasonable. Change may affect how someone performs familiar tasks, whether their experience is still valued, how they are measured, or whether they can keep up while handling their normal workload. Good managers do not dismiss those concerns as negativity. They deal with them directly.

Uncertainty feels like a threat

Even positive change can create anxiety when the detail is unclear. Employees may hear that a department is being restructured, a service is being automated or targets are changing, yet receive little information about timing, responsibilities or support. In that gap, rumours grow quickly.

People often imagine the worst when leaders are vague. They may worry about redundancies, loss of status, reduced flexibility or being blamed if the new approach fails. Clear information will not remove every concern, but it gives people something solid to work with. Say what is known, explain what is still being decided, and commit to a date for the next update.

They may not trust the process

Trust is central to change. If previous initiatives were launched with enthusiasm and then abandoned, employees will be cautious. If leaders have made promises that were not kept, or if decisions appear to have been made behind closed doors, people may assume this change will be no different.

Trust is not rebuilt through a polished announcement. It is rebuilt through consistent behaviour. Managers need to answer questions honestly, follow through on commitments and admit when they do not yet have an answer. Credibility rises when employees see that leaders are dealing with reality rather than selling a slogan.

Change can threaten competence and identity

Many people take pride in being good at their job. A new system or method can make an experienced employee feel like a beginner again. That is uncomfortable, particularly in busy teams where nobody wants to appear incapable in front of colleagues or customers.

This is one reason training matters. Telling staff that a new process is ‘easy to use’ can sound dismissive if they are already struggling. Show them how to use it, give them time to practise and make help easy to access. The aim is not merely compliance. It is to help people regain confidence and perform well.

The workload problem is real

A common management mistake is to treat implementation as something staff will somehow fit in around everything else. A new procedure may require learning, meetings, testing, data entry and feedback, while daily service levels still need to be maintained.

When workload is ignored, resistance can be a practical response rather than an emotional one. Employees may agree with the change in principle but feel unable to carry it out safely or properly. Ask what needs to stop, pause or be simplified during the transition. If nothing changes except the number of tasks, frustration is predictable.

They were told, not involved

Not every decision can be made by committee. Leaders sometimes need to set a clear direction quickly. However, there is a major difference between deciding the destination and excluding people from the journey.

Front-line employees understand the daily reality of customers, systems and bottlenecks. They can identify risks that senior managers cannot see from a report. Involving them early does not weaken leadership. It improves implementation and gives people a fair chance to shape the practical details.

Resistance Is Not Always the Same

Managers should avoid labelling all hesitation as resistance. One employee may be worried about losing their job. Another may need technical training. A third may have spotted a genuine flaw in the plan. Treating each response as stubbornness will push useful feedback underground.

Look at the behaviour and ask better questions. Is the person seeking clarity, avoiding a new task, openly challenging the decision, or influencing others to reject it? The response should match the issue. Someone who lacks skill needs coaching. Someone with a valid concern needs to be heard. Deliberate obstruction may require firmer performance management, but that should not be your starting assumption.

It also depends on the scale of the change. A small adjustment to a meeting format needs a lighter touch than a merger, a major digital transformation or a change to terms and conditions. The greater the impact on people’s security, identity and workload, the more time leaders must invest in communication and support.

How Managers Can Turn Resistance into Progress

The strongest change managers do not try to ‘win’ every objection. They create the conditions in which people can understand the need, contribute their knowledge and build the capability to act.

Start with a clear case for change

Employees need more than the instruction to do things differently. Explain the problem the change solves. Use real workplace evidence: customer complaints, duplicated effort, missed deadlines, rising costs, safety concerns or opportunities to improve service.

Then make the connection to the team. A message such as, ‘We are introducing this new call-handling process because customers are currently repeating their details three times, and we can reduce that frustration,’ is far more meaningful than, ‘This is part of our transformation programme.’ Keep the purpose practical and believable.

Communicate early, then communicate again

One announcement is not communication. People need opportunities to hear the message, consider its impact and ask questions. Use team briefings, one-to-ones and practical demonstrations. Repeat the key points without sounding scripted: why the change is happening, what will change, what will not change, when it will happen, and where support is available.

Be careful not to overpromise. Change is rarely effortless, and employees will spot empty reassurance immediately. A stronger message is: ‘There will be a learning curve. We have planned time for training, and we will review the process after the first month.’ That is honest, specific and credible.

Give people a role in implementation

Invite employees to test a new process, identify likely customer issues or suggest improvements to guidance materials. Appoint change champions only if they have genuine influence and enough time to help colleagues. A champion who is simply given a badge and more work will not build commitment.

When teams contribute to solving real problems, ownership grows. They are no longer passive recipients of a decision. They are helping make the change work.

Build skills, not just awareness

Awareness sessions can explain what is coming, but they do not guarantee performance. People need practical learning: a demonstration, a chance to practise, clear job aids, feedback and follow-up coaching. This is particularly important when change affects customer-facing work, where uncertainty can quickly become inconsistent service.

Training should focus on the moments employees will actually face. What do they say to a customer? Which step has changed? What happens when the system does not behave as expected? Practical management development, such as the change management learning within The Brilliant Suite, is most valuable when it equips people to apply a method immediately rather than merely understand a theory.

Notice and reinforce progress

Early wins matter because they make change visible. Share examples of improved turnaround times, fewer errors, better customer feedback or a team member who has found a smarter way to work. Recognition should be specific: praise the action and the result, not just the attitude.

At the same time, keep reviewing what is not working. A change plan is not a fixed script. If a new process creates unnecessary duplication or confusion, adjust it. Employees are more likely to commit when they see that feedback leads to sensible action.

The Manager’s Standard During Change

Your team will watch your behaviour more closely than your presentation slides. If you complain about the new system, avoid using it or provide mixed messages, employees will take their cue from you. If you stay calm, prepared and available, you make the change feel more manageable.

That does not mean pretending everything is easy. It means being professionally honest while keeping the team focused on what they can control. Set clear expectations, make time for questions, remove obstacles and hold people accountable for agreed actions.

The next time your team pushes back, do not rush to silence the concern. Listen for the risk, the workload issue or the missing information beneath it. Address that well, and resistance can become the moment your team starts taking ownership of change.

Back to blog