Why Employees Sometimes Resist Change

Change is a normal part of organisational life. Businesses introduce new technology, restructure teams, revise procedures, enter new markets, respond to financial pressure or adapt to changing customer expectations. Yet even when a change appears sensible to leaders, employees may respond with hesitation, criticism, delay or open opposition.

This resistance is often misunderstood. Leaders may label people as negative, disloyal or unwilling to learn, while employees may feel that management has ignored the practical consequences of its decisions. Understanding why employees resist change helps managers respond with better communication, stronger planning and more respectful leadership.

What employee resistance to change really means

Resistance to change is any behaviour, attitude or response that slows, questions or challenges a proposed change. It can be visible, such as refusing to use a new system, arguing against a policy or organising opposition. It can also be quiet, such as missing deadlines, avoiding training, withholding feedback or continuing to use old processes.

Resistance is not always harmful. Employees may notice operational risks that decision-makers have missed. A nurse may question a new patient-recording process because it adds a step during emergencies. A shop supervisor may warn that a stock system will not work reliably in areas with weak internet connectivity. A Kenyan small-business employee may point out that a mobile payment procedure does not reflect how customers actually pay in that location.

The important distinction is between constructive challenge and unproductive obstruction. Constructive challenge identifies risks, asks reasonable questions and suggests improvements. Unproductive obstruction rejects every option, spreads misinformation or deliberately prevents implementation. Effective leaders make room for the first while addressing the second fairly.

Why employees resist organisational change

1. Fear of the unknown

People generally find uncertainty uncomfortable. Employees may not know what the change will require, how success will be measured or whether their roles will still exist. Even when leaders believe the change is positive, employees may be imagining job losses, reduced status, unfamiliar duties or a decline in income.

For example, introducing automation may be described as a way to improve efficiency, but staff may hear that some tasks will disappear. If leaders do not explain how roles will develop, the silence creates room for rumours and anxiety.

2. Fear of losing control

Employees are more likely to resist when decisions seem to be happening to them rather than with them. A person who has managed a process successfully for years may feel powerless when a new procedure is imposed without consultation. The issue may not be the change itself; it may be the lack of influence over how the change is designed or introduced.

Participation does not mean every employee gets to make the final decision. It means that people have a genuine opportunity to share relevant knowledge, raise concerns and influence practical details where possible.

3. Loss of competence and confidence

A new system can make experienced employees feel like beginners. Someone who is highly capable with an established accounting package may feel exposed when asked to use unfamiliar software. Employees may worry that their mistakes will be visible or that younger colleagues will adapt more quickly.

This can lead to avoidance. A person may criticise the system when the deeper concern is, “I am not yet confident that I can use it successfully.” Training, practice time and patient support are therefore central parts of change management, not optional extras.

4. Poor communication

Employees resist change when they receive incomplete, inconsistent or overly technical information. Announcing that “a transformation programme is under way” does not answer the questions people need addressed:

• Why is the change necessary?
• What specifically will change?
• What will remain the same?
• When will each stage happen?
• How will employees and customers be affected?
• Where can people raise questions or report problems?

Communication must also be repeated. A single announcement cannot support a change that unfolds over several months. People need updates as decisions are confirmed, risks emerge and plans are adjusted.

5. Lack of trust in leadership

Employees assess new announcements in light of past experience. If leaders have previously promised support but reduced resources, or if they have hidden important information, staff may treat new assurances with caution. Trust is weakened when managers say that nothing will change for employees and later introduce major alterations without explanation.

Trust is not created by persuasive slogans. It develops when leaders provide accurate information, acknowledge uncertainty, keep commitments and explain changes to the plan honestly.

6. Change fatigue

Organisations sometimes introduce several initiatives at once: a restructuring, a new performance system, revised reporting requirements and a technology upgrade. Even sensible projects can become exhausting when employees are expected to absorb too many changes while maintaining their normal workload.

Change fatigue may appear as indifference rather than active opposition. Employees may attend meetings but stop engaging, complete only the minimum required tasks or wait for the latest initiative to disappear. Leaders need to consider the organisation’s capacity for change, not only the desirability of the proposed outcome.

7. Increased workload and unclear priorities

Many changes require employees to perform old and new tasks simultaneously. A new customer-recording process may be introduced while staff are still expected to meet existing sales targets. Without time, staffing or revised priorities, employees experience change as additional work rather than organisational improvement.

Resistance in this situation may be a rational response to unrealistic demands. Managers should identify which tasks will stop, which deadlines will move and what resources will be available during the transition.

8. Threats to status, identity or relationships

Work is not only a set of tasks. It also provides people with professional identity, authority and social connections. A restructure may remove a supervisor’s decision-making role. A merger may change which team is considered central. A new reporting line may disrupt relationships built over many years.

These losses can be real even when the new structure is necessary. Leaders should not dismiss emotional responses as irrational. Respectful conversations help employees understand their future role and recognise what they are leaving behind.

9. Previous negative experiences

Employees who have experienced failed projects may reasonably be sceptical about another initiative. Perhaps a previous system was introduced without adequate training, or an earlier reorganisation created confusion. Resistance can then serve as self-protection: employees wait for evidence before investing energy in the new direction.

Rather than demanding immediate enthusiasm, leaders should identify what went wrong before and demonstrate how the current approach will be different.

How resistance develops

Resistance often develops through a chain of interpretation. An employee hears about a change, tries to understand what it means personally, assesses whether the leaders can be trusted and decides how much effort to invest. If information is limited and perceived risk is high, the response is likely to be defensive.

Consider a company replacing paper-based expense claims with an online platform. A leader may see a simple efficiency project. An employee may see a requirement to use unfamiliar technology, a risk of delayed reimbursement and an indication that management does not understand field-based work. Both are responding to the same proposal, but they are evaluating different consequences.

This is why leaders should avoid asking only, “Why are people resisting?” A more useful set of questions is:

• What do employees believe they may lose?
• What information is missing?
• Which practical obstacles make the change difficult?
• Have employees been involved in decisions that affect their work?
• What past experiences shape their response?

How leaders can respond effectively

Start with listening and diagnosis

Before trying to persuade employees, gather information. Use team discussions, one-to-one conversations, surveys, pilot groups or structured feedback sessions. Ask open questions and distinguish facts from assumptions. A complaint about a new process may reveal a training gap, an access problem or a genuine design flaw.

Listening does not require leaders to accept every recommendation. It requires them to understand the concern accurately before responding. Managers should also look beyond the most vocal employees. Quiet staff may have important reservations but may not feel safe expressing them publicly.

Explain the reason for change clearly

People need a credible explanation of the problem the change is intended to address. Explain the current situation, the risks of doing nothing and the outcomes the organisation is seeking. Avoid exaggeration. If the change has disadvantages, acknowledge them and explain how they will be managed.

A strong explanation connects organisational needs with employee realities. Instead of saying, “Head office requires a new reporting system,” a manager might explain, “Our current reports take too long to combine, which delays decisions. The new system should reduce duplicate entry, but we will test it with the field team first because internet access varies across locations.”

Involve employees in practical design

Employees often know more about daily operations than senior decision-makers. Involve them in testing workflows, identifying risks, developing guidance and deciding how implementation should occur. A pilot can reveal problems before the change is applied across the organisation.

Be clear about the boundaries of participation. Explain which elements are fixed, such as a regulatory requirement or approved budget, and which elements can be adjusted. This prevents consultation from becoming a symbolic exercise that increases distrust.

Provide training, tools and time

Training should reflect the actual work employees perform. A brief demonstration may not be enough for staff who need to use a new system under pressure. Useful support may include practice exercises, job aids, peer mentors, help desks, translated guidance or scheduled time to learn without normal performance pressure.

Managers should monitor whether training has been understood. Attendance is not proof of competence. Short practical checks, observation and opportunities to ask questions can reveal where further support is needed.

Use managers as trusted translators

Senior leaders may announce a change, but direct supervisors usually explain what it means in daily work. Equip managers with consistent information, likely questions and authority to solve local problems. If supervisors receive information late or cannot answer basic questions, employees may conclude that the change is poorly planned.

Managers should also model the desired behaviour. If leaders continue using old forms while asking everyone else to adopt the new process, the organisation sends conflicting signals.

Recognise progress and correct problems

Change is easier to sustain when employees can see evidence of improvement. Share specific progress, such as reduced duplication, faster service or fewer errors, without presenting early success as proof that all problems have disappeared.

When something goes wrong, respond quickly. Distinguish between problems caused by the change, problems caused by implementation and problems that existed beforehand. Correcting weaknesses builds credibility and prevents employees from feeling that feedback is ignored.

What leaders should avoid

• Labelling all resistance as negativity: this can silence useful warnings and damage trust.
• Relying on one announcement: employees need continuing information as the change develops.
• Promising certainty that does not exist: honest acknowledgement of unknowns is more credible.
• Using pressure before removing obstacles: demanding compliance without training or resources creates frustration.
• Consulting without acting: repeatedly requesting feedback and ignoring it teaches employees that participation is pointless.
• Assuming one approach suits everyone: different teams may face different technical, cultural or workload pressures.

Applying This in Practice

Suppose a growing Nairobi-based distribution business plans to introduce a digital inventory system. Some employees resist because they have used paper records for years, while others are concerned that the system will expose mistakes or fail when they are working away from reliable connectivity.

A practical change-management approach could follow these steps:

1. Map the impact: identify which roles, tasks, locations and customer interactions will be affected.
2. Listen before launch: speak with warehouse staff, drivers, supervisors and finance employees about current difficulties and likely risks.
3. Test a limited version: run a pilot in one team or location and record technical and operational problems.
4. Explain the purpose: show how better inventory information can support purchasing and customer service, while acknowledging the learning period.
5. Provide realistic support: offer hands-on training, simple reference materials and a process for reporting system failures.
6. Adjust performance expectations: allow for learning time and avoid judging employees by old targets while they are mastering new procedures.
7. Review and communicate: share what has improved, what remains difficult and what will change next.

This approach treats resistance as information to investigate rather than an obstacle to crush. It also recognises that successful adoption depends on capability and trust, not merely on announcing a decision.

Questions to Consider

• What specific loss or risk might each affected group be worried about?
• Have employees been given enough information to understand the reason for the change?
• Which parts of the plan can employees help improve?
• Do people have the training, equipment, time and authority needed to adopt the new way of working?
• What previous organisational experiences may be shaping current scepticism?
• How will leaders know whether resistance reflects a valid operational problem?
• What will managers do when the first implementation problems appear?

Key Takeaways

• Resistance to change often reflects uncertainty, loss of control, low confidence, workload pressure or weak trust rather than simple stubbornness.
• Separate constructive challenge, which identifies risks and improvements, from deliberate obstruction.
• Diagnose concerns by listening to employees and examining the practical effects of the proposed change.
• Explain why change is necessary, what will be affected and what remains uncertain.
• Involve employees in practical design, provide realistic training and adjust workloads during transition.
• Build trust by acknowledging problems, acting on useful feedback and communicating consistently.