Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Handle a Team Member Who Resists Change
Transcript
- Lucas: So let me paint a picture for you. It's January 2025, and a regional logistics company called SwiftLine — about 400 employees — rolls out a new warehouse scheduling platform. The software is meant to cut shift allocation time from three hours to about forty-five minutes. Within a week, the data shows that one of their most experienced supervisors, a guy named Derek who's been there twelve years, hasn't touched the new system once. Luna: He just kept doing it the old way? Lucas: Exactly. Paper printouts, whiteboard markers, the whole analog setup. And Derek's manager, a first-time manager named Priya, is stuck. She can't exactly fire her most tenured supervisor, but the team is confused — half following Derek's old process, half trying the new one. It's a recipe for chaos. Luna: I've seen this play out a dozen times. The instinct is to assume the person is just stubborn or tech-averse. But usually there's something deeper going on. Lucas: Right. And that's what we're digging into today — the specific psychology behind resistance to change, and a concrete playbook for turning someone like Derek around. Because the worst thing you can do is issue an ultimatum: 'Use the system or else.' That almost always backfires. Luna: Especially with someone who has institutional knowledge. They feel like their expertise is being devalued. Lucas: That's exactly the core of it. When Priya finally sat down with Derek — not in a formal performance review, just a twenty-minute coffee chat — she asked one question that changed everything: 'What do you worry we'll lose if we switch to the new system?' And Derek's answer was that he had built a mental model of every worker's preferences, who can't do early mornings, who needs to leave by three on Tuesdays. The old whiteboard system let him adjust on the fly. The new software felt rigid. Luna: So it wasn't about being lazy or difficult. It was about losing control and nuance. Lucas: Exactly. And that's the first step in our three-step framework — diagnose the loss. People resist change when they perceive a threat to their competence, their relationships, or their autonomy. For Derek, it was all three. He was the go-to guy for schedule wrangling. That was his identity. Luna: And step two? Lucas: Step two is what Priya did next: she gave Derek ownership of the transition. She said, 'I need your expertise to make this software work for our team. Will you be the lead tester and give me feedback on what's missing?' That reframed his role from 'resister' to 'advisor'. Suddenly, Derek had a reason to engage — the system would only get better if he helped shape it. Luna: So you're giving them a way to preserve their status while moving forward. I love that. And step three? Lucas: Step three is the simplest but most often skipped: celebrate small wins publicly. After Derek found three bugs in the software that the vendor fixed, Priya mentioned it in the team huddle. She said, 'Derek caught that the system double-counts part-timers on Fridays — we'd have been short-staffed without him.' That acknowledgment made Derek feel seen, not sidelined. Luna: And within a month, Derek was training other supervisors on the new system. Lucas: Exactly. The whole team adoption rate went from 40 percent to 95 percent in six weeks. The key insight here is that resistance is almost never about the change itself — it's about what the person believes they'll lose. If you can't name what they're afraid to lose, you can't lead them through it. Luna: That's such a useful framework. And it applies beyond software rollouts — new reporting structures, new performance metrics, even a new office layout. Lucas: Absolutely. I want to give listeners a quick way to apply this tomorrow. Next time you're facing resistance, schedule a fifteen-minute conversation and ask three questions: 'What's your biggest concern about this change?', 'What do you think we might lose?', and 'What would make this work better for you?' Don't defend the change. Just listen. Luna: And if they say 'I just don't like it' — what then? Lucas: That's actually a gift. It means they trust you enough to be honest. So you dig one level deeper: 'What specifically about it bothers you?' Nine times out of ten, the real concern surfaces. Maybe it's fear of looking incompetent, or a past bad experience with a similar change. Once it's on the table, you can address it. Luna: I want to add one nuance: there's a difference between healthy skepticism and toxic obstruction. The employee who asks tough questions but engages — that's gold. The one who actively sabotages the rollout while smiling to your face — that's a different conversation. Lucas: Great point. And the distinction often comes down to intent. A skeptic wants to make the change better. An obstructer wants it to fail so they can say 'I told you so.' In Priya's case, Derek was a skeptic. Once she treated him as a partner, he became an advocate. If someone consistently undermines the process after being given a voice, then you have a performance issue, not a change management issue. Luna: And that's when you escalate. But that's a rare case. Most resistance is just fear dressed up as logic. Lucas: Exactly. And here's a final tactical takeaway: when you announce a change, always lead with the 'why' that matters to your team, not the company's bottom line. Saying 'this software will save the company $200,000 a year' means nothing to someone like Derek. Saying 'this will get you home by 5:30 instead of 7:00 on scheduling days' — that resonates. Luna: Frame it as a benefit to them directly. I've seen managers skip that step and wonder why nobody's excited. Lucas: So to recap: diagnose the loss, give them ownership, celebrate the wins, and frame the change around what's in it for them. That's the playbook. And it works whether you're managing a warehouse supervisor or a senior engineer. Luna: If this episode gave you a practical takeaway that you'll use — and I hope it did — we want to mention that the reason these shows stay ad-free and focused on real, usable content is listener support. If you find value in what we do, you can toss a coffee our way at buy me a coffee dot com slash fexingo. It's how we keep the lights on without selling your attention. Lucas: And honestly, it means a lot when listeners chip in — it tells us we're actually helping. So thank you if you've ever done that. Now, let's pivot to a related challenge that often follows a successful adoption: how do you keep that momentum when the next change comes along? Luna: Yeah, because the Derek who fought the first change might become your biggest champion for the second one — but only if you handle it right. Lucas: Exactly. And there's research from a 2024 Harvard Business Review article that looked at teams with high 'change readiness' — they found that the single biggest predictor was whether employees felt their input was genuinely used in the last change. So every time you successfully navigate resistance, you're building a track record of trust. Luna: So the next change is easier. Lucas: Much easier. But it requires discipline. You can't just pay lip service to feedback. If an employee suggests something and you don't implement it, you need to explain why. That transparency is what compounds. Luna: And that's where many managers trip up — they ask for input, then disappear into a black box. Lucas: Exactly. So here's a final rule: after any change initiative, schedule a fifteen-minute retrospective with the team. Ask: 'What worked about how we rolled this out? What would you do differently? What should we keep for next time?' That closes the loop and builds the muscle for the next change. Luna: Great advice. And that's it for this episode of Manager Mondays. We'll be back next week with another practical toolkit for your leadership journey. Lucas: Until then, keep asking the right questions — and really listen to the answers.