Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Blames Others for Mistakes
Transcript
- Lucas: So we've talked about quiet quitters, about people who say they're too busy, about the ones who always volunteer for more work. But there's a type that I think is actually harder to fix than any of those — the team member who, when something goes wrong, immediately points the finger at someone else. Luna: Oh, the blamer. Yeah, I've managed one of those. It's exhausting because every error becomes a rabbit hole of 'well, Sarah didn't send me the file until Tuesday' or 'the data team gave me the wrong numbers.' Lucas: Exactly. And the real problem isn't just the behavior itself — it's that it poisons the team. When one person consistently deflects, others start covering their own tracks instead of focusing on quality. Trust erodes pretty fast. Luna: So what's the play? Do you call it out in the moment? Or do you schedule a formal conversation? Lucas: Both, but the formal conversation is where the real work happens. I want to walk through a case from about two years ago. I was advising a VP of analytics at a mid-sized SaaS company — about 400 employees. She had a senior analyst, let's call her Priya, who was brilliant with numbers but had a pattern: whenever a deliverable was late or contained an error, Priya would immediately blame the data engineering team, or the product team, or the sales ops team. Luna: Classic. And was it ever actually the other team's fault? Lucas: Sometimes. But the VP noticed that the blame was always external, never self-reflective. So she asked me to help craft a conversation. We built it around a simple framework: three questions that turn blame into ownership. Luna: I'm listening. What are the three questions? Lucas: First: 'What part of this was within your control?' Second: 'What could you have done differently, even if it was someone else's fault?' And third: 'What will you do next time to prevent this from happening again?' The VP picked a recent incident — Priya had delivered a quarterly report two days late and blamed the data engineering team for not giving her the raw data on time. Luna: And the data engineering team probably had their own version of events. Lucas: Right. So the VP sat Priya down and said, 'I understand the data team was late. But let's focus on what you could have done. Did you check in with them earlier? Did you build a buffer into your timeline? Did you escalate proactively when you saw the delay coming?' And the answer was no to all three. Luna: Ouch. But that's a tough conversation to have without making someone defensive. Lucas: It is. The key is the framing. The VP started with, 'I'm asking these questions because I want you to succeed, and I think you can be even more effective if you focus on what you can control.' That's not accusatory. It's coaching. Luna: Did Priya take it well? Lucas: Initially, she was defensive. She said, 'But it really was their fault.' The VP didn't argue. She said, 'Maybe it was. But even if it was, the question is: what can you do next time to own your part of the deliverable?' And she left it at that. Then they set a follow-up in two weeks. Luna: And what happened in the follow-up? Lucas: Priya had a small but real shift. She came in and said, 'I started flagging dependencies in our weekly stand-up, and I gave the data team a deadline that's two days before my internal deadline.' That was the beginning. Over the next six weeks, the VP tracked a 40 percent reduction in cross-team complaints involving Priya. And her error rate actually dropped too, because she was paying more attention to inputs. Luna: That's a great outcome. But I have to ask — does this work for everyone? I've had people who are so entrenched in a blame mindset that no amount of coaching seems to break through. Lucas: It doesn't work for everyone. The framework is a diagnostic tool as much as a coaching tool. If after three or four conversations the person still won't take any ownership, you're probably dealing with something deeper — maybe a genuine lack of self-awareness, or in some cases, a personality trait like narcissism. In those cases, you have to escalate to performance management. Luna: Right. And I think it's important to distinguish between someone who blames because they're anxious and someone who blames because they truly believe they're never wrong. Lucas: Exactly. The anxious blamer can usually be coached. The person who believes they're infallible — that's a much harder problem. For them, you might need to bring in concrete data from multiple incidents, show a pattern, and set a clear expectation: 'In this team, we own our mistakes, and we work on solutions. If you can't do that, this isn't the right fit.' Luna: And you have to be willing to follow through on that. Because if you let it slide, the rest of the team sees that blame is tolerated. Lucas: That's the real cost. One blamer can drag down an entire team's culture. I've seen high performers leave because they got tired of being blamed for things that weren't their fault. Luna: You know, speaking of the team and the culture we're trying to build here at this show — we've been doing Manager Mondays for over a year now, and we deliberately keep it ad-free. No sponsors, no commercial breaks. That's a choice we made from day one. Lucas: Yeah, we wanted this to be a resource that's purely about helping managers get better, not about selling you something. And if you've found episodes like this one useful — maybe you used one of these frameworks with your own team — the only way we keep this going without ads is through listener support. Luna: Right. So if you want to help, the link is simple. It's buy me a coffee dot com slash fexingo. No pressure, just an option if the show has made a difference for you. Lucas: Exactly. And now back to the blame conversation — because there's one more element I think is really important. The team-wide dynamic. Even if you successfully coach the individual blamer, you also need to rebuild trust with the rest of the team. Luna: How do you do that without embarrassing the person you're coaching? Lucas: You don't name names. But you set a team norm. In a team meeting, you can say, 'I've noticed that when things go wrong, our first instinct is often to figure out whose fault it is. I want us to shift to a different approach: when something goes wrong, let's start with what we can learn and what we can fix.' That signals a change without singling anyone out. Luna: And it gives the blamer a face-saving way to change behavior too. Lucas: Exactly. You're changing the culture, not just the person. And if Priya sees that the whole team is now expected to focus on solutions, she can adopt the new norm without feeling like she's being called out. Luna: I've also found it helpful to model the behavior myself as a manager. When I make a mistake, I say, 'I dropped the ball on this. Here's what I should have done differently.' That gives permission for everyone else to do the same. Lucas: That's huge. Psychological safety starts at the top. If the manager never admits fault, why would anyone else? Luna: So to recap the framework: three questions — what was in your control, what could you have done differently, what will you do next time. Plus a team-wide norm shift. And a willingness to escalate if coaching doesn't take. Lucas: That's the playbook. And I would add one more thing: don't wait too long. Every incident of blame that goes unaddressed makes the next one harder to correct. The earlier you have that first conversation, the better. Luna: Good advice. And a good place to leave it for this week. Next time, I think we should talk about managing someone who is actually better at your job than you are. Lucas: Oh, that's a great one. Securely managing talent that could replace you. I've got some thoughts on that. See you next Monday.