It's interesting how quickly we label people. A new system is introduced, priorities shift, a team is restructured, or a different way of working is proposed. When people ask questions, express concern, or don't embrace the change as quickly as expected, it is easy to call them "resistant."
To be fair, sometimes they are. Most of us have encountered someone who prefers the familiar, even when the familiar is no longer working particularly well. Change can be inconvenient, uncomfortable, and disruptive, and not everyone approaches it with the same level of openness.
But resistance can also be a convenient explanation that keeps us from looking more closely at what people are actually reacting to. Once the label has been applied, their questions may sound like excuses, their hesitation may look like negativity, and their concerns may become something to overcome rather than something worth understanding.
People rarely experience change only as a new process or strategic direction. They may also experience it as a possible loss of competence, influence, stability, connection, or control. What appears straightforward from the conference room can feel very different to the person trying to understand what the change means for their work and their future.
A new technology may look like an opportunity to improve efficiency. An employee may be wondering whether the expertise they have spent years developing will still be valued. A restructuring may make sense on an organizational chart while leaving someone uncertain about where they belong, who they can rely on, or whether their role is secure.
That does not mean the organization should stop moving forward. It does mean there may be more underneath the reaction than an unwillingness to change.
I have seen leaders respond to resistance by communicating more. They schedule another meeting, send another email, or repeat the reasons the change is necessary. That can help when people genuinely need more information, but it may not help when the communication keeps answering a different question than the one employees are asking.
Leaders may be explaining what is changing and when it will happen. Employees may wonder whether the decision was made with a realistic understanding of their workload, whether they will receive meaningful support, or whether anyone is willing to acknowledge what they may be giving up. More information about the plan does not automatically answer those questions.
Listening for the concern underneath the resistance can give leaders a clearer picture of what is happening. Perhaps people do not understand the direction. Perhaps they understand it but do not trust the process. They may see a problem leadership has missed, or they may be carrying frustration from previous changes that were announced with optimism and handled poorly.
Not every concern will be reasonable, and not every objection can determine the outcome. Listening does not require a leader to surrender authority, seek unanimous agreement, or abandon a decision because it makes someone uncomfortable. A leader may understand the concern and still decide that moving forward is the right choice.
However, there is value in making that decision with a fuller understanding of what people are being asked to navigate. Leaders can be clearer about what has already been decided, what remains open for discussion, and where employee input can genuinely influence the process. That kind of clarity is often more respectful than inviting feedback when it can't realistically affect anything.
The same is true when leaders do not yet have every answer. Most people recognize that organizational change comes with uncertainty. Acknowledging what is still unknown can feel more credible than offering reassurance that reaches beyond what anyone can confidently promise.
Emotional intelligence matters here because resistance can trigger emotional reactions on both sides. Employees may feel anxious, overlooked, or frustrated. Leaders may feel challenged, impatient, or defensive, particularly when they have invested significant time in a decision and believe they are acting in the organization's best interest.
Those reactions can make it harder to remain open long enough to understand what is being communicated. A question can sound like defiance. A concern can feel like a lack of trust. A leader's confidence can be experienced as unwillingness to listen, even when that was not the intention.
Before calling someone resistant, it may be worth getting closer to what they believe is at stake. Are they asking for more clarity, more support, more influence, or a more honest acknowledgment of what could change? Are they reacting to this decision, or to what earlier decisions have taught them to expect?
The answer may not change the direction. It may change how the change is led, what support people need, or how trust is protected along the way. At the very least, it helps leaders respond to what is actually happening rather than to the label they have placed on it.