Change Resistance: Turn Pushback into Progress

A new process is announced on Monday. By Tuesday, the same questions are circulating: “Why are we changing this?”, “Who decided?”, and “Will this create more work?” By Friday, people are still using the old spreadsheet, old handover method or old customer script. Change resistance is not an inconvenient interruption to the plan. It is the point at which a manager’s credibility, communication and leadership are tested.

The instinct can be to push harder: repeat the deadline, issue another instruction and label the hesitant people “negative”. That approach may create short-term compliance, but it rarely creates commitment. People may follow the new process while you are watching, then quietly revert when pressure rises.

A better manager does not treat resistance as defiance by default. They treat it as information. Something may be unclear, impractical, risky, poorly timed or personally unsettling. Your job is to find out what it is, respond with purpose and help people make the change real in their everyday work.

Why change resistance is useful information

Resistance often sounds emotional, but it usually has a practical cause. A customer service adviser may worry that a new system will slow response times. A supervisor may fear losing control of work they understand well. An experienced colleague may feel that their hard-earned expertise is being dismissed. A team already carrying a heavy workload may simply see no capacity for another initiative.

These concerns are not all equally valid, and leaders should not promise that every objection will change the decision. Yet listening properly can reveal risks that the project team has missed. It can also show whether people understand the purpose of the change, know what is expected of them and believe they will be supported through it.

The key distinction is between resistance to the goal and resistance to the route. A team may agree that customer complaints must reduce, while questioning whether the proposed process will achieve that result. If managers confuse those two issues, useful challenge gets shut down and poor decisions become harder to correct.

What sits behind resistance to change?

People rarely resist a change simply because it is new. They resist what the change appears to mean for them. In practice, the most common drivers are loss, uncertainty, lack of trust and lack of capability.

Loss of control, status or familiarity

Even a positive change can involve loss. A colleague who has built a reliable way of working may lose confidence when asked to adopt unfamiliar tools. A team leader may feel their authority is reduced when decisions move elsewhere. Others may lose the comfort of predictable routines.

Do not dismiss this with “You will get used to it.” Acknowledge what is changing and explain what will remain stable. People cope better when they can see that their experience still has value and that they will retain some influence over how work is carried out.

Uncertainty and rumour

Where information is incomplete, people fill the gaps themselves. If a restructure is mentioned without a clear timetable, rumours can travel faster than facts. If a new target is announced without explaining how performance will be measured, staff may assume the worst.

Managers do not need every answer before speaking to their teams. They do need to be honest about what is known, what is not yet decided and when the next update will arrive. Silence is not neutral. In a period of change, silence is usually interpreted as concealment.

A credibility gap

Staff judge a change partly by its history. If previous initiatives were announced with energy, then abandoned a month later, people have learned not to invest. If senior leaders say “your views matter” but decisions are repeatedly made without consultation, the issue is not communication skill. It is trust.

Trust is rebuilt through visible follow-through. When you ask for feedback, show what happened to it. When you make a promise about training, provide it. When the plan changes, explain why. Consistent action carries more weight than a polished presentation.

No confidence in the new way of working

Some resistance is a capability problem in disguise. A person may say a new system is unnecessary when what they really mean is, “I am not confident using it and I do not want to look incompetent.” This is especially common when teams are expected to learn while maintaining normal service levels.

Training must be close to the task, not a one-off event detached from the workplace. Demonstrate the new method, allow practice, provide simple job aids and make it safe to ask basic questions. Competence turns uncertainty into momentum.

How to manage change resistance without losing authority

Strong change leadership is not about seeking permission for every decision. It is about being clear where the decision is fixed, where people can contribute and what support will be available. That balance protects both speed and trust.

1. Make the case for change concrete

Avoid broad statements such as “We need to modernise” or “This will improve efficiency.” Teams need to understand the real problem and the practical benefit. Explain what is happening now, what it costs in time, quality, customer experience or risk, and what will be different when the change is working.

For example, do not tell a customer-facing team that a new call-handling process will “drive excellence”. Tell them that repeat calls are rising because customers receive inconsistent information, and that the new process gives every adviser a clear route to resolve common issues first time.

Then connect the organisational reason to the individual reality. What will staff need to stop, start or do differently on a normal working day? If you cannot answer that clearly, the change is not ready to implement.

2. Involve people in the right decisions

Consultation is not a vague invitation for opinions. It works best when the question is specific. Ask the people doing the work where the proposed process may fail, what customers are likely to notice and what would make adoption easier in the first two weeks.

Give teams genuine influence over practical details such as handovers, templates, training priorities and local measures of success. Do not pretend that a fixed business decision is open for debate. Straightforward boundaries earn more respect than false consultation.

A useful question for every manager is: “What do you know about this job that I need to know before we proceed?” It signals respect for expertise while keeping the conversation focused on implementation.

3. Turn the change into visible actions

Large programmes overwhelm people because they sound endless. Break the change into small, observable behaviours. Instead of asking a team to “embrace a customer-first culture”, define the behaviour: confirm the customer’s need, take ownership of the next step and record the outcome accurately.

Set short review points. In the first week, observe whether people can complete the new task. In the second, identify recurring errors. In the third, remove barriers that are still slowing the team down. This is where managers TAKE CONTROL: not by policing every move, but by making progress measurable and support immediate.

4. Prepare your supervisors before the wider launch

Employees will usually look first to their direct manager, not the slide deck from senior leadership. If supervisors cannot explain the reason for change, answer predictable questions or use the new process themselves, the message loses force immediately.

Brief managers early. Give them the practical case for change, the non-negotiables, the areas open to local input and an agreed response to difficult questions. Invite them to challenge the plan before they are expected to champion it. A manager who feels ignored is unlikely to build confidence in others.

5. Reinforce progress and deal with repeated refusal

Early wins matter because they give people evidence. Share a real example: a quicker handover, fewer errors, better customer feedback or time saved at the end of a shift. Be precise. “The new approach is working” is weak; “the team reduced incomplete forms by 30 per cent in ten days” is credible.

At the same time, distinguish between understandable hesitation and persistent refusal. Someone who needs coaching, practice or reassurance should receive it. Someone who has had clear instruction, sufficient support and reasonable time, but continues to undermine an agreed change, needs a direct performance conversation. Support and accountability belong together.

A manager’s change resistance conversation

When a colleague pushes back, do not rush to defend the plan. Start with: “Talk me through what concerns you most about this.” Listen for the operational detail beneath the emotion. Then clarify what is fixed, what can be adjusted and what help is available.

You might say: “The new reporting standard is not optional because we need consistent information across the service. But your concern about duplicate data entry is useful. Show me where it happens, and we will review the workflow before next week.” That response is firm without being dismissive. It protects the change while showing that sensible feedback has a route.

Change is rarely made successful by a single announcement. It is made successful in team briefings, coaching conversations, practice sessions and the small moments when a manager chooses clarity over assumption. Give people a reason to believe, a practical way to contribute and the skills to perform. That is how resistance becomes progress - and how you make the MAGIC happen where it counts: in the work itself.