Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Teammate Who Always Says That Is Not My Job
Transcript
- Lucas: You've assigned a task. It's clearly within the person's general area. And they look up from their screen and say — I'm quoting — 'that's not my job.' Luna: Oh, that line. It's like the official anthem of people who want to stay in their lane. I've heard it mostly from folks who've been at a company long enough to have carved out a very narrow territory. Lucas: Exactly. And for a new manager, it's one of the most disorienting responses you can get because it challenges your authority indirectly. They're not saying they can't do it. They're saying you're wrong to ask. So let's talk about what's actually going on when you hear 'that's not my job' and how you respond without escalating. Luna: Is the first move usually to check the job description? Because I feel like sometimes the employee is technically right. Lucas: That's exactly where I want to start. About eighteen months ago, I worked with a team at a SaaS company where a mid-level engineer named Derek kept pushing back on data migration tasks. He'd say 'that's the data team's job.' And you know what? His official job description said 'backend API development.' No mention of data migration. So technically, he had a point. But the company needed him to help. Luna: So the issue wasn't Derek being difficult. It was a job description that hadn't been updated in three years. Lucas: Right. And that's a pattern I see a lot. Gallup's most recent State of the Global Workplace report — released in June 2025 — found that only about 30 percent of employees strongly agree that their role expectations are clear. And among those who don't have clarity, turnover risk is nearly double. So if you're hearing 'that's not my job,' your first question should be: 'Is this person's job description accurate and current?' Luna: But what if the job description is fine and the person is still deflecting? Then it's a mindset issue, right? Lucas: Then we shift to the 'responsibility ladder.' It's a framework I picked up from a former boss. You draw a simple ladder with four rungs. Bottom rung: 'I need explicit instructions and will do exactly what I'm told.' Second rung: 'I'll do the task but I need guidance.' Third: 'I can handle this independently.' Top rung: 'I own this area and will proactively improve it.' Luna: I like that. So when someone says 'that's not my job,' they're essentially saying they believe the task is below their rung or on a different ladder entirely. Lucas: Exactly. So your job as manager is to have a conversation about which rung you expect them to be on for this particular task. And you need to be specific. Not 'I need you to be more of a team player.' Say: 'For this data migration project, I need you at rung three — handle it independently and come to me if there's a blocker.' Luna: That's much harder to argue with than a vague 'please step up.' Lucas: And it also reveals if the real problem is skill or will. If Derek says 'I don't know how to do data migration,' that's a skill gap we can train. If he says 'I don't think that should be my job,' then we're negotiating scope. Both are manageable, but you need different tools. Luna: Let's talk about the scope negotiation. Because I've seen managers cave and just reassign the task to someone else. That feels like the easy path. Lucas: It's the path that creates a silo culture. You reassign once, twice, and suddenly you have a team where nobody does anything outside their narrow lane. And when someone leaves, you have a huge gap. So instead, I recommend a 'scope conversation' that starts with a question: 'Help me understand why you see this as outside your role.' Luna: That's disarming. It invites them to explain rather than defend. Lucas: Right. And then you listen. Maybe they're worried about bandwidth. Maybe they think the task is below their skill level. Maybe they had a bad experience with a similar task before. All of those are addressable. But if you skip that step and just say 'do it anyway,' you get resentment. Luna: I once had a manager who used the phrase 'that's not in my portfolio' — basically the executive version of 'that's not my job.' And when we talked about it, it turned out she was worried about being evaluated on something outside her formal goals. So it was a performance review anxiety issue. Lucas: That's a really important angle. Many employees resist cross-functional work because they don't see how it counts toward their performance review. So you as a manager need to explicitly connect the task to their growth or their metrics. Say: 'I know this isn't in your current job description, but learning data migration will make you more valuable for the next promotion cycle, and I'll make sure that's reflected in your review.' Luna: That's a promise you have to keep, though. Otherwise you lose credibility forever. Lucas: Absolutely. You cannot ask someone to step outside their job description and then not credit them for it. That's how you create a cynic. And on that point — and this is a bit of a sidebar, but it connects — this is exactly the kind of practical advice we try to give on this show, and we've always kept the show ad-free because we think that makes the advice more trustworthy. We don't have sponsors pushing any agenda. If you find value in that approach and want to support it, you can at buy me a coffee dot com slash fexingo. It's a simple way to keep us independent. Anyway, back to Derek. Luna: Yeah, I appreciate that. So what happened with Derek? Did the scope conversation work? Lucas: It did, but it took two conversations. The first time, he admitted he was worried about failing — he'd never done data migration and was afraid it would slow him down. So we arranged for him to shadow the data team for two afternoons. After that, he felt confident enough to take it on. And six months later, he was actually leading a migration project. Luna: So the 'not my job' was really a cover for 'I'm not sure I can do it.' Lucas: Often it is. And that's why I never want managers to treat the phrase as insubordination right away. It's a symptom. Your job is to diagnose what's underneath. Luna: What about the person who says it repeatedly, even after you've clarified expectations and provided training? Then it's a pattern. Lucas: At that point, it becomes a performance issue. And you need to escalate the conversation. I'd say something like: 'We've talked about this task twice already. I need you to complete it by Friday. If you can't, we need to discuss whether this role is the right fit for you.' That's a last resort, but sometimes you have to be direct. Luna: Have you ever had someone quit over a conversation like that? Lucas: Once. An engineer who genuinely believed his role should be strictly coding and nothing else. He left for a company with a more rigid structure. And honestly, it was probably the right outcome for both sides. Not every team needs a siloed specialist, and not every employee wants a fluid role. Luna: So part of managing is knowing when to let someone go to a place that fits them better. Lucas: Exactly. Retention isn't about keeping everyone at all costs. It's about keeping the right people who align with the team's needs. And a team that needs cross-functional collaboration cannot carry someone who insists on a narrow scope. Luna: Let's talk about prevention. How do you set up a team so that 'that's not my job' rarely comes up? Lucas: I think the single most effective thing is to, during onboarding and at quarterly check-ins, explicitly discuss role fluidity. Say: 'In this team, we all pitch in on urgent tasks. Your core responsibilities are X, Y, Z, but you should expect about 20 percent of your time to go toward unexpected needs.' That sets the norm upfront. Luna: So it's about managing expectations from day one rather than reacting. Lucas: Yes. And also modeling the behavior. If you as a manager ever say 'that's not my job' when someone asks you for help, you've lost the right to ask them to do the same. So be willing to step outside your own role. Luna: That's a good point. I've seen managers who are happy to delegate cross-functional work but would never do it themselves. Lucas: Right. And that creates resentment. So if you want a team that's flexible, you have to be flexible first. Luna: What about using team agreements? Like a written document that says 'we support each other on tasks outside our core role when needed'? Lucas: I love that. And the best ones include a clause like 'if you feel overloaded, you can say no, but you must offer a solution — like a later date or a partial contribution.' That way, 'no' becomes a negotiation, not a wall. Luna: So you're not forcing anyone to say yes, but you're also not letting them just shut down a request. Lucas: Exactly. It preserves autonomy while ensuring accountability. Luna: I want to circle back to something you said earlier about the responsibility ladder. How do you introduce that to a team without sounding like you're giving them a lecture? Lucas: I usually do it during a one-on-one, not in a team meeting. I'll say: 'I've been thinking about how we work together, and I want to try a simple tool I learned. It's a ladder of responsibility. Can I walk you through it?' Most people are curious. Then I ask them where they see themselves on that ladder for their main projects. And then I share where I see them. If there's a gap, we talk about it. Luna: That's non-confrontational. It's a shared framework. Lucas: Yes. And it makes the abstract concept of 'ownership' concrete. People understand ladders. They know what it means to climb a rung. Luna: We've covered a lot. Let's bring it home with a summary. For a new manager who faces 'that's not my job' tomorrow, what's the first thing they should do? Lucas: Pause. Don't react. Say: 'Okay, I hear you. Let's talk about that.' Then in the conversation, figure out if it's a job description issue, a skill issue, a bandwidth issue, or a mindset issue. Each requires a different response. And if you handle it well, you might turn a blocker into one of your most flexible team members. Luna: And if you handle it poorly, you get a silo. So the stakes are real. Lucas: They are. But the good news is, most of the time, the phrase 'that's not my job' is a request for clarity, not a declaration of war. Treat it as a signal, not a threat, and you'll get somewhere. Luna: Well said. Thanks, Lucas. Lucas: Thanks, Luna. Talk to you next Monday.