Resistance to Change is the predictable human, social, and system response that occurs when people perceive a change as risky, unclear, unfair, or unsupported.

Back to BoK Index
Change ManagementLeadershipAdoption

Definition

Resistance to Change is the active or passive pushback that occurs when people do not understand, trust, accept, or feel able to adopt a change. It can appear as skepticism, delay, workarounds, silence, compliance without commitment, or direct opposition.

Resistance is information. It often reveals unclear purpose, weak involvement, poor communication, capability gaps, competing incentives, or real operational risks.

History

Change resistance has been studied in organizational psychology, management, and continuous improvement for decades. Lean and Six Sigma deployments often learned that technical solutions fail when adoption, leadership behavior, and frontline concerns are not managed.

When to Use

Use resistance analysis whenever implementing new standards, layouts, systems, roles, measures, automation, staffing models, or improvement routines. It is especially important when changes affect identity, workload, authority, job security, or daily habits.

Step-by-Step

  1. Identify who is affected and how the work changes.
  2. Listen for concerns, losses, risks, and misunderstood assumptions.
  3. Separate rational barriers from emotional or political barriers.
  4. Clarify the reason for change and expected benefits.
  5. Involve credible users in design and testing.
  6. Provide training, support, and time to adapt.
  7. Align measures, leadership behavior, and reinforcement.
  8. Monitor adoption and respond to issues without blaming people first.

Examples

  • Standard work: Operators resist a new method because it ignores real material shortages.
  • Software: Users bypass a new system because old reports still drive meetings.
  • Lean deployment: Supervisors resist daily management because escalation creates blame.

Common Pitfalls

  • Labeling people as difficult instead of studying the system.
  • Communicating once and expecting adoption.
  • No training or support after rollout.
  • Ignoring informal leaders.
  • Changing metrics without changing expectations.
  • Overpromising benefits and losing trust.

Related Tools

Further Reading