Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Says It's Not My Job
Transcript
- Lucas: Luna, let me ask you something. You've delegated a task to a team member — reasonable request, within their general domain — and they look at you and say, 'That's not in my job description.' What goes through your head? Luna: Honestly? A mix of frustration and curiosity. Frustration because it feels like a roadblock. Curiosity because I wonder what's really behind it. Lucas: Right. And I think that's the right instinct — to get curious. Because on the surface, it sounds like a boundary issue. But often, it's something else entirely. Luna: Like what? Lucas: Fear, for one. Fear of failure. If I stick strictly to my job description, I can't be blamed for falling short on something outside it. Or maybe it's a trust issue — they don't believe you'll have their back if the task goes wrong. Luna: So it's not always about being lazy or difficult. Sometimes it's self-protection. Lucas: Exactly. And that reframes the whole conversation. Instead of getting into a power struggle over 'yes it is your job,' you can address the underlying concern. Luna: Okay, but let's be real — sometimes it is just someone who's disengaged or has a very narrow view of their role. How do you tell the difference? Lucas: Great question. I look at pattern. Is this a one-off reaction to a specific request that feels unfair? Or is it a recurring theme where they resist anything that isn't spelled out in writing? Luna: And if it's the second pattern, what's your move? Lucas: I'd start with a one-on-one conversation that's not about the task itself. I'd say something like, 'I've noticed you tend to stick closely to your job description. Help me understand what's driving that.' Then listen. Luna: That's a non-accusatory opener. What do you typically hear back? Lucas: Sometimes they say they don't want to overstep into someone else's turf. Or they've had a bad experience in the past where taking on extra work led to burnout. Or frankly, they feel undervalued and see the job description as the only thing they're being paid for. Luna: All valid concerns. So the manager's job is to address those, not to argue about the wording of the job description. Lucas: Right. And then you can pivot to a more constructive frame. Instead of 'this is your job,' you say, 'this is how this task connects to our team's goals and your growth.' Luna: I've used that approach. I remember one team member who kept saying 'that's not my job' about data entry tasks. Turned out she thought data entry was beneath her skill level. She wanted more analytical work. Lucas: And did you give her that? Luna: Eventually, yes. I swapped the data entry for a reporting task that played to her strengths. She stopped pushing back, and her engagement went up. Lucas: That's a perfect example. You addressed the unspoken need. But let's talk about the scenario where the task genuinely is outside their scope, and they're right to push back. Luna: Yeah, because managers can make unreasonable requests too. Lucas: Absolutely. If someone says 'that's not my job' and they're correct, you need to respect that. But you can still explore if they'd be interested in learning that skill, or if there's a way to rotate responsibilities so the workload is fair. Luna: So it's not about forcing the issue. It's about negotiating and being transparent about why you're asking. Lucas: Exactly. And if you consistently get pushback, even after addressing concerns, you might have a values mismatch. Some people genuinely prefer a very defined role, and that's okay. But in a fast-moving team, you need flexibility. Luna: That's when you have to decide: is this person in the right seat? Or do you need to have a more serious conversation about fit? Lucas: Yeah. And I think a lot of managers avoid that conversation because they don't want to seem confrontational. But if you've tried the coaching approach and it's not working, it's actually kinder to be honest. Luna: Let's talk about a specific technique I've used: the 'roles and responsibilities chart'. I'll literally draw up a one-page document with columns for each team member, listing their core duties, but also a row for 'stretch projects' and 'collaborative tasks'. It makes the grey areas visible. Lucas: I like that. It takes the ambiguity out. People often say 'that's not my job' because they genuinely don't know whose job it is. A chart like that can prevent the objection before it comes up. Luna: And if someone still pushes back after seeing the chart, you have a clear artifact to reference. It's less personal. Lucas: One more thing: sometimes the issue is that the employee feels the job description is a contract. They think, 'If I do X, I'm owed Y.' So they're protective. If you can link the extra tasks to something they value — a promotion path, a skill they want to build — the resistance often melts. Luna: That's the 'what's in it for me' question. You have to answer it before they ask it. Lucas: Right. And if you can't answer it honestly — if the task is just a grind with no upside — then you need to ask yourself if you're being a good manager by piling it on. Luna: Speaking of being a good manager, if today's episode gave you a useful perspective or a script you can actually use on Monday, that's exactly why we do this. And the way we keep the show ad-free and focused on real, practical advice is through listener support at buy me a coffee dot com slash fexingo. Lucas: Yeah, that's right. It's a small way to say 'this helped me' — and it genuinely lets us keep making episodes without sponsors or interruptions. So if you found value, consider it. Otherwise, let's get back to the conversation. Luna: So we've covered the why behind 'that's not my job' and some coaching approaches. But I want to circle back to something you mentioned earlier — the fear factor. Can you elaborate on that? Lucas: Sure. I've seen employees who are terrified of failing in front of their manager. They'd rather say 'that's not my job' than risk doing something they're not confident in. In those cases, you need to build psychological safety. Explicitly say, 'I'm not expecting perfection. I'd rather you try and learn than stick to the script.' Luna: And that permission often unlocks them. I've had people who were rigid about their roles become incredibly flexible once they trusted that mistakes wouldn't be punished. Lucas: Exactly. So to summarize: when you hear 'that's not my job', don't just hear a boundary. Hear a signal. It could be fear, lack of trust, unclear expectations, or a genuine mismatch. Your job as a manager is to diagnose and address the root cause. Luna: And if you can turn that resistance into willingness, you've not only solved the immediate problem — you've built a stronger relationship. That's the real win. Lucas: Agreed. Thanks for the conversation, Luna. And to our listeners — go try one of these approaches this week. See what happens.