Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage an Employee Who Always Says Not My Problem
Transcript
- Lucas: So let me paint a scene. You assign a task that touches two teams — your team and another department. And the person on your team says, 'That's not my problem.' Maybe they say it politely. Maybe they shrug. But the message is clear: they see a boundary and they won't cross it. Luna: Right. And the frustrating part is that it often comes from someone who is otherwise competent. They're not slacking — they just have a very narrow view of what they're responsible for. Lucas: Exactly. And that's what makes it tricky. If it were a performance issue, you'd have a performance conversation. But this is more of a mindset thing — a boundary that the employee has drawn, and you as the manager need to either respect it or redraw it. Luna: Where does that boundary come from? Is it usually about protecting their time, or is it more about fear of failure? Lucas: It can be either. But in my experience, a lot of it comes from previous organizations where people got burned for stepping outside their box. Imagine working at a place where every time you helped someone else, your own deadlines slipped and you got blamed. You learn to say 'not my problem' as a defense mechanism. Luna: So it's a learned behavior. That means it can be unlearned. Lucas: That's the hope. But you have to address it deliberately. I want to walk through a specific case from a logistics company — mid-sized, about 400 employees. They had a warehouse supervisor, let's call him Mark, who was great at running his shift. But anytime a data-entry error from his team caused a misroute, he would say, 'That's the data team's problem — I just move boxes.' Luna: And that cost them. Lucas: Forty-seven thousand dollars in one quarter. The CFO tracked it: misrouted shipments that had to be expedited or replaced. And Mark's manager had been letting it slide because Mark hit his own metrics. But the company was bleeding money from these handoffs. Luna: So what did the manager do? Lucas: She used a three-step approach that I think works well for this pattern. Step one: label the pattern. Not in an accusatory way — more like, 'Hey Mark, I've noticed that when a mistake involves data entry, you tend to say it's not your team's problem. Is that how you see it?' Luna: Just naming it, without judgment. Lucas: Yeah. And Mark said, 'Well, the data entry is done by a different department.' So step two: reframe the ask. The manager said, 'I'm not asking you to fix the data entry. I'm asking you to own the outcome — the shipment going to the right place. That's your shift's responsibility. So if you see an error, you flag it. You don't let it go.' Luna: That shifts it from blaming to problem-solving. Lucas: Right. And step three: set a boundary. She said, 'Starting this week, if a misroute happens and your team didn't catch it, I'll need to document it as a performance issue. Not because you caused it, but because you let it leave your dock.' Luna: That's firm. Did it work? Lucas: It did. Within two weeks, Mark's team started double-checking the data. They caught six errors that would have cost the company about twelve thousand dollars. And Mark stopped saying 'not my problem.' He started saying, 'Let me look into it.' Luna: So the key was expanding his definition of ownership without piling on unrelated work. Lucas: Exactly. And that's the nuance. You're not asking them to do someone else's job. You're asking them to be accountable for the handoff. That's a different ask. Luna: What about the employee who says 'not my problem' about something that genuinely isn't their job? Like, they're in accounting and someone asks them to move furniture. Lucas: That's a valid boundary. And a good manager should respect clear job scope. The issue is when 'not my problem' becomes a reflex for anything beyond a tightly defined task list. That reflex breaks down collaboration. Luna: So how do you tell the difference between a legitimate scope issue and a defensive reflex? Lucas: Look at the pattern. If the employee says 'not my problem' about tasks that clearly fall under their team's outcomes — like the data-checking for Mark — then it's a reflex. If it's about something truly outside their function, then it's about role clarity. You can have a conversation about that too. Luna: And what about the culture piece? If the whole company has a 'not my problem' vibe, one manager can only do so much. Lucas: That's a bigger challenge. But you can still create a pocket of ownership on your own team. I've seen managers do it by modeling the behavior themselves — saying 'let me find out who can help' instead of passing the buck. And by rewarding people who step up across boundaries. Luna: You know, this reminds me of something I read about Patagonia. They have a culture where everyone is expected to care about the product, regardless of their job title. A finance person might flag a quality issue they noticed in a catalog photo. And no one says 'not my problem'. Lucas: That's a great example. And it's not accidental — it's built into the hiring and onboarding. They look for people who are naturally curious beyond their silo. Luna: But what about the manager who's dealing with this on a tight timeline? They can't overhaul the culture. They need a fix by next week. Lucas: Then I'd say: pick one repeated handoff point. Maybe it's the weekly report that goes to another department, or the handoff from sales to fulfillment. Sit down with the employee and say, 'This is where we've had issues. I need you to own this specific thing from start to finish.' Make it concrete and limited. Luna: And give them feedback when they do it well. Lucas: Absolutely. Positive reinforcement is huge. If someone catches an error at the handoff, acknowledge it publicly. Say, 'Hey, Sarah saved us from sending a wrong order to a client by double-checking.' That sends a signal that ownership is valued. Luna: It also makes the behavior visible to others who might be watching. Lucas: And that's how you start shifting the norm. Look, we talk about a lot of management challenges on this show — and we're able to do it ad-free because a small group of listeners chips in through buy me a coffee dot com slash fexingo. If you've gotten something useful out of these episodes, that's a simple way to keep it going. Luna: Yeah, it really makes a difference. And we appreciate every bit of support. Lucas: Alright, back to the topic. So after you've set that clear ownership, the next thing is to follow through on the boundary. If the employee still says 'not my problem' about that specific handoff, you need a consequence. Luna: What does that look like in practice? Lucas: It could be a documented coaching session, or a note in their performance review. But it should be consistent. If you let it slide sometimes, the behavior won't change. Luna: And what about the employee who is defensive because they're overwhelmed? Sometimes 'not my problem' is a way of saying 'I can't take on anything else.' Lucas: That's a very different root cause. In that case, you need to have a workload conversation first. Ask, 'What's on your plate? Let's prioritize together.' If they're genuinely overloaded, then saying no is appropriate — but they should say 'I can't take that on because I have X, Y, Z' rather than 'not my problem.' Luna: So you're teaching them a better way to communicate boundaries. Lucas: Exactly. The phrase 'not my problem' is almost never productive. Even if it's true, it sounds dismissive. You want to coach them to say 'I can't own that because of these reasons' or 'Let me connect you with the person who can.' Luna: It's a communication skill, not just an accountability issue. Lucas: Right. And as a manager, you can model that too. When you get a request you can't fulfill, say 'I can't do that, but here's what I can do' or 'Let me find the right person.' That shows a different way to say no. Luna: I think the bottom line is that 'not my problem' is often a symptom of a lack of shared goals. If people see how their work connects to the bigger picture, they're less likely to draw hard lines. Lucas: That's a good way to frame it. So for any manager listening: if you hear those three words, don't just get frustrated. Ask yourself — is this a boundary issue, a capacity issue, or a culture issue? And then address it accordingly. Luna: And maybe start with one handoff point, like Lucas said. Lucas: Exactly. Small changes compound. Thanks for being here, and we'll talk next week.