Stop Calling It Resistance Before You Understand It

Leaders introduce a change and the response is not what they expected.

People question the plan.

Adoption is slow.

Old workflows continue.

Someone says the frontline is resistant.

Sometimes that may be true. But the label often arrives before the understanding.

Resistance is frequently information in disguise.

If we dismiss it too quickly, we may lose the clearest signal that something in the plan needs attention.

🧭 Today, We Go Off the Clinical Path…

Change looks different depending on where you stand.

From the project team’s perspective, a new workflow may represent months of planning, thoughtful design and a solution to a known problem. From the frontline perspective, it may arrive as a short training, a new expectation and another change to absorb during an already full shift.

Both views can be accurate.

When clinicians hesitate, they may be seeing something the project team cannot see from the conference room. The new step may duplicate existing work. The timing may create risk. The technology may not fit the exceptions that occur every day. The purpose may be unclear, or the team may remember a previous rollout that promised support and disappeared after launch.

Hesitation can also come from simple uncertainty. People may not know what is changing, why it matters, how success will be measured or whether they will be supported while they learn.

Calling all of that resistance compresses several different problems into one word.

And one word rarely gives leaders enough information to respond well.

🥾 Where the Path Gets Rough

The resistance label is attractive because it creates a simple story. The change is good. The plan is sound. The people who are not adopting it are the obstacle.

That story protects the plan from scrutiny.

It can also damage trust. Once employees believe that questions will be interpreted as negativity, they learn to stay quiet. Leaders may then see less visible pushback and assume the change is working, while workarounds and frustration continue out of view.

This does not mean every objection should stop a project. Some changes are required. Some decisions will remain difficult. Some people will prefer the familiar even when a new approach is safer or more effective.

Leadership still has to set direction.

But direction without curiosity creates avoidable blind spots.

The key is to separate the kinds of hesitation we are hearing. Is the concern about patient safety? Workflow burden? Training? Staffing? Technology reliability? Loss of autonomy? A prior experience? Or a disagreement with the goal itself?

Different concerns require different responses. More communication will not fix a flawed workflow. More training will not resolve a staffing gap. Executive sponsorship will not make an unreliable tool dependable.

Until we understand the concern, we are guessing at the solution.

🧭 Check Your Compass

Before labeling a team resistant, leaders should ask what the behavior may be telling them.

Have we explained the problem clearly enough for people to understand why change is necessary?

Were frontline employees involved early enough to shape the approach?

Does the new process work during nights, weekends, high volume and uncommon situations?

Have we made time for people to learn, or have we added training on top of full workloads?

Do employees believe their feedback will change anything?

What happened the last time this organization introduced a similar change?

Leaders should also pay attention to who is raising the concern. Experienced clinicians may recognize patterns that are not visible in a pilot. New employees may notice assumptions that everyone else has stopped questioning. Informal leaders may be expressing what others are reluctant to say.

The goal is not to agree with every concern. It is to understand what evidence the concern contains before deciding what to do with it.

💡 A Different Direction

What if we treated resistance as part of change design rather than a problem that appears after design is complete?

Teams could test proposed workflows with the people who will use them, including those most skeptical of the change. Project plans could include time to investigate friction, adapt training and address exceptions before full rollout.

Leaders could replace broad questions such as ‘Do you support this?’ with questions that produce useful detail: Which part of this workflow will be hardest to complete? What could make it unsafe? What step will people work around? What would help you trust the change?

That kind of conversation does not give away leadership authority. It improves the information behind the decision.

It also creates a responsibility for leaders. If we invite feedback, we should explain what we heard, what will change, what will not change and why.

People can accept a decision they did not choose more readily when they know their perspective was considered honestly.

⭐ Finding True North

Change requires movement, and movement creates friction.

The friction may come from habit. It may also come from a real problem in the path.

Strong leaders learn the difference before pushing harder.

That means staying curious when questions feel inconvenient. It means looking at the workflow through the eyes of the people expected to carry it. It means being willing to change the plan when frontline experience reveals a risk.

Resistance is often information in disguise.

We do not have to let it control every decision. But we should understand it before we decide it has nothing to teach us.

Before you label the next hesitation as resistance, ask one more question: What might this team be trying to tell us?

Until next time, keep asking questions, challenging what has always been done and finding your true north. 🧭

Off the Clinical Path—Navigating the challenges, changes and innovations shaping healthcare.