'How Do You Handle a Team Member Who Resists Change?' Interview Answer: Examples

Answer the resists-change question with a method that treats resistance as information: find out what it is protecting, involve the person in how the change is done, show the change working on something small, and hold the line on what is changing. It is the other side of how do you handle change, it belongs with how do you motivate a team, and the conversation at the centre of it uses the skill in a time you persuaded someone. This page explains what the interviewer is really asking, gives a structure that works, three sample answers of forty to eighty words to adapt, the mistakes that sink the answer, and a ten-minute practice routine.

What the interviewer is asking

Whether you see resistance as a problem person or as a signal, whether you can hold a direction while flexing on the method, whether you have patience for the second and third conversation, and whether you know when patience has to end. Interviewers for management and lead roles ask it because every change produces a resister, and the weak responses, steamrolling and giving up, both cost teams. The strong answer has a curious first conversation, a concrete involvement, a small win and a limit.

A structure that works

1. Ask what it is protecting: a skill they are proud of, a workload they fear, a past change that went badly.
2. Involve them in the how: give them a real part of the implementation, often the part they worried about.
3. Show it small: a pilot or one week, with the result visible.
4. Hold the what: the change is happening; the method and the timing can flex; and name the point where resistance becomes a performance conversation.

Three sample answers

Manager

When we moved to a new ticketing system, my most experienced technician refused to use it and kept a paper log. I sat with him and asked what the problem was, and it was not the software; it was that the old system had his fifteen years of notes and he thought they would be lost. We migrated his notes together over two afternoons, I asked him to write the team's quick guide because he knew the edge cases, and within a month he was the one correcting everyone else. If the resistance had continued after that, it would have become a different conversation, and I told him so kindly at the start.

Team lead

Resistance usually means someone has not been asked. On a process change in our warehouse, one of the pickers kept doing it the old way. I asked him to walk me through the old way, and he showed me two steps the new process had actually made slower. We fixed those, which made the change better for everyone, and I asked him to run the first week on his aisle as the pilot. He went from resisting to owning it. I think the mistake people make is deciding the person is difficult before they have heard the reason.

Peer

I am not always the one in charge, so sometimes it is a colleague resisting a change I need. I do not try to win the argument; I ask what their concern is and whether there is a version of the change that handles it. On a reporting change, a colleague thought it would take her twice as long. We timed it together for a week; it took longer for three days and then less. The evidence did what the argument would not have. And where I cannot persuade, I take it to the person who decides, with both views.

Mistakes that sink the answer

• Treating the resister as a problem to be removed from the start.
• Giving up on the change because someone objected.
• A story with no curious conversation in it.
• No limit; interviewers want to know you know when patience ends.
• A story where the resister turned out to be simply wrong and you simply won.

A ten-minute practice routine

1. Write your four steps, including the limit.
2. Pick one real resister and write what their resistance turned out to be protecting.
3. Add the involvement you gave them and the small win.
4. Say it aloud in under ninety seconds.
5. Answer it in the browser demo or a mock interview and compare with the structured answer.

Where CoPilot Interview fits

CoPilot Interview is an AI interview assistant whose browser demo at /try lets you answer this question aloud and compare your answer with a structured one, free and with no signup, and whose free AI mock interview asks it in the context of your résumé and the job description and scores your spoken answer out of ten. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Practice is the use nobody objects to; if you consider live help in a real interview, follow your employer's rules.

Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.

Frequently asked questions

How do you answer 'how do you handle a team member who resists change'?

Find out what the resistance is protecting, involve the person in how the change is implemented, show it working on something small, hold firm on what is changing, and name the point where it becomes a performance conversation.

Should I say I would remove someone who keeps resisting?

Say that persistent resistance after genuine involvement becomes a performance conversation with a clear expectation. Say it calmly and after the patient steps, not instead of them.

What if I am not a manager?

Describe the peer version: ask the concern, test a version of the change together, and escalate with both views if you cannot agree.

How long should the answer be?

Sixty to ninety seconds.