Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Says That Is Not My Job
Transcript
- Lucas: So you've got a team member who, whenever you ask them to do something that's even slightly outside their listed responsibilities, says 'that's not my job' — maybe politely, maybe not. And you're not sure whether to push back or rewrite the job description. Luna: I think every manager has encountered this at some point. It's especially common in organisations where roles are very rigidly defined. Lucas: Right. And this is Episode 58 of Manager Mondays. I'm Lucas. Luna: And I'm Luna. Today we're going to talk about what you actually do when an employee consistently says 'that's not my job' — without turning it into a confrontation or a performance improvement plan right away. Lucas: Let me start with a specific case. I was talking to a marketing director at a midsize agency — about 200 people. She has a senior designer, let's call her Priya, who is excellent at her core work. Design, layout, brand guidelines — top notch. Luna: So the quality isn't the issue. Lucas: Exactly. But the director asked Priya to sit in on a client kickoff meeting to understand the brand voice better. Priya said 'that's not my job, I just design what the copywriter gives me.' Then she asked Priya to help a junior designer troubleshoot a file — same response. Luna: Oof. And I bet that created resentment on the team, because others were picking up those tasks. Lucas: Exactly. The director said other team members started complaining about Priya being inflexible. But here's the thing — Priya's job description actually did say 'collaborate with cross-functional teams' in the bullet points. Luna: So it's not really a job description problem. It's more about how Priya interprets her role. Lucas: That's the first insight. Often when someone says 'that's not my job,' they are actually signalling something else. They might feel overloaded and this is a way to protect their time. Or they might genuinely believe their role is narrowly defined. Or — and this is key — they might feel that saying yes to these tasks means they will be taken advantage of. Luna: So the manager's first step is diagnosis, not discipline. Lucas: Exactly. In Priya's case, the director had a one-on-one and asked open questions: 'When I ask you to join a client meeting, what concerns come up for you?' Priya said she worried it would add two hours to her week without any recognition, and that she wasn't sure what value she could add. Luna: That's such a different conversation than 'she's being difficult.' Lucas: Totally. Once the director understood the concern, she could address it. She explained that the client meeting would actually reduce revision cycles because Priya would hear the brief firsthand. And she committed to acknowledging Priya's cross-functional work in her performance review. Luna: So part of it is making the 'why' explicit. Many managers assume the employee sees the value, but they don't. Lucas: Right. And the other piece is boundaries. Some employees are right to protect their focus. If you're a deep work role — like a data scientist or a writer — constant context switching is costly. The trick is distinguishing between legitimate role protection and using 'that's not my job' as a shield against any discomfort. Luna: How do you tell the difference as a manager? Lucas: Look at the pattern. If the employee says no to everything — including small, five-minute requests — it's likely a shield. If they say no selectively, and they can articulate a thoughtful reason, it's probably role protection. And you can work with that. Luna: So what's the concrete step for a manager who's listening right now and has a Priya on their team? Lucas: Three steps. First, in your next one-on-one, ask specifically: 'When I ask you to do X, you often say it's not your job. Help me understand what you see as the core of your role and what feels outside it.' Listen without defending. Second, after you understand their perspective, clarify your expectations. Say something like: 'I see your core role as A, B, and C. But I also need you to occasionally do D and E because they support the team's goals. Let's agree on what's reasonable.' Luna: And the third step? Lucas: Third, create a feedback loop. After a few weeks, check in: 'How did it feel when you joined that client meeting? Did it create the problems you worried about?' This reinforces that you respect their concerns and you're adjusting together. If they still refuse after that, then you have a performance conversation. Luna: That makes sense. It's not about winning an argument, it's about realigning expectations. Lucas: Exactly. And one more thing — sometimes the employee is right. Sometimes the task genuinely is outside their role and should go to someone else. A good manager is open to that possibility. The phrase 'that's not my job' can be a signal that the organisation has a gap. Luna: That's a generous way to look at it. But it does require the employee to be thoughtful, not just reflexive. Lucas: Right. And that's where coaching comes in. You can train someone to say 'I'm happy to help with that, but can we talk about how it fits into my priorities?' That's a much more constructive version of the same boundary. Luna: I want to circle back to something you said earlier about recognition. You mentioned that Priya was worried about not being acknowledged. That feels like a big part of the equation. Lucas: Huge. If the organisation only rewards people for their narrow metrics, then why would anyone go beyond? The manager has to make the invisible work visible — in reviews, in team meetings, in compensation discussions. Luna: So part of the solution is systemic. It's not just about the individual employee. Lucas: Exactly. And that's a good note to take a quick breather on, because we've been talking about managing others, and it reminds me of why we do this show without any ads. We believe these conversations are useful enough that they should be accessible to anyone, without interruption. Luna: Absolutely. And the way that works is listener support. If you've gotten value from an episode like this — maybe it helped you handle a tough conversation — you can support us at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. Lucas: It's a small way to keep this ad-free and focused on practical help. No pressure, but if it's made a difference in your work, we appreciate it. Luna: Okay, back to Priya. So after the manager had that open conversation and adjusted the recognition, did Priya's behaviour change? Lucas: It did, gradually. She started attending client meetings — and she actually gave valuable design input that saved two rounds of revisions. The director made sure to call that out in a team email. Within a month, Priya was volunteering for cross-functional projects. Luna: That's a great outcome. But I imagine not every story ends that way. Lucas: No. If you've done the three steps — listen, clarify, check in — and the person still refuses to do reasonable cross-functional work, then you have a performance issue. At that point, it's about accountability. You set a clear expectation: 'I need you to do X by Friday. If you can't, let's talk about why.' And if they still refuse, you escalate. Luna: And sometimes the right outcome is that the person leaves — either to a more narrowly defined role elsewhere, or because the organisation isn't a fit. Lucas: Exactly. But most of the time, the 'that's not my job' response is fixable with better communication and better systems. The manager just has to be willing to dig into the 'why' first. Luna: So to wrap up, here's a quick recap: diagnose the reason behind the resistance, clarify expectations with specific examples, and create a feedback loop that rewards flexibility. Lucas: And remember, sometimes the employee has a point. Listen for that too. I'm Lucas. Luna: And I'm Luna. Thanks for being here.