Why Employees Resist New Systems and What to Do About It

Employee Resistance to New Systems: Causes and Solutions

When an employee says “the old way was faster”, they may be partly right. Understanding the causes of resistance is the shortest route past it, and this article covers the most common causes and how to deal with each one.

Skills and change management 5 min read

By Nour Aldein Tleti. Updated 7 October 2026.

Why do employees resist new systems, and how do I handle it?

Employees usually resist out of fear of losing their job or status, fear of making mistakes in front of others, or because the system really has added steps with no clear benefit to them. The answer is to listen and identify the real cause, then address it through explanation, training or changes to the system, while management stays clear that the change is going ahead.

Common causes of resistance

Fear for their job: The employee worries that automation will make them unnecessary, especially in data entry and accounting work.
Loss of status or control: Someone who was the only source of certain information may feel the system is taking that role away.
Fear of mistakes: An employee with less computer experience worries about looking incapable in front of colleagues.
A doubled workload: During the transition the employee works with both systems at once, and feels the change has added to their work instead of easing it.
A real problem with the system: Sometimes the system does not fit how the department works, and resistance is the first sign of it.

Practical solutions

One-to-one conversations: Ask the employee directly what worries them, as the stated reason may differ from the real one.
Clarity about roles: Explain how tasks will change and where the time the system saves will go, without promises you cannot keep.
Training that embarrasses no one: A test environment where employees can make mistakes without consequences, and one-to-one training for those who need it, away from others.
Fix what deserves fixing: If the complaint is valid, change the screen or procedure, and tell the team their feedback made a difference.
Involve the objectors: A long-serving employee who objects can become the best tester of the system if you give them a role in improving it.

Considerations for Syrian organisations

Sensitivity about livelihoods: With difficult economic conditions, fear for income is stronger, so early clarity about the future of roles is essential.
Seniority and respect: In many organisations long-serving staff hold a special standing, and involving them in a way that respects it makes change easier for everyone.
Past attempts that failed: If the organisation has been through a system that failed before, expect more scepticism, and start with small, tangible results that rebuild trust.

A practical plan for handling resistance

01
Observe without judging
Note where usage lags and who avoids the system, without accusing anyone at this stage.
02
Listen before explaining
Short one-to-one or small-group meetings whose first aim is to understand concerns, not to defend the system.
03
Sort the causes
Separate what needs training, what needs a change to the system, and what needs reassurance about roles.
04
Fix it and say what you did
Make the changes you can, and tell the team what changed as a result of their feedback.
05
Lock in the decision
Once the real causes are addressed, set a final date after which the system is the only approved way of working.

From resistant behaviour to the right response

What you notice	Likely cause	Response
Repeated delays in entering data	Difficult to use, or lack of time	Simplify the screen and set aside specific time for data entry
Keeping a parallel notebook or spreadsheet	Lack of trust in the system’s accuracy	Reconcile the two for a short period, then stop the alternative
Negative comments in work groups	Unspoken anxiety	An open Q&A session clarifying what will and will not change
Relying on a colleague to get tasks done	Insufficient training	Short one-to-one training on the employee’s own tasks

Read also

Skills and change management

Frequently asked questions

Should I force employees to use the system?

A management decision is needed in the end, but forcing people without explanation and training breeds workarounds. Combine firmness that the change is going ahead with enough support to make it happen.

What do I do with a long-serving employee who flatly refuses to change?

Start with a private conversation that respects their experience, ask their opinion on improving the system, and offer one-to-one training. If the refusal continues after that, it becomes a management matter, handled like any other work obligation.

Is resistance a sign the system is bad?

Not always, but it deserves a look. Separate the natural discomfort of change from real problems that need fixing.

How long does resistance usually last?

It varies with the size of the change and the quality of support. Resistance usually eases when staff see a tangible benefit in their daily work.

How do I reassure employees about their jobs?

Be honest, explain which tasks will change and which new skills are needed, and offer training that helps them move into higher-value work.