Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage the Employee Who Always Says That Is Not My Job
Transcript
- Lucas: So we've spent a lot of episodes on employees who say 'I can't' or 'I'm not ready' or 'I need more time.' But there's a version that's even more direct, and it's the one that makes a manager's blood pressure spike. Luna: Let me guess. 'That's not my job.' Lucas: Exactly. And it's fascinating because unlike the other phrases, this one isn't about capability or confidence. It's about territory. The employee is essentially drawing a line in the sand and saying 'this belongs to someone else.' Luna: I've definitely had that moment. What do you do when someone says that to you? Lucas: Well, the first thing I do is take a breath, because my instinct is to say something like 'it's all our job' or 'we're a team.' But that's not helpful. It's actually dismissive. The real move is to get curious about why they're drawing that line. Luna: So you think there's often a legitimate reason behind it? Lucas: Sometimes. Let's take a concrete example. I had a friend who managed a customer support team, and one of his agents refused to document a bug that kept showing up in the product. The agent said 'I'm not a QA engineer, that's not my job.' And sure, technically it wasn't in the job description. But the impact was that the same bug kept getting reported, and the product team never knew, so it kept happening. Luna: So what did your friend do? Lucas: He didn't push back right away. He asked the agent to walk him through why she felt it wasn't her job. And it turned out that she had been burned before—she'd documented a bug once, and then it became her job, and her actual support tickets piled up. So she'd learned that saying 'not my job' was the only way to protect her core responsibilities. Luna: That makes sense, actually. It's a defensive move that comes from a real place. Lucas: Right. And that's the key insight: 'that's not my job' is rarely about laziness. It's usually about fear of overload, or unclear expectations, or a previous experience where being flexible got punished. If you treat it as a character flaw, you'll miss the actual problem. Luna: So what's the first step for a manager in that moment? Lucas: I'd say the first step is to check your own assumption. Are you asking this person to do something that genuinely falls outside their role? And is it a one-time request or a recurring expectation? That matters a lot. Luna: Because if it's a recurring thing, you're essentially changing their job description without telling them. Lucas: Exactly. And nobody likes that. So before you label them as difficult, ask yourself: have I clearly communicated what's part of the role and what's just a helping hand? If you haven't, the employee is actually making a fair point. Luna: So then how do you have the conversation? Let's say you've decided it really is part of the job. Lucas: You reframe it. Instead of talking about duties, talk about outcomes. For the support agent, the goal is to reduce customer friction. Documenting a bug reduces future friction. So you're not asking them to do QA work—you're asking them to help solve the problem they're already seeing. Luna: That's a nice shift. From 'task' to 'purpose.' Lucas: And it's more than a language trick. It changes what you're asking for and why. But I also want to be careful here—there are some 'not my job' moments where the employee is actually right. Sometimes it's a boundary that should be respected, especially if the request is outside their expertise or would genuinely overburden them. Luna: So how do you know the difference between a boundary that's healthy and one that's just rigid? Lucas: Look at the pattern. If an employee is generally flexible and occasionally says 'I can't take this on right now because I'm at capacity,' that's a healthy boundary. But if every request, no matter how small, is met with 'that's not my job,' that's a pattern of territoriality that you need to address. Luna: And how do you address the pattern without getting defensive yourself? Lucas: You set a clear expectation around team citizenship. That means having a frank conversation that goes something like: 'I hear that you see this as outside your role. I'd like us to think about the broader goal we share. Sometimes that means taking on tasks that aren't in your job description.' And then you have to be specific about what you're asking for. Luna: But what if the employee still refuses? Lucas: Then you need to explore whether this is a willingness problem or a capacity problem. If it's willingness, you might need to make it clear that flexibility is a core part of the role going forward, and that could be reflected in performance reviews. If it's capacity, then you need to look at their workload and see if something can be reprioritized. Luna: Have you ever seen a situation where the employee was right and the manager was wrong? Lucas: Yeah, I've seen managers dump tasks on people who were already stretched thin, and then get frustrated when they pushed back. In one case, a manager asked a data analyst to take over some reporting that was clearly the responsibility of a different team. The analyst said it wasn't her job, and she was right. The manager just didn't want to deal with the other team. Luna: That's a good reminder that the phrase can be a signal to the manager, not just a problem with the employee. Lucas: Absolutely. Sometimes 'that's not my job' is the most honest feedback you'll get about your own process. So listen to it before you react. Luna: I also think about the team dynamic. If one person is the 'not my job' person, it can breed resentment among others who are more flexible. Lucas: That's a really good point. And that's why you can't just let it slide. If you let one person refuse, other people will notice and might start drawing their own boundaries. The next thing you know, everyone is saying 'that's not my job.' Luna: So it's not just about the individual—it's about modeling the behavior you want across the team. Lucas: Exactly. And there's a great way to do that: you can model flexibility yourself as a manager. When you step in to help with something that isn't technically yours, you signal that the goal matters more than the title. But you also need to be careful not to enable a culture where everything falls on you. Luna: Right. It's a balance. Lucas: So let's say you've had the conversation, you've reframed the ask, and the employee starts to come around. How do you reinforce that behavior without making it feel like a big deal? Luna: I'd say acknowledge it. Something like 'I really appreciated you jumping in on that documentation, even though it wasn't in your wheelhouse.' Positive reinforcement goes a long way. Lucas: That's a good one. And you can also be transparent about why you're asking them to do something new. If you explain that you're trying to build their skills or that it's a growth opportunity, it changes the framing from 'extra work' to 'development.' Luna: But what about the employee who still hasn't budged after several conversations? Lucas: At that point, you need to be more direct. You can say something like 'this is a core part of our team's success, and I need your help to make it happen.' If they still refuse, then you have a performance issue, and you need to treat it like one—with clear consequences if behavior doesn't change. Luna: So in a way, 'that's not my job' can be a gateway to a deeper conversation about role, purpose, and accountability. Lucas: It really can. And when you handle it well, you often find that the employee wasn't trying to be difficult—they just needed a clearer picture of how their work connects to the bigger mission. And honestly, that's a conversation worth having with everyone on your team, not just the ones who say the phrase. Luna: That's a great note to end on. But before we do, I know we've been talking about how important it is to have these conversations, and that reminds me—if you've been getting something out of these episodes, and maybe you've even had a version of this conversation at work, it's a small thing that keeps the show going. You can support us over at buy me a coffee dot com slash fexingo. Lucas: Yeah, a couple of dollars a month genuinely makes a difference. It keeps the podcast ad-free and lets us keep digging into these real management scenarios. No pressure at all, but if it's helped you, it's a nice way to say thanks. Luna: Alright, so back to the topic. One thing I want to add—having handled a 'not my job' moment myself, I've found that asking the employee to suggest an alternative solution can turn the conversation cooperative. Like, 'if you can't do this, who do you think should?' Lucas: That's a great tactic. It forces them to think about the problem as a shared one. And sometimes they'll come up with a better idea than you would have. Luna: So the takeaway is: don't fight the phrase, understand it. Lucas: And ask yourself if you've been clear about what the job actually is. Because sometimes the employee is just telling you the truth—and the best thing you can do is thank them.