Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Transformation management and PMO

Resistance to change: reading the symptoms, treating the causes

In brief

Resistance to change refers to the behaviours by which people slow down, work around or refuse a new way of working. Management Square treats it here as a symptom to diagnose: the signs to note, the four possible causes (not knowing, not being able, not wanting, not being required to) and the remedies ranked in order of effort.

Page contents

Take a finance department where a new expense claims application has been in service for a few months. The accountants continue to ask for receipts by email, managers approve in batches at the end of the month, and the usage curve presented to the steering committee has stopped rising. The project manager sums up the situation in three words: resistance to change.

The expression refers to all the behaviours by which people slow down, work around or refuse a new way of working. It describes what can be seen, without saying anything about what produces it. Used as an explanation, it closes the discussion and puts the blame on users. Treated as a symptom, it opens a diagnosis: note the signs, trace back to the cause (people do not know, cannot, do not want to or are not required to), then apply the lightest remedy that addresses it.

The symptoms: what can be seen and what goes unsaid

The visible signs are in the project’s data. Usage plateaus, or is limited to the operations that a control makes compulsory. Parallel channels persist: spreadsheet, email, old screen. Requests for exceptions multiply. Entries arrive late or incomplete. Places remain empty in training sessions. The help desk keeps receiving the same questions.

The silent signs require more attention. A team that asks no questions has often stopped trying. A manager who passes on instructions by attributing them to the project (“they’re asking us to…”) signals to their team that they do not endorse them. This passive resistance is harder to deal with than open objection, which at least has the merit of giving its reasons.

Where the symptom appears is a clue. A general drop-off points to the tool or the message. A drop-off limited to one site, one team or one step of the process points to a business scenario, a manager or a local workload. Before any hypothesis, usage figures therefore need to be broken down by population.

Behind resistance to change: knowing, being able, wanting, being required

The same symptom can have four origins, which do not call for the same response. What is heard on the ground gives direction; an observable fact must confirm it.

Cause What you hear What confirms it
People do not know “Nobody told us it was compulsory”, “I can’t find where to do it” Errors are concentrated on the same screens; the announcement went out once, through a single channel
They cannot “My case isn’t covered”, “it takes me longer than before” A real case is missing from the tool; the go-live falls in an already busy period
They do not want to “Before, I used to sort this out myself” The change removes a degree of autonomy, recognised expertise or a direct contact
They are not required to “My manager prefers the old spreadsheet” The old way remains open; neither objectives nor controls have changed

The fourth cause is the easiest to miss, because it produces no complaints. A team adjusts its practice to what its direct manager asks for and checks. In a matrix organisation, the project makes the request while the line management assesses people: if line management does not pass on the requirement, it remains optional.

The second cause has a collective variant. When several projects call on the same team at the same time, no support arrangement creates the time that is lacking: the trade-off falls under project portfolio management.

This classification sets aside explanations based on people’s temperament or the company culture. Even when accurate, they point to no action to take.

When resistance is right

An objection can be right against the project. What remains is to sort them. The test is simple: can the objection be reproduced on a real case, in front of the project team? If so, it stops being an opinion. It becomes a defect or a change request, with a priority and a response date communicated to those who raised it.

It also happens that the change is genuinely unfavourable to a population: a data entry task is transferred to it, a check is added, some latitude disappears. Presenting it with a benefit it will never see destroys the project’s credibility. It is better to name the loss, say why the organisation considers it acceptable and what is planned in return. This decision belongs to the sponsor, and it is management that explains it.

The remedies, from the lightest to the heaviest

The first remedy costs only attention: qualify. A few interviews, usage figures by team and observation of a case handled from end to end are usually enough to identify the dominant cause.

Next comes restating the expectation, when people do not know. It is expressed by the direct manager, and says what is compulsory, from when, and whom to turn to when a case is blocked. A short guide per role accompanies it.

One step up, fixing irritants addresses the “cannot”: handling the missing case, removing a mandatory field that serves no purpose, adjusting access rights. Added to this are a lighter workload during start-up and additional training on the real situations that cause difficulty. As long as an everyday case remains impossible in the tool, no message will make it usable.

The next effort is managerial. Closing the old way on an announced date, aligning objectives and controls with the new practice: these measures require a decision by the sponsor and the commitment of line management.

Dealing with loss takes the longest. When the role or the job changes, responsibilities have to be redefined, experts in the old system given a place and, if the content of jobs is modified, human resources and staff representatives involved. This work calls for a complete set-up, from impact analysis to measuring adoption, which our service page on change management describes workstream by workstream.

As a last resort, it is the project that is revised: phased roll-out, reduced scope, an exemption granted to a population by an explicit and dated decision.

This order has a practical reason. Light remedies also serve as a test: if a clear reminder from the direct manager changes nothing, the cause lies elsewhere. The opposite mistake is costly. Relaunching a communication campaign or retraining everyone when a business scenario is missing wears out teams’ patience without touching the problem.

Checking that the treatment is working

The check concerns the symptoms noted at the outset, where they were noted: use of key functions in the team concerned, volume of the parallel channel, nature of help desk requests. A remedy that has shifted nothing after being genuinely applied invalidates the diagnosis, which then has to be revisited.

Before the next committee, pick the team where usage is dropping off most and follow a real case there from end to end, with the person handling it. Note what they do instead of what was planned, what the tool prevents them from doing and what their manager asks of them. These three answers identify the cause, and therefore the first remedy to apply.

Insights

Further reading

All insights

FAQ

Frequently asked questions

Another question? Ask us

What is resistance to change?

Resistance to change covers the behaviours by which people slow down, work around or refuse a new way of working: minimal use of a tool, keeping the old channels, repeated objections, silence. The term describes an observable effect. It says nothing about the cause, which may lie in the information received, the ability to do the work, what the person loses or what their management actually requires.

What are the causes of resistance to change?

They fall into four families. People do not know what is expected or how to do it; they cannot, because the tool, the time or the skill is lacking; they do not want to, because they lose something or judge the change badly designed; they are not required to, because the old practice remains possible and nobody demands the new one. Several causes can coexist within the same team.

What is the difference between active and passive resistance?

Active resistance is voiced: objections in meetings, declared refusal, referral to staff representatives. Passive resistance is not spoken: people agree, then carry on as before or use the new tool only to the minimum required. The first is more uncomfortable and simpler to deal with, because it gives its reasons. The second requires going to observe the real work.

Is resistance to change always a problem?

No. Some objections point to a real flaw in the project: a forgotten business scenario, a task that has become longer, a check that has become pointless. It is better to hear them during a pilot than after general roll-out. Resistance becomes a problem when it persists although the flaws have been fixed and the expectation has been clearly set by management.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.