Understanding Resistance to Change

The Psychological Core of Resistance

Before we get into formal frameworks, let's start with the human element. At its core, resistance to change is rarely a logical disagreement; it's almost always an emotional response.

Simon Sinek offers a concise and powerful perspective on this.

Sinek's point is crucial: people resist the disruption of what is working for them, fearing the loss of status, security, or competence. Your experience in customer-facing roles has likely shown you that simply presenting facts about a new product isn't enough; you must also address the customer's underlying concerns and emotions. The same principle applies tenfold to internal change management.

Furthermore, it's helpful to reframe resistance not as a problem to be crushed, but as a signal to be decoded.

This mindset shift—from battling resistance to diagnosing it—is the foundation of effective change leadership.

Frameworks for Categorizing Resistance

To move from a general understanding of fear to a specific diagnosis, we need structured frameworks. Different models offer different lenses for categorizing resistance. We'll explore a few of the most useful ones.

1. Individual vs. Organizational Sources

A fundamental way to categorize resistance is to distinguish between factors related to individual psychology and those embedded in the organization's structure and politics.

The following video provides a clear overview of these two categories.

This initial split helps you determine whether you're dealing with personal anxieties or systemic blockages. An intervention to address an employee's fear of learning a new skill is very different from one designed to address a power struggle between departments.

2. Kotter & Schlesinger's Four Reasons for Resistance

John Kotter and Leonard Schlesinger developed a classic framework that is highly practical for managers. They argue that resistance typically stems from one of four situations.

Here is a summary of the four key reasons:

• Self-Interest: People are focused on what they will lose (e.g., power, status, convenience, or even their job).
• Misunderstanding & Lack of Trust: People resist when they don't understand the purpose of the change or they distrust the people leading it.
• Different Evaluations: People genuinely disagree with the rationale for the change. They may have different information or see the situation from a different perspective, leading them to believe the change is a mistake.
• Low Tolerance for Change: People fear they won't be able to develop the new skills and behaviors required of them.

3. A Multi-Faceted Psychological View

For a more granular view, we can turn to a model that breaks resistance down into more specific psychological, social, and political drivers.

This model shows the complexity you'll face. For example, resistance from an engineer could be partly Pragmatic (they don't feel they have the skills), partly about Identity (their role as a "monolith expert" is threatened), and partly Political (they feel their team is losing influence).

Visualizing the Sources of Resistance

Mind maps can be a great way to consolidate these frameworks. These two images provide excellent visual summaries of the different ways to categorize resistance.

As you can see, while the labels differ, the underlying concepts—fear, loss of control, social pressure, and conflicting interests—are consistent across all models.

Application Exercise: Diagnosing Resistance at AlphaTech

Now, let's apply these concepts to the "Project Phoenix" transformation. In our last lesson's readiness assessment, we flagged Motivation/Desire and Capability/Know-how as "Red" or "Amber" for groups like the senior engineers and the sales team. Your task is to use the Kotter & Schlesinger framework to diagnose the likely sources of this resistance for these two groups.

Your Task:
Complete the table below. For each group, brainstorm the specific reasons they might resist the change, categorizing your points under the four headings.

(Take about 15 minutes for this exercise. There are no perfect answers; the goal is to practice applying the framework.)

This exercise demonstrates that "resistance" is not a single entity. The engineers' resistance is likely rooted in identity and technical evaluation, while the sales team's resistance is driven by financial incentives and customer-facing risks. By diagnosing the specific sources, you can now design targeted interventions, which we will cover in later lessons.

Conclusion

In this lesson, you moved from identifying the presence of risk to diagnosing the sources of resistance. This is a fundamental shift from a reactive to a proactive approach to change management.

Key Takeaways:

• Resistance is a natural and often emotional reaction to perceived threats, rooted in fears of loss—of control, status, competence, or security.
• Effective change leaders treat resistance as data. It's a signal that provides valuable insight into misalignments, legitimate concerns, and hidden anxieties.
• Categorizing resistance allows for targeted strategies. Using frameworks like Individual vs. Organizational or Kotter & Schlesinger's Four Reasons helps you move beyond a generic response and address the specific drivers for different groups.
• Different groups resist for different reasons. A one-size-fits-all communication plan will fail. Your strategy must be tailored to the unique self-interests, beliefs, and fears of each key stakeholder group.

Preview of the Next Lesson:

Now that we have explored resistance at the individual and group levels, we need to zoom out and examine a powerful, systemic force that shapes how everyone in the organization responds to change: the organizational culture. In our next lesson, you will learn to analyze organizational culture using the Competing Values Framework. This will help you understand how "the way we do things around here" can be either a major accelerator or a formidable barrier to your transformation efforts.