Why the pushback inside your organization may be telling you something you need to hear
Change rarely fails because people simply “don’t like change.”
That explanation is convenient. It is also usually incomplete.
In organizations navigating a transformation—new technology, a restructuring, a new operating model, a major acquisition, an AI initiative, or a shift in strategy—resistance is often treated as something to overcome. Leaders identify the skeptics, build the change-management plan, increase communications, and try to get everyone moving in the same direction.
But what if resistance is not the obstacle?
What if it is data?
At Cybaxis, we often see resistance as one of the earliest signals that something in the transformation deserves a closer look. Sometimes the signal is about incentives. Sometimes it is about capacity. Sometimes it exposes a flawed process, an unclear decision right, or a gap between what leadership believes is happening and what employees experience every day.
And sometimes, yes, resistance is simply resistance.
The important point is that you cannot know which one you are dealing with until you listen.
“Resistance is often the organization telling you where the real work is.”
The problem with calling people “resistant”
There is a subtle but important difference between saying people are resisting change and asking what is the resistance telling us?
The first frames the employee as the problem.
The second treats the organization as a system worth understanding.
Consider a technology rollout. Leadership sees a platform that will eliminate manual work, improve reporting, and create better visibility across the business. Six months later, adoption is uneven. Teams have developed workarounds. Some employees are still using spreadsheets. Managers are frustrated.
The easy diagnosis is: They aren’t adopting the technology.
A better set of questions might be:
- Does the new workflow actually make the work easier?
- Were the people doing the work involved in designing it?
- Does the system reflect how decisions are really made?
- Are employees being measured on outcomes that conflict with the new process?
- Did the organization remove the old process, or simply add another layer?
- Do people understand why the change matters to them—not just to the business?
The answers can fundamentally change the intervention.
You may not have an adoption problem. You may have a design problem.
Listen for the signal beneath the pushback
Not all resistance sounds the same.
A frontline employee might say, “This isn’t going to work.”
A middle manager might say, “We tried this three years ago.”
A senior leader might say, “Now isn’t the right time.”
Those statements can look like different versions of the same problem. They are not.
The frontline employee may have identified a practical flaw that was invisible in the executive design process.
The middle manager may be carrying institutional memory about a previous transformation that leadership has forgotten.
The senior leader may be signaling a resource conflict, an incentive misalignment, or a concern about execution risk.
The words are the surface. The underlying signal is what matters.
This is where transformation work becomes less about communication and more about diagnosis.
Resistance can reveal hidden operating-model problems
One of the most useful things about resistance is that it often exposes the gap between the organization on paper and the organization in practice.
An operating model might say that a decision belongs to one function. In reality, three functions need to approve it.
A process map might show five steps. Employees know there are nine.
A strategy might prioritize speed. The incentive structure may reward risk avoidance.
A new technology platform might promise standardization. Individual business units may have legitimate reasons for operating differently.
None of these issues necessarily appear in an executive steering committee presentation.
They show up when people push back.
“The loudest objection is not always the most important signal. Sometimes the most valuable insight is buried inside a seemingly small complaint.”
This is why resistance deserves structured attention.
Not every objection should change the plan. But every meaningful objection should help test the assumptions behind the plan.
From “change management” to organizational intelligence
Traditional change programs often focus on helping people move from the current state to the future state.
That is necessary.
But organizations can get more value by treating the journey itself as a source of intelligence.
Think of resistance as a feedback mechanism.
If the same concern appears across multiple teams, there may be a systemic issue.
If resistance is concentrated in one part of the organization, there may be a local operating constraint.
If senior leaders support the transformation but middle management struggles to execute it, the issue may sit in accountability, incentives, or decision rights.
If employees support the objective but reject the implementation, the distinction matters enormously.
The question shifts from:
“How do we get people to accept this?”
to:
“What would have to be true for this to work?”
That is a much more productive question.
Four signals worth paying attention to
In our work, resistance tends to become particularly useful when it falls into a few recognizable categories.
1. Capacity resistance
“We don’t have time for this.”
Sometimes that is an excuse. Sometimes it is an accurate description of the operating environment.
If a transformation depends on people doing significant additional work while maintaining their existing responsibilities, resistance may be telling you the organization has not funded the transition operationally.
The answer may not be better messaging. It may be reprioritization.
2. Capability resistance
“We don’t know how to do this.”
This is different from unwillingness.
A new strategy can be perfectly sound while the organization lacks the skills, tools, leadership behaviors, or technical capabilities required to execute it.
Calling this resistance does not solve the capability gap.
Building the capability does.
3. Incentive resistance
“Why would I do this?”
This question can be uncomfortable because it forces leaders to examine whether the organization’s formal priorities match what the system actually rewards.
If employees are told to collaborate but rewarded individually, collaboration will struggle.
If leaders are told to innovate but penalized for failed experiments, innovation will remain rhetorical.
People respond to incentives, not just communications.
4. Trust resistance
“We’ve heard this before.”
This is perhaps the most difficult signal to address.
Trust is built through evidence. If previous initiatives were announced with great urgency and quietly disappeared six months later, skepticism is rational from the employee’s perspective.
The answer is not another presentation explaining why this time is different.
The answer is to demonstrate it.
The leadership challenge: listen without surrendering the strategy
There is an important caveat.
Treating resistance as information does not mean allowing every objection to dictate the strategy.
Leaders still have to make decisions.
A transformation can be strategically necessary even when it is uncomfortable. Employees can have legitimate concerns while leadership still chooses to move forward. And some resistance will come from understandable preferences for the status quo.
The discipline is to separate signal from noise.
That requires leaders to ask three questions:
What are we hearing?
Collect the concerns without immediately defending the plan.
What does the evidence tell us?
Test those concerns against data, operating realities, customer needs, economics, and the organization’s strategic objectives.
What should change—and what should not?
Some feedback should alter the design. Some should change the sequencing. Some should trigger additional investment. And some should simply be acknowledged without changing the direction.
That distinction is leadership.
A better way to approach the next transformation
Before launching the next major change initiative, consider building resistance into the design process itself.
Identify the assumptions the transformation depends on.
Then deliberately look for the people and teams most likely to challenge them.
Ask them where the plan could break.
Ask what leadership is missing.
Ask what would make the new model harder to operate than the current one.
Ask what unintended consequences they can already see.
Then do something important: close the loop.
Tell people what you heard, what you changed, and what you did not change—and why.
That last step matters.
When people see that raising a concern can influence a decision, even when the answer is ultimately “no,” resistance becomes less adversarial and more constructive.
It becomes part of the organization’s intelligence system.
The organizations that learn fastest
The most adaptable organizations are not necessarily the ones with the least resistance.
They are often the ones that know what to do with it.
They create enough psychological and operational space for people to challenge assumptions without turning every disagreement into a referendum on leadership. They distinguish legitimate friction from simple reluctance. They use frontline insight to test executive assumptions. And they treat transformation as an iterative process rather than a perfectly designed plan that must be protected from reality.
Because reality is going to show up anyway.
Usually through the people closest to the work.
“Don’t ask only how to overcome resistance. Ask what you can learn before you do.”
At Cybaxis, we help organizations turn moments of friction into better decisions—connecting strategy, operating models, technology, and execution so transformation works not only on paper, but in the real world.
If your next transformation is meeting resistance, don’t start by pushing harder. Start by listening more carefully.
The signal may be pointing directly at the work that matters most.