liveBook · Manning

Resistance to change

Resistance to change is reluctance or opposition to adopting or participating in a change to established practices, processes, or ways of working.

How 3 Manning books explain it

Collaborative Software Design: How to facilitate domain modeling decisions

Resistance is a reluctance or opposition to change, participation, or confronting a problem within a group.

How it is used
Surfaces hidden obstacles to participation and shared modeling decisions during collaborative facilitation.
How deep it goes
Defines resistance, catalogs observable patterns, and gives observation and decision-framing practices without claiming motives from isolated behavior.
Examples
Uses withdrawal, sarcasm, excuses, interruptions, remote camera-off behavior, gossip, and a design-discussion withdrawal scenario.
What you can do after
Diagnose/debug with it by recognizing repeated observable patterns and clarifying buy-in before resistance obstructs participation.

Read how Collaborative Software Design: How to facilitate domain modeling decisions explains resistance to change →

Test Driven: Practical TDD and Acceptance TDD for Java Developers

Resistance to change is reluctance or opposition to adopting a proposed change.

How it is used
Addresses resistance while helping people adopt TDD and other changes in development practice.
How deep it goes
Explains how to recognize indirect resistance and offers listening, goal-setting, and other responses, with cautions about support capacity and disruption.
Examples
Uses a developer’s earlier work schedule to reveal discomfort with pair programming, and suggests financial results or an unhappy customer as signals for change.
What you can do after
Practice recognizing possible resistance, checking its causes through conversation, and choosing a response suited to the situation.

Read how Test Driven: Practical TDD and Acceptance TDD for Java Developers explains resistance to change →

Interview Speak

Opposition or reluctance among people toward accepting an idea, proposal, or change to established behavior, processes, or practices.

How it is used
Prepares you to answer interview questions about persuading people to accept beneficial changes.
How deep it goes
Provides a step-by-step answer structure from identifying resistance through implementation and results.
Examples
Uses a sales-strategy proposal and an internal customer-prioritization process change as interview scenarios.
What you can do after
Practice/perform an interview response that shows how you gained acceptance for a change.

Read how Interview Speak explains resistance to change →

Also covered in

What to know first

Related concepts

Questions about resistance to change

What is resistance to change?

Resistance to change is reluctance or opposition to adopting or participating in a change to established practices, processes, or ways of working.

Which Manning books explain resistance to change?

Collaborative Software Design: How to facilitate domain modeling decisions, Test Driven: Practical TDD and Acceptance TDD for Java Developers and Interview Speak.

What should I know before learning resistance to change?

Manning books that teach resistance to change usually introduce decision making first.

What kinds of resistance to change are there?

Kinds of resistance to change include experience-based resistance, fear-based resistance, identity-based resistance and false agreement.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.