What to Say When an Employee Says ''That's Not My Job

The request felt straightforward. You’ve asked your senior analyst, Mark, to pull together some numbers for the board deck. It’s not a huge lift, but it’s urgent. You’re standing by his desk, and the air in the open-plan office suddenly feels very still. Mark looks up from his screen, not at you, but at a point just over your shoulder. He says, “I can’t. That’s not my job.” Your mind goes blank for a second. Your first thought is to say, “Yes, it is.” Your second is to list all the reasons it has to be him. You can feel your face getting warm, and you’re acutely aware of the junior staff who can probably hear this. You’re searching for the right words, wondering what to do when an employee says ‘that’s not my job’ without turning this into a public power struggle.

When this happens, it feels like a direct challenge to your authority. But it’s almost never about insubordination. The phrase “That’s not my job” is a symptom of a hidden breakdown in the shared understanding of a role. It’s a clumsy, defensive signal that the unwritten rules of work, who does what, who carries the extra weight, what’s considered fair, have been violated. Your employee isn’t just refusing a task; they are trying to redraw a boundary they feel you have crossed. The reason it feels so high-stakes is that it forces a hidden conversation about roles, fairness, and workload out into the open, and it does so without any of the language or preparation needed to have that conversation well.

What’s Actually Going On Here

“That’s not my job” is a surface-level phrase for a deeper, systemic issue. In most organisations, job descriptions are vague documents, filled with phrases like “support the team” or “other duties as assigned.” They aren’t precise, operational guides to how work is actually distributed. In reality, work flows like water to the place of least resistance, usually, the most competent and responsible person on the team. That person says yes, delivers high-quality work, and doesn’t complain. Until they do.

Consider a senior engineer who is repeatedly asked to mentor junior staff. It’s not in her job description, but she’s good at it. At first, it feels like a recognition of her skills. After six months, she’s spending a quarter of her time on unrecognised, unrewarded mentoring while her own project deadlines loom. The next time a manager asks her to “just help out” a new hire, she says, “I’m sorry, but that’s not my job.” The manager sees a difficult employee refusing to be a team player. The engineer sees herself protecting the core function she is actually paid and evaluated on.

The system itself creates this conflict. By leaving role boundaries informal and relying on goodwill, the organisation ensures that its most capable people will eventually become overloaded. The employee who finally draws the line isn’t the least dedicated; they are often the most dedicated person who has reached a breaking point. They are enforcing a boundary that the system has failed to provide. Their blunt phrase is a reaction to a pattern of requests that feels unsustainable and unfair.

What People Usually Try (and Why It Backfires)

When your authority feels questioned, your instincts will probably lead you down one of several paths. They are logical, common, and almost always make the situation worse.

• Pulling Rank: You might say, “Actually, as your manager, I’m telling you that it is.” This move ends the immediate debate, but it fundamentally changes the relationship. You’ve turned a conversation about roles into a raw exercise of power. You’ll get compliance on this one task, but you’ve lost trust and planted the seeds of resentment.
• Minimizing the Request: A common move is to downplay the work: “Come on, it’ll only take twenty minutes.” This feels helpful, but it dismisses the employee’s real concern. The problem isn’t the twenty minutes. The problem is the precedent, the pattern of work, or the principle of the thing. By minimizing, you signal that you aren’t listening to what they’re actually trying to tell you.
• Appealing to Teamwork: You try to frame it as a matter of attitude: “We all need to pitch in and be team players.” This is a subtle accusation that implies the employee is selfish. It’s a form of guilt-tripping that attempts to shame them into compliance, and it invalidates their legitimate concern about their role and workload. It’s an especially damaging move if they’re the one who always pitches in.
• Litigating the Job Description: The most bureaucratic response is to say, “Let’s look at your JD. It says ‘other duties as assigned’ right here.” This is the workplace equivalent of saying “because I said so.” It’s a conversation-killer. It tells the employee that you are not interested in their lived experience of the job, only in what you can contractually force them to do.

A Better Way to Think About It

The fundamental mistake in all the moves above is treating this as a conflict over a single task. It’s not. It’s a signal that the shared understanding of the role has broken down. Therefore, your goal is not to win the argument and get the task done. Your goal is to use this moment to clarify the role for the next six months.

This shifts your entire posture. You are no longer an authority figure trying to enforce compliance. You are a manager trying to diagnose a problem with the work system. You are moving the conversation from “Will you do this?” to “Help me understand the mismatch between what I’m asking and your understanding of your responsibilities.”

By focusing on the role, not the task, you accomplish three things. First, you dramatically lower the emotional temperature. It’s no longer a personal battle of wills. Second, you show the employee that you are listening to the real issue they are raising, even if they raised it clumsily. Third, you turn a moment of conflict into a productive conversation about how the team functions. You are not trying to prove them wrong; you are trying to get aligned.

A Few Lines That Fit This Move

These are not scripts to be memorized, but illustrations of how this shift in thinking sounds in practice. The goal is to open a different kind of conversation.

• “Okay, let’s pause on the task for a moment. When I asked you to do X, you said, ‘That’s not my job.’ Help me understand what part of that request felt like it was outside the lines for you.” This line works because it de-escalates immediately by setting the contentious task aside and opens a diagnostic conversation about the role itself.
• “You’re right, this isn’t something you do every day. The reason I brought it to you is because it connects to [core responsibility or development goal]. Does that connection make sense from your side, or does it still feel separate?” This validates their perception (“you’re right”) while reframing the request. It links the unfamiliar task to a larger, agreed-upon purpose and invites them to co-author that link.
• “I hear you. It sounds like there’s a larger concern here about workload or how your role is defined. Can we talk about that bigger picture for a few minutes?” This line names the likely underlying issue directly, workload, role clarity, showing that you’re listening for the message behind the words, not just reacting to the surface-level refusal.
• “Let’s assume for a second you’re right and this task doesn’t fit neatly into your job description. The work still needs to get done. From your perspective, who on the team is best positioned for it, and how should we handle these kinds of requests in the future?” This is a powerful move that bypasses the personal conflict entirely. It provisionally accepts their premise and immediately enlists them as a problem-solving partner in fixing the systemic issue.