Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says That's Not My Job
Transcript
- Lucas: You hear the phrase 'that's not my job' and you immediately feel that little spike of frustration — because you know it's technically true, but it's also a total conversation-ender. Luna: Right. It's the kind of statement that shuts down collaboration before it even starts. And it's surprisingly common — a 2024 Gallup survey found that about 40 percent of managers say they deal with this at least once a month. Lucas: Forty percent — that's huge. And the thing is, the phrase itself isn't always malicious. Sometimes it's about genuine confusion over role boundaries. Sometimes it's fear — 'if I do this, will it become my job forever?' And sometimes, frankly, it's a power move. Luna: Let's start with a concrete example. I was talking to a friend who manages a warehouse team at a mid-sized logistics firm. He had a coordinator — smart guy, great with numbers — but every time someone from sales asked him to pull a quick report on shipping delays, he'd say, 'That's the sales analyst's job.' Lucas: And technically he was right. But in a small team, rigid boundaries can cause real problems. In his case, the sales analyst was out sick for three days, the report didn't get pulled, and a major client's order was misrouted — cost the company about twelve thousand dollars in expedited shipping and penalties. Luna: Twelve grand because one person refused to step outside a dotted line. That's the kind of story that makes managers want to rewrite every job description with a giant 'and other duties as assigned' clause. Lucas: And look, if this episode helps you handle that situation even a little better — maybe it's worth the price of a coffee. Honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. Luna: Yeah, listener support is what keeps this show ad-free and focused on real management problems. No pressure, just if it's useful to you. Lucas: So back to that coordinator. His manager tried a few different approaches before landing on something that worked. And the key was understanding that 'that's not my job' often hides a deeper concern. Luna: What was the deeper concern in that case? Lucas: Turned out the coordinator had been burned before. In a previous role, he'd volunteered to help with a project, and it became his full-time responsibility without any change in title or pay. So his boundary was a protective mechanism. Luna: Ah, so the phrase wasn't laziness — it was a learned response to being taken advantage of. That changes the conversation entirely. Lucas: Exactly. And once his manager understood that, they could address the real issue: the lack of a clear process for role expansion. They set up what they called 'role expansion conversations' — quarterly check-ins where they'd discuss new tasks, adjust the job description if needed, and always tie it to compensation or development goals. Luna: So instead of the employee feeling like every 'yes' was a trap, they had a framework. That's smart. But what about the employee who uses the phrase as a blunt instrument — someone who's just not interested in helping out? Lucas: That's a different animal. With that type, you have to separate the behavior from the person. I recommend a three-step approach. First, acknowledge the boundary — 'You're right, that isn't in your current job description. I appreciate you pointing that out.' That disarms the defensiveness immediately. Luna: Because you're not arguing. You're validating their reading of the situation. Lucas: Right. Step two: connect it to the bigger picture. 'In this case, we have a client deadline that depends on this information, and I need your expertise to get it right. Could we treat this as a one-time request and then talk about whether it should be part of your role going forward?' Luna: That's key — you're not asking them to adopt a permanent new duty on the spot. You're framing it as a temporary collaboration. That lowers the stakes. Lucas: Exactly. And step three is the follow-through. If they help, you have to actually have that conversation afterward. 'We did that task — let's discuss whether it should be added to your responsibilities, and if so, what that means for your role.' Otherwise, you've just confirmed their fear that 'yes' means 'forever.' Luna: I think a lot of managers skip step three because they're busy. But that's exactly where trust gets built — or broken. Lucas: Totally. And I want to loop back to something you said earlier about job descriptions. A 2023 study from the Society for Human Resource Management found that 67 percent of employees say their job description is 'mostly accurate' but misses significant day-to-day tasks. So when a manager says 'that's not your job,' they may actually be reinforcing an outdated document. Luna: Interesting — so sometimes the phrase comes from the top down. A manager tells an employee to stay in their lane, and then the employee internalizes that and repeats it. Lucas: Exactly. So if you're hearing 'that's not my job' frequently, it's worth asking: did you or another leader ever imply that boundary? And is your current job description accurate for what the team actually needs? Luna: Let's talk about the opposite scenario too — where the employee is right to say no. I'm thinking of a junior designer I worked with once who kept getting pulled into administrative tasks because she was the only one who knew how to use a certain database. She finally said 'that's not my job,' and her manager was annoyed — but she was right. She was being underutilized. Lucas: That's a really important nuance. Not every 'that's not my job' is resistance. Sometimes it's the employee protecting their own ability to do the work they were actually hired for. As a manager, you have to distinguish between the person who's protecting their boundaries appropriately and the person who's using boundaries to avoid growth. Luna: How do you tell the difference? Lucas: I look at pattern. Is this the same person who also volunteers for stretch assignments? Who takes on new projects when they can? If yes, then their 'no' is probably a healthy boundary. If they never say yes to anything outside their core duties, then it's likely avoidance. Luna: That's a good heuristic. And I think the conversation also depends on the company culture. In startups, 'that's not my job' is almost taboo — everyone wears many hats. In larger organizations, roles are more defined and the phrase might be more legitimate. Lucas: Right. So you can't apply a one-size-fits-all approach. But I think the underlying principle is: when an employee says 'that's not my job,' treat it as a data point, not an insult. Ask yourself: why are they saying it? Is it fear, is it clarity, is it a power play, is it a legitimate concern? Luna: And then address the root cause, not the symptom. Which is good management advice in general. Lucas: Absolutely. So let's leave listeners with one actionable takeaway. Next time you hear 'that's not my job,' try the three-step approach: validate the boundary, connect it to the shared goal, and commit to a follow-up conversation. And if you're the one setting boundaries as an employee, make sure you're saying 'no' to protect your priorities, not to avoid contribution. Luna: And if you want to dig deeper into this, we've linked to a few resources on the show page — including a template for those role expansion conversations. That's at buy me a coffee dot com slash fexingo. Lucas: Luna, good conversation. See everyone next week.