Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Says That's How We've Always Done It
Transcript
- Lucas: Luna, I want to talk about a phrase that makes every manager's eye twitch just a little. 'That's how we've always done it.' Luna: Oh, I've heard that one. Usually delivered with crossed arms and a slight head shake. Lucas: Right. And the tricky part is — the person saying it often isn't trying to be difficult. They're often your most tenured, loyal employee. So how do you handle it without crushing their spirit or letting them block progress? Luna: Before we dive in — and I know this is a tangent, but it's related to the idea of change — if this podcast has helped you navigate a tough conversation or a career decision, it's a big reason we keep doing it ad-free. A small way listeners support us is at buy me a coffee dot com slash fexingo. No pressure, just mentioning it. Lucas: Appreciate that, Luna. And it does tie in — because listener support lets us dig into these specific cases without worrying about sponsorship constraints. So let's get into a real example. Lucas: I was talking to a manager at a mid-size logistics firm. They were rolling out a simple digital barcode system in their warehouse. The cost was low, the training was two hours, and it would cut inventory errors by about 40 percent. But one senior warehouse lead — fourteen years on the job — just kept saying 'the paper system works fine, that's how we've always done it.' Luna: And I bet the manager's first instinct was to argue. Show him the error-rate data, prove him wrong. Lucas: Exactly. And that's exactly the wrong move. Because what's really going on isn't about data. It's about status quo bias. Psychologists use that term to describe our tendency to prefer things to stay the same, even when change is objectively better. For someone who's been doing a job for fourteen years, their identity is wrapped up in being the expert. Asking them to change the system feels like telling them their expertise is obsolete. Luna: So you have to separate the person from the process. Validate their contribution before you ask them to change. Lucas: That's the first step. I call it Validate, Reframe, Co-Design. So step one: validate. The manager in this case sat down with the lead and said, 'Look, you've kept this warehouse running smoothly for over a decade. The paper system you built — it's reliable because of you. I'm not asking you to abandon your expertise. I'm asking you to help me improve it.' Luna: That's a very different opening than 'here's why you're wrong.' Lucas: Completely. And once the lead felt seen, he relaxed. That's when the reframe happens. Step two: connect the change to something he actually cares about. The manager said, 'You've mentioned you hate it when the night shift mislabels pallets and you have to spend the first hour of your day fixing it. This barcode system would eliminate that entirely. You'd never have to fix a mislabel again.' Luna: So you're not selling the change on its own merits. You're selling it as a solution to a problem he already owns. Lucas: Exactly. And that worked. But the real breakthrough was step three: co-design. The manager didn't just hand him a new process. He asked, 'How would you roll this out? What would you change to make it work for your team?' Luna: So now the lead owns the rollout. That's genius. He went from resistor to champion. Lucas: He did. He suggested adding a laminated quick-reference card for the older workers who weren't comfortable with tablets. That wasn't in the original plan, but it was a great idea. And because he suggested it, he made sure everyone used it. Luna: I think a lot of first-time managers skip that co-design step. They think 'I'm the boss, I make the decision.' But that's how you get passive resistance. Lucas: Exactly. And the irony is, the co-design step often takes less time than the months of friction you'd get from ignoring it. In this case, the rollout happened in three weeks, error rates dropped, and the lead started showing off the system to new hires as 'his process.' Luna: That's the dream outcome. But what about when the person truly is just stubborn? Not a loyal expert, just someone who reflexively says no. Lucas: That's a slightly different case. If they're not a top performer and they're blocking change without any real expertise to back it up, then it becomes a performance management issue. But I'd still start with Validate, Reframe, Co-Design. You might discover they have a legitimate fear you hadn't considered. And if they still refuse after you've genuinely tried, then you escalate. Luna: So give them a real chance to be part of the solution before you label them as the problem. Lucas: Right. And one more thing: timing matters. Don't drop a big change in the middle of a busy season or right before a deadline. The status quo bias is stronger when people are stressed. Pick a moment when things are calm, and give them time to process. Luna: That's a good practical tip. So to recap: validate their contribution, reframe the change as solving a problem they care about, and co-design the rollout with them. Lucas: And if you do that, the person who once said 'that's how we've always done it' might become the person who says 'here's how we do it now.' Luna: And that's a win for everyone. Thanks, Lucas. Lucas: Thanks, Luna. See you next time.