Resistance Is Information

Every improvement leader has felt it. The change is sound. The evidence is clear. The workflow has been thought through. And somewhere in the organization, people are not doing it.

The reflex is to explain this as a problem with the people. They are set in their ways. They do not see the bigger picture. They need to be reminded, retrained, or, eventually, held accountable. That reflex is understandable and it is almost always wrong. Resistance is not a character trait. It is information, and it is usually the most honest information a change will ever receive.

What resistance actually looks like

Open refusal is rare. In healthcare organizations, resistance is quiet and it is reasonable-looking. It is a screening tool that is always in the file and never scored. A new step that is done when the manager is on the unit and skipped when she is not. An exception that gets invented on night shift because nobody wrote one down for days. A form completed correctly and a behavior that never changed. Compliance without adoption.

None of these people are refusing. Each is solving a problem the change created for them, in the only way available. Read that way, resistance is a map of where the change does not yet fit the work.

What it is telling you

Resistance almost always signals an unmet need, and the needs come in a few recognizable kinds.

Time. The change costs minutes that the day does not have. In an organization running short, every added step is subtracted from something, and the person doing the subtracting is the one being called resistant. Until the plan gives the time back somewhere, no explanation of the benefits will land, because the benefits are not the problem.

Belief. The person does not think the change helps, or thinks it harms something they value. This is a professional conviction, not stubbornness. A manager cannot argue it away, and trying tends to harden it. Only a trusted peer, someone who shares the craft and has done the new thing, can speak to belief.

Competence. The person is not confident they can do the new thing well, and would rather not do it than do it badly in front of colleagues or patients. This looks like avoidance. It is fear, and it responds to practice, not reminders.

Load. The change is the fourth change to land on the same people this year. There is nothing wrong with it. There is no room for it. This resistance is about timing and it is the easiest to misread, because the person is not objecting to the change at all.

Control. The change was designed somewhere else and handed down. People who had no part in shaping it will find its flaws quickly, and they will be right about most of them. This resistance is about ownership, and it is cured by involvement rather than persuasion.

Each of these needs a different response. Training treats one of them. Reminders treat none of them. This is why “more communication” so rarely works: it answers a question nobody asked.

The most resistant people are often the most valuable

Here is the idea that changes how a leader sees the room. The people who push back hardest are usually the ones who understand the workflow best and care most about the work. They see what the change will break because they are the ones who will have to live with it. Their objection is often the most detailed description of the real process that the improvement team will ever get.

Treated as opposition, they become the reason the change fails. Treated as informants, they become the reason it works. The difference is entirely in the leader’s response.

How to listen

Listening to resistance is a skill, and it has a shape.

Ask why, in person, and let the answer be long. The first reason given is rarely the real one. Ask again.

Separate the kinds. Is this about time, belief, competence, load, or control? Two people saying no to the same change may be saying it for opposite reasons, and one plan will not answer both.

Send the right listener. A supervisor can hear a time problem. Only a peer can hear a belief problem.

Look for the workaround before the complaint. The workaround is what people do when they have stopped bothering to object. It is resistance that has gone quiet, and it is the most important kind to find.

Write the exceptions down. When people invent their own, the change looks optional. When the team agrees on them and posts them, the change looks designed.

What changes when resistance is data

The response becomes specific. Instead of a reminder to everyone, there is a fix for the time problem, a peer conversation for the belief problem, practice for the competence problem, a schedule change for the load problem, and a seat at the table for the control problem.

The plan gets better. Resistance found early, during a small test, is a design input. Resistance found late, after a full launch, is a failure report.

And trust builds. People who see their objection turned into an adjustment will bring the next objection sooner. That is the beginning of an organization that improves easily, and it starts with one leader deciding that pushback is something to read rather than something to overcome.

Improvement methods are good at finding what is wrong with a process. Resistance tells you what is wrong with a change. The tools for hearing it, and for responding to each kind, are mapped to the steps of the cycle on our PDSA page and our DMAIC page.