Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Says That's Not in My Job Description
Transcript
- Lucas: You're a first-time manager. You ask a team member to handle a quick task — something urgent, something reasonable — and they look you in the eye and say, 'That's not in my job description.' Luna: And you freeze. Because technically... maybe they have a point? But also, the work needs to get done. Lucas: Right. That moment is the subject of today's episode. Episode 82 of Manager Mondays. I'm Lucas. Luna: I'm Luna. And we've covered a lot of 'how to manage an employee who...' scenarios, but this one — the job description shield — it's a classic. Lucas: It is. And it's actually harder than it sounds because the employee may be genuinely correct. Many job descriptions are written by HR or inherited from a previous role and they're often too narrow or outdated. Luna: So you can't just say 'do it anyway' without considering whether you're actually asking something outside their scope. Lucas: Exactly. So let me anchor this with a specific case. About 18 months ago I was working with a VP of Engineering at a mid-sized SaaS company — roughly 400 employees. They had a senior backend engineer, let's call him David. David was excellent at his core responsibilities: maintaining API endpoints, writing documentation, reviewing pull requests. But one Friday afternoon, a production bug came in that affected a customer-facing dashboard that David's team owned indirectly. The fix wasn't complicated — maybe an hour of work — but it involved touching a front-end component. David's job description said 'backend engineer'. He refused. Said it wasn't his job. Luna: Oof. And what happened? Did the VP escalate? Lucas: Initially the VP was frustrated. He thought about writing David up. But instead, he called me and we walked through a framework I've developed for exactly this situation. It has three steps. Luna: Okay, lay it out for us. Lucas: Step one: clarify expectations before you need them. Most managers never explicitly discuss the scope of a role beyond the job description. They assume 'we're a team, we help each other'. But that assumption is the root cause. If you haven't had a conversation about the unwritten rules — like 'when production is down, everyone pitches in regardless of title' — then you don't have a leg to stand on when someone invokes their job description. Luna: So prevention is really the first intervention. But what if you're already in the heat of the moment? Like David's VP was. Lucas: That's step two: separate the behavior from the person. You don't accuse David of being unhelpful. You say, 'I hear you that this isn't in your job description. Let's talk about why I asked you specifically and what our team's shared responsibility is in critical moments.' Then you ask a question: 'In the future, if a similar situation arises, what would make it feel more appropriate for you to step in?' That opens a dialogue instead of a power struggle. Luna: And step three? Lucas: Step three: update the job description — or don't, but make a conscious choice. If a role genuinely needs to be flexible, rewrite the description to include a clause like 'and other duties as needed to support the team's objectives.' If you decide that the role truly is narrow and you need a different person for other tasks, then own that decision and hire accordingly. But don't leave it ambiguous. Luna: So in David's case, what happened? Did they update the description? Lucas: They did. The VP sat down with David after the crisis was resolved and they redrafted his role together. They added a line about 'triage and support for adjacent systems in production incidents.' David actually appreciated it because it made expectations clear. He wasn't trying to be difficult — he was trying to protect his boundaries based on what he'd been told his job was. Luna: That's a great outcome. But I want to push back a little. Sometimes the employee is being unreasonable, right? I mean, we've all worked with someone who hides behind their job description to avoid any extra work. Lucas: Absolutely. That's the other side of the coin. And in that case, the issue isn't the job description — it's the employee's attitude. But even then, the framework helps. Step one reveals whether you ever set the expectation that team members support each other. If you did and you have evidence, then step two becomes a coaching conversation about accountability. Step three might involve formal performance improvement. Luna: Right. So the framework works whether the employee is in good faith or bad faith. That's useful. Lucas: Exactly. And what I love about this is that it forces the manager to take responsibility first. Did I set the team up for success? Did I communicate the unwritten rules? If the answer is no, then the problem starts with me. Luna: You know, this reminds me of something I read recently. A study from Gallup — I think it was 2023 — found that only about 30 percent of employees strongly agree that their job description matches the work they actually do. So there's a systemic mismatch. The job description is often a relic of a hiring process, not a living document. Lucas: That's a crucial point. And managers rarely revisit job descriptions after hire. They just let them sit in the HR system. So if you're managing someone who says 'that's not in my job description,' it might be a sign that you need to update the document — not punish the person. Luna: And that brings up another angle: what about the rest of the team? If one person is allowed to say no to tasks outside their description, but others routinely pick up the slack, you create resentment. Lucas: Resentment and inequity. So step zero, before the framework, is to check if you have a culture where some people are expected to be flexible and others aren't. That's a leadership failure. If David can say no but the junior front-end developer can't, you've got a fairness problem. Luna: So let's talk about the conversation itself. You mentioned asking the employee 'what would make it feel more appropriate to step in?' Can you give us a specific script for that? Lucas: Sure. So you're in the moment. The employee just said 'that's not my job.' You take a breath. You say: 'I appreciate you being clear about your understanding of your role. Let me share why I asked you specifically — you have the most context on this system, and the fix needs to happen quickly. In the future, if a similar situation comes up, what would make it feel like a reasonable request to you?' Then listen. Maybe they need more notice. Maybe they want a rotation so it's fair. Maybe they want the job description updated. You find the real issue. Luna: I like that. It's not confrontational. It's curious. Lucas: And it preserves the relationship. Because if you come in hot and say 'you're not a team player,' you're going to get defensiveness. But if you treat their concern as legitimate — even if you disagree — you keep the door open. Luna: Okay, but what if after that conversation, the employee still refuses? Like, they say 'no, I really don't think this is my job' and they won't budge. Lucas: Then you escalate to step three faster. You say, 'I hear you. Let's schedule a time to review your job description and clarify expectations going forward. For now, I need this task done. I'm going to assign it to someone else, but we will follow up.' And then you do follow up. You don't let it drop. Luna: So you don't force the issue in the moment. You buy time. Lucas: Exactly. Because forcing someone in a crisis creates long-term damage. Better to solve the immediate problem with another resource and then address the root cause later. Luna: That's a really practical takeaway. I'm going to remember that. Lucas: And I think that's a good note to wrap this part. Before we go further, I want to mention something. You know, we've been doing Manager Mondays for over 80 episodes now — covering all kinds of tough people situations. And one reason we can explore these topics in depth is that the show is ad-free. We deliberately don't run ads. Not because we're anti-business — obviously — but because we think this kind of practical career content works better without interruptions. Luna: Yeah. And if you've gotten value from episodes like this one — maybe you used the framework with your own team or you shared it with a friend — there's a simple way to support that choice. It's buy me a coffee dot com slash fexingo. That's it. No subscription, no patreon tiers. Just a one-time coffee if you feel like it. Lucas: And it genuinely helps us keep making these episodes without sponsors or ads. So thanks for considering that. Now, back to the job description conversation — because there's another layer I want to cover. Luna: What's that? Lucas: The legal angle. Some employees genuinely believe that if something isn't in their written job description, they can't be required to do it. In most at-will employment situations in the US, that's not true — employers can change responsibilities. But in practice, if an employee has a contract or a union agreement, it might be different. So managers need to check their context. Luna: Good point. And also, if you're managing someone in a country with strong labor protections, you need to be careful. So managers should consult HR before making any demands. Lucas: Right. But for the vast majority of knowledge workers, the job description is a guideline, not a legal document. The real issue is trust and clarity. Luna: So let's talk about trust. If an employee has used the job description shield before, how do you rebuild trust after resolving the conflict? Lucas: You rebuild trust by following through on your commitments. If you said you'd update the job description, update it. If you said you'd create a rotation for unpleasant tasks, create it. And then you have a follow-up conversation: 'Hey, I wanted to check in on how things have been since we clarified your role. Do you feel clearer about expectations?' That shows you care about the long-term relationship, not just the immediate task. Luna: And if the employee continues to be rigid even after the clarification? Lucas: Then you have a performance issue, not a job description issue. And you manage it like any other performance problem — with clear feedback, documentation, and consequences. But you start with the assumption that the employee wants to do the right thing. Most do. Luna: I think that's a really important takeaway. Assume good intent first, investigate, then act. Lucas: Exactly. And I'd add one more thing: as a first-time manager, you're going to encounter this situation at some point. It's almost inevitable. So being prepared with a framework — clarify, separate, update — can make the difference between a conflict that damages the relationship and a conversation that strengthens it. Luna: Great advice. So to recap for our listeners: if a team member says 'that's not in my job description', don't react defensively. First, check if you've set clear expectations. Then, have a curious conversation to understand their perspective. Finally, update the role documentation to reflect reality. Lucas: And if you're the one hearing that phrase, take it as a signal — not necessarily a sign of bad attitude, but a sign that your team's role clarity needs work. Luna: Well said. Thanks for joining us on Manager Mondays. We'll be back next week with another real-world leadership challenge. Lucas: Until then, keep leading with clarity.