Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Breaking the Thats How Weve Always Done It Mindset
Transcript
- Lucas: I was talking to a project manager at a mid-sized logistics firm last month. She had an employee who, when asked to switch to a new inventory tracking system, said 'That's how we've always done it.' And she had to navigate that exact resistance. It's one of the most common phrases managers hear when introducing change. Luna: Right, and it's not just about stubbornness. There's often a real comfort in the familiar process, even if it's inefficient. What did she do? Lucas: She started by acknowledging the employee's expertise. She said, 'You've been doing this longer than I have, so help me understand what works about the current system.' That disarmed the defensiveness. Then she asked what could be improved—without mentioning the new system yet. Luna: So she turned it into a collaborative problem-solving conversation. That's smart. Instead of selling the change, she pulled out the pain points first. Lucas: Exactly. Once the employee listed a few frustrations—like double data entry and lagging reports—she showed how the new system addressed exactly those. The employee started to see it as his idea almost. Luna: That's a classic technique: co-create the solution. But what if the employee genuinely believes the old way is better for valid reasons? Lucas: Great question. That's where data comes in. The manager can run a small pilot—two weeks with the new system on one low-risk process and compare outcomes. Numbers are hard to argue with. The resistant employee might even be the best person to lead that pilot because they know the old system inside out. Luna: Right, give them ownership of the test. That also shows you're not just imposing change from above. Lucas: Exactly. There's research on this—status quo bias is a well-documented cognitive bias. We overweight the risks of change and underweight the costs of staying the same. A study by McKinsey found that 70 percent of change initiatives fail, often because of employee resistance. But when you involve people early, success rates go up dramatically. Luna: Is there a difference between resisting change and being cautious? I think sometimes managers confuse the two. Lucas: Huge difference. A cautious employee might need more data or a slower rollout. A truly resistant one might need a different approach entirely—like peer influence. If you can get one respected team member to adopt it and show results, that often tips the scale. Luna: That's how the logistics manager did it. She got a couple of early adopters, and when the doubter saw them finish their work faster, he came around. Lucas: And that's the social proof piece. People don't want to be left behind. But I want to add something: sometimes the employee is right. The old way might be better for certain edge cases. A good manager listens for that too. Luna: So part of managing 'that's how we've always done it' is having the humility to admit when the current system actually has merit. Lucas: Absolutely. I think of a famous example from NASA. Engineers resisted using commercial software for shuttle diagnostics because they felt it wasn't proven. Turned out they were partly right—the off-the-shelf tool didn't handle some critical scenarios. So they adapted, blending old and new. Luna: That's a great lesson. Change doesn't have to be all or nothing. You can take the best of both worlds. Lucas: Exactly. And that's sometimes what the 'we've always done it this way' person is really saying: 'We've already solved some problems that you might not see.' Your job as a manager is to surface that knowledge. Luna: So the goal isn't to override the resistance, it's to explore it. That makes the employee feel heard, and you get better outcomes. Lucas: Precisely. Now, another tactic is to frame the change as a low-risk experiment. Tell them, 'Let's try it for two weeks, if it fails we'll know why, and we'll revert.' That reduces the fear of permanent loss. Luna: I like that. It's like a safety net. And for first-time managers especially, it's a great way to build trust. Lucas: Yeah, because nothing destroys credibility faster than pushing a change that backfires without acknowledging it. I've seen managers double down and lose their team's respect. Luna: What about the cost of not changing? Sometimes the employee needs to see the bigger picture—like if the company is losing market share because of outdated processes. Lucas: That's a leadership conversation. You have to connect the local change to the strategic context. If the team knows that the company's survival depends on being more agile, the 'we've always done it' argument loses weight. Luna: You mentioned the logistics manager earlier. Did she ultimately succeed with that employee? Lucas: She did. It took about three months. The employee ended up becoming the go-to person for training others on the new system. She said the key was patience and not making it personal. Luna: That's a great outcome. And it shows that even the most resistant employees can become champions if you respect their experience. Lucas: Absolutely. You know, it's amazing how much practical advice we cover on this podcast. And it's entirely listener-supported. Luna: Yeah, a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's what keeps this ad-free. If you've found these episodes helpful for your career, it's a way to give back. Lucas: And every contribution goes right into creating more content like this. We really appreciate it. Luna: So back to that logistics manager—she eventually got a pilot group to test the new system, and the resistant employee volunteered to help design the training. That's the kind of shift we're talking about. Lucas: Perfect example. To summarize: when you hear 'that's how we've always done it,' don't fight it. Explore it, use data, run small experiments, and involve the resistor. You might end up with a better change and a stronger team. Luna: And sometimes the best change is the one that the team helps build. Lucas, great discussion. Lucas: Thanks, Luna. And to our listeners—next time you hear that phrase, try curiosity, not frustration. See you next week.