liveBook · Manning

Resistance to change

As explained in Interview Speak

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

Resistance to change is reluctance to accept a new idea, process, or way of working. In an interview, the useful story is not simply that others eventually agreed with you. It shows that you can understand objections, connect a change to other people’s priorities, help implement it, and produce a positive result. section 4.7 section 6.13

Build a convincing example in a clear sequence:

  • Start with a beneficial idea and name who resisted it and why. Avoid treating resistance as irrational; show the concern behind it. section 6.13
  • Learn the perspectives of affected people. Ask questions, gather relevant information, and identify what matters to them. section 4.7
  • Explain the benefit in terms of “what’s in it for them,” including how work may become easier after an initial learning period. section 4.7 section 6.13
  • Support the proposal with concrete evidence, such as CRM data and real-world examples, rather than relying on confidence alone. section 4.7
  • Describe approval, implementation, and results. Include how early resisters responded after the change when possible. section 6.13

Turning sales-strategy skepticism into support

A sales team resists reaching a new customer segment because traditional members believe the current targets are correct. A stronger response explains that the market is changing, then shows how you consulted customers and colleagues, combined their input with CRM data, and presented benefits for the team. The point is to demonstrate listening, evidence, shared benefit, and participation in implementation—not merely insistence on being right. section 4.7

Beware of answers built on broad claims such as “people listen to me” or “it was a no-brainer.” Direct conversation can help, but a persuasive account must make the resistance, the specific response to objections, and the outcome visible. Saying that a change is obvious does not show why another department would accept it. section 6.13

Prepare an authentic example before the interview. Ask yourself what created the resistance, what you said or did to gain acceptance, and how you would improve an occasion when persuasion failed. These questions help turn a general claim of influence into a specific, reflective story. section 4.13

How Interview Speak covers it

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 it assumes
Assumes you can recall a workplace change and identify resistance, actions, acceptance, and lessons learned.
What you can do after
Practice/perform an interview response that shows how you gained acceptance for a change.
How it connects
Connects resistance to change with persuasion, influence, objections, implementation, and smooth transitions.

Also explained in

Compare how 2 books explain resistance to change →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Interview Speak. The section links point to the parts of the book it draws on.