Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage the Employee Who Always Says Thats Not My Job
Transcript
- Lucas: So there's a phrase that, if you've been managing people for more than about six weeks, you have probably heard: 'That's not my job.' Luna: It lands like a door slamming shut, doesn't it? Lucas: Exactly. And what's interesting is how often we — as first-time managers especially — react to it emotionally. We feel disrespected, or we worry the team's going to fragment into silos. But the phrase itself is almost never the real problem. It's a symptom. Luna: A symptom of what, typically? Lucas: In my experience, three things. Fear of failure, a too-narrow job description, or — less commonly — a genuine workload issue. But let me give you a concrete case. I worked with a logistics company last year — about 200 employees, regional distribution. The warehouse lead, let's call him Marcus, kept saying 'that's not my job' whenever the operations manager asked him to help with inventory reconciliation. It wasn't in his official duties, but the whole team was expected to pitch in during quarter-end. Luna: And he was the only one refusing? Lucas: He was the loudest. The operations manager tried everything — explaining the business need, pointing out that others were helping, even threatening a performance note. Nothing stuck. Marcus would just say, 'I was hired to run the floor, not to count boxes.' And technically, he wasn't wrong. His job description listed 'warehouse floor supervision' and nothing else. Luna: So the manager was asking him to do something outside his formal scope, and Marcus used that as a shield. Lucas: Exactly. And that's the first trap managers fall into — arguing about what's in or out of the job description. You can't win that argument because it's written down. Instead, you have to reframe the conversation around role versus responsibilities. A role is the container; responsibilities are the stuff you actually do. And responsibilities evolve. Luna: So how do you get someone like Marcus to accept that evolution? Lucas: You start with curiosity. In a 1:1, you say something like: 'I noticed when I asked about the inventory reconciliation, your reaction was that it wasn't your job. Help me understand what concerns that raises for you.' Nine times out of ten, they'll tell you something real. In Marcus's case, he was afraid that if he did inventory work, he'd fall behind on his floor duties and look bad. He didn't trust that the manager would adjust expectations elsewhere. Luna: So it was a trust issue wrapped in a scope issue. Lucas: Exactly. And once you know that, you can negotiate. The manager said, 'Okay, what if we shift your floor check-ins to every two hours instead of hourly on the days you're doing inventory? And you only do reconciliation for two hours, three days a week, through the end of the quarter.' Marcus agreed to try it. He ended up being fine. Luna: So the script is: name the behavior, ask about the concern, then offer a concrete adjustment. Lucas: Right. But there's a second layer. Sometimes the employee is right — the task really doesn't belong to them. And a good manager has to be honest about that. If you're asking a junior analyst to do executive-level presentation prep, that's not a growth opportunity, that's dumping. The employee saying 'that's not my job' might be protecting their own career trajectory. Luna: That's a harder conversation because now you have to look in the mirror as a manager. Lucas: It is. And that's why the first step is always self-check. Ask yourself: Is this task core to their growth? Does it teach them something they need? Or am I just trying to get it off my plate? If it's the latter, don't be surprised when they resist. Luna: Let's talk about the team dynamic for a second. When one person says 'that's not my job' and everyone else is pitching in, doesn't that breed resentment? Lucas: Hugely. And it's actually the most common reason managers escalate the issue. They're not upset about the task; they're upset about the unfairness. But publicly calling someone out in a team meeting usually backfires. It makes the employee defensive and the team uncomfortable. Luna: So you handle it privately, but you also have to address the equity gap publicly somehow. Lucas: You do. One approach I've seen work: in a team meeting, the manager says, 'I want to thank everyone who helped with the inventory push last week. I know some of you took on tasks outside your usual scope, and that flexibility is what makes this team strong. I also want to clarify that going forward, inventory reconciliation will be part of everyone's quarterly objectives — including warehouse leads. I'll be updating role summaries to reflect that.' No naming names. Just resetting the expectation for everyone. Luna: That's smart because it makes the expectation explicit and removes the ambiguity that allowed the pushback in the first place. Lucas: Exactly. And if Marcus still says 'that's not my job' after the role summary is updated? Then it becomes a performance issue, not a scope issue. You can say, 'The role now includes this. Let's talk about what support you need to integrate it.' And if he still refuses, you have a much clearer path to progressive discipline. Luna: But ideally you never get there if you handle the first conversation well. Lucas: Right. And that's the thing — most employees who say 'that's not my job' are not trying to be difficult. They're trying to protect themselves from something: overload, failure, or irrelevance. Your job as a manager is to figure out which one, and then address the root cause, not the symptom. Luna: Speaking of protecting the show's ability to keep having these conversations — you know, we deliberately don't run ads on Manager Mondays. No sponsors, no pre-rolls, none of that. If you've found a specific tactic from an episode useful in your own team, and you want to support that choice, the link is buy me a coffee dot com slash fexingo. Lucas: Yeah, it's a small thing that adds up. Helps us keep the episodes focused on real cases instead of selling something. Appreciate anyone who chips in. Luna: Alright, back to the warehouse floor. So you mentioned three root causes — fear, scope, and workload. We covered fear and scope. What about workload? When should a manager accept the 'not my job' as legitimate? Lucas: When the employee is genuinely at capacity. If someone is already working fifty hours a week and you're asking them to take on a new task, 'that's not my job' might be a poorly worded way of saying 'I can't fit another thing.' In that case, the conversation shifts to priorities. You ask: 'What's on your plate right now? Let's look at your current tasks and see what can be deprioritized or reassigned so you can take this on.' Luna: So you're not asking them to do more; you're asking them to do different. Lucas: Exactly. And sometimes the answer is that nothing can be deprioritized, and then you have to either hire or absorb the task yourself. That's uncomfortable but honest. The worst thing you can do is insist they take it on and then blame them when something else drops. Luna: So let's land this with a concrete three-step script. What's the go-to move when you hear 'that's not my job'? Lucas: Step one: self-check. Is this task appropriate for their role and development? Step two: in a private conversation, get curious. 'Help me understand your concern.' Step three: negotiate the specifics — timing, support, scope adjustment. If they still refuse after that, update the role description and make it explicit. If they still refuse, it's a performance conversation. Luna: And the biggest mistake managers make? Lucas: Getting into a debate about the job description in the moment. You can't win. Instead, acknowledge the technical correctness and then move to the real conversation about expectations and support. That's where the actual work happens. Luna: Yeah, I think that's the takeaway. The phrase 'that's not my job' is almost never about the job. It's about something deeper. Lucas: And once you treat it as a signal rather than an insult, you can actually solve the problem.