How to Uncover Organizational Resistance to Change: Warning Signs of Hidden Employee Resistance

When working with global organizations on digital transformations and other change initiatives, we frequently encounter executives who are confident that resistance will not be a problem. They believe their teams are adaptable and that significant investment in change management is unnecessary. They are almost always wrong. Resistance to change is one of the most predictable threats to any transformation, and the most dangerous resistance is the kind that hides beneath the surface. This post explains the two types of resistance, where it comes from, and the specific warning signs that predict trouble ahead.

The Two Types of Resistance

Resistance to change is not a single phenomenon. It comes in two distinct forms, and understanding the difference is essential to managing it.

Intentional Resistance

When asked about resistance, most leaders immediately think of intentional resistance: the people who have openly resisted change in the past, or those who are visibly attached to a particular system or process. Using the well-known iceberg analogy, intentional resistance is the part that sticks out above the water. It is visible, identifiable, and relatively easy to plan for.

Unintentional Resistance

What most executives fail to realize is that the majority of resistance does not come from the people openly opposing the initiative. It comes from the quiet group who do not even realize, at first, that they harbor resistance. These are the unintentional resisters, and if they are not identified and realigned, they can derail an entire implementation.

A common example: people begin to realize that their unique workarounds to the current system will no longer apply. Maybe it is a customized spreadsheet or a siloed application that will be automated by the new system. These employees understand the broader need for change and genuinely believe the transformation is best for the company. But underneath that support is a quiet concern that their personal value to the organization may be at risk. Identifying these cases early is critical to crafting the right messaging and alignment.

Why Expressed Readiness Is Not the Same as Actual Readiness

Many clients believe their teams are ready for change because the teams say they are ready. People understand the need for change, especially when existing systems are outdated and frustrating. This initial enthusiasm seems promising, but assuming it guarantees a smooth transition is a serious misstep.

Expressing a desire for change and agreeing with its theoretical benefits is not the same as being ready for the practical reality of change. Employees are not being insincere when they express readiness. They simply do not yet comprehend the full intricacy of what the change will require. The real test of adaptability comes when they encounter the practical implications, including:

• New processes that require unlearning old habits
• Changed roles and reporting structures
• Lost workarounds and informal shortcuts
• Unfamiliar ways of working with new tools
• New skills and competencies required to perform their jobs

This is why a structured organizational change management program, grounded in an honest readiness assessment, matters so much. Surface enthusiasm is not a substitute for genuine readiness.

Warning Signs of Hidden Resistance

Beyond the two types of resistance, there are specific warning signs that predict trouble. The earlier you recognize these, the more time you have to address them.

Executives Over-Delegating to the Project Team

A key warning sign is when executives excessively delegate decision-making to the project team. Transformation that aims to improve efficiency, establish a common operating model, or drive significant process improvement must be directed from the top. Relying solely on the project team or software vendors is insufficient.

Without executive leadership, the project team often takes the easiest route: maintaining the status quo. This results in adopting new technology while retaining outdated processes. When the executive team sidesteps its responsibility and leaves the project team without a clear vision, the team will tend to replicate existing methods with new tools rather than driving genuine change.

We Have Always Done It This Way

One of the clearest signs of resistance is adherence to the idea that processes should not change because that is how they have always been done. When stakeholders cannot articulate why a process exists or why it should not be altered, that inability is itself a sign of resistance. This mindset obstructs the identification and implementation of genuine improvements.

The Regulatory Excuse

A subtler form of resistance is the regulatory excuse. Team members may claim that a process cannot be modified due to customer demands or regulatory requirements. Sometimes this is genuinely true. But it is also frequently used as a defense against change. It is essential to distinguish real regulatory constraints from those cited merely as an excuse to avoid changing.

Lack of Understanding

Employees often resist change simply because they do not understand it. They may be unclear about why the change is happening, what it means for them, or what the broader purpose of the transformation is. Clear communication of the vision is essential, including how it benefits the organization, individual work groups, and each employee.

Just as important is clarity about the post go-live landscape. Employees need to understand how their roles and responsibilities will evolve. If they cannot envision their place in the transformed organization, they will revert to familiar practices and seek comfort in the known.

Undefined WIIFM (What Is in It for Me)

A common driver of resistance is the absence of a clear personal benefit. Beyond explaining how roles, processes, and tools will change, organizations need to articulate how the transformation will benefit individuals in performing their work. If employees do not recognize a personal benefit, they may not only hesitate but actively resist. People need to understand both their role in the larger organizational vision and the direct advantages they stand to gain.

Excessive Software Customization Requests

When a transformation generates numerous requests for software customization, it is worth re-evaluating those requests carefully. Often, customization demands are less about the software’s inadequacies and more about organizational resistance. An employee accustomed to a particular process might request changes to make the new software behave like the old system.

In many project recoveries and expert witness assessments, excessive customization emerges as a central issue. But the root cause is usually not that the software was deficient. It is inadequate change management and unaddressed resistance. Software customization should be viewed not just as a technical question but as a potential symptom of change management problems.

Inconsistent Business Processes

Organizations with inconsistent business processes, often the result of organic growth across multiple locations or growth through acquisition, are highly likely to encounter resistance when standardizing. Individuals have built processes tailored to their own needs rather than aligned to organizational objectives, so standardization feels like a loss.

This is especially common in environments with frequent mergers and acquisitions. Before implementing new software, it is crucial to identify commonalities across existing processes and establish a standardized operating model where uniformity is the goal. Attempting standardization during implementation leads to escalating costs, extended timelines, and greater resistance. A consolidated business process optimization blueprint should be created before the implementation phase begins.

Undefined Job Roles

When employees lack clarity about their future responsibilities, they are more likely to resist. Roles, responsibilities, and expectations should be designed deliberately so that by the time new technology is deployed, employees fully understand and accept their new roles.

This work should happen as early as possible, because it is heavily affected by process improvements. As the future operating model takes shape and processes are re-engineered, job roles inevitably change. Rather than vaguely telling someone their role will become more strategic or will be automated, organizations should explain clearly what that means in practice. If a role is being automated, outline how that person’s time will be reallocated. Clarity prevents the resistance that comes from ambiguity.

A Real-World Example of Misalignment Resistance

Consider a consumer goods distributor that was directed by its parent company to implement SAP across all divisions. Before the implementation, the small distributor had built a successful business by carving out a niche and maintaining an entrepreneurial, get-it-done culture.

It did not take long for employees to realize that the procedural mandates coming with the SAP implementation and the parent company’s standardization efforts would put that entrepreneurial spirit at risk. The resistance that emerged was not about the software. It was about a perceived threat to the culture and the autonomy that had made the business successful.

This is a textbook example of misalignment resistance. The technology was sound, but the human and cultural implications were underestimated. Anticipating this kind of resistance and addressing it through deliberate change management is what separates successful standardization efforts from contentious ones.

Questions We Hear Most

How Do You Identify Unintentional Resistance Before It Becomes a Problem?

The most reliable method is a structured organizational readiness assessment conducted early in the project. This combines anonymous quantitative surveys about culture, leadership, and communication with qualitative focus groups that go deeper into the organization’s dynamics. Because unintentional resisters often do not recognize their own resistance, you cannot rely on simply asking people whether they support the change. The assessment surfaces the hidden concerns that predict where resistance will emerge. Doing this during Phase Zero planning gives you time to address those concerns proactively.

Is All Resistance a Bad Thing?

Not necessarily. Resistance sometimes surfaces legitimate concerns that the project team should address, including:

• Genuine regulatory constraints
• Real operational risks
• Processes that actually do provide competitive advantage
• Customer commitments that cannot easily be changed

The goal is not to eliminate all resistance but to understand it. Some resistance points to problems worth fixing. Other resistance is rooted in fear or attachment to the familiar and needs to be managed through communication and engagement. Distinguishing between the two is a core change management skill.

What Is the Most Overlooked Source of Resistance?

Excessive customization requests. Most organizations treat customization as a purely technical conversation about whether the software can do what they need. In reality, a flood of customization requests is often a symptom of unaddressed resistance, with employees trying to make the new system behave like the old one. Recognizing customization as a potential change management signal, rather than just a technical requirement, is one of the most valuable shifts in perspective a transformation team can make.

If your organization is preparing for a transformation and wants help identifying and managing resistance before it derails the project, contact us at eric.kimberling@thirdstage-consulting.com.