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

A manager brings you a scene that still has heat in it. They asked a senior analyst for some board-deck numbers, urgent, no big deal. The analyst looked past their shoulder and said, “I can’t. That’s not my job.” Your client tells you their first impulse was to say “Yes, it is,” their second to recite every reason it had to be that person, and that the junior staff were within earshot the whole time. They want a better line for next time. The work is to stop them reaching for a line at all until they understand what the refusal was protecting.

Your client read the moment as a challenge to their authority. It almost never is. “That’s not my job” is what a role breakdown sounds like when nobody has the words for it. The unwritten agreement about who does what, who absorbs the overflow, what counts as fair, has been violated, and the employee is reaching for the bluntest available tool to redraw a line. Help your client see that the phrase is a boundary marker wearing the costume of insubordination.

What the refusal is actually defending

In most organizations the job description is a vague document. “Support the team.” “Other duties as assigned.” It was never an operational map of how work gets distributed. Work flows like water, toward the point of least resistance, which is usually the most competent and responsible person on the team. That person says yes, delivers, does not complain. Until one day they do.

Walk your client through the slow version. A senior engineer gets asked to mentor junior staff. Nothing in her description, but she is good at it, and at first the requests feel like recognition. Six months on she is spending a quarter of her week on mentoring nobody logs or rewards while her own deadlines close in. The next “just help out the new hire” gets met with “I’m sorry, that’s not my job.” Her manager sees a difficult employee who will not play team. She sees herself defending the core function she is actually paid and reviewed on.

The system manufactures this collision. Leave role boundaries informal, run the whole thing on goodwill, and the most capable people are guaranteed to overload. The one who finally draws the line is rarely the least dedicated person on the team. More often she is the most dedicated, arrived at a breaking point, enforcing a boundary the organization never bothered to supply. Her blunt sentence is a reaction to a pattern of requests that stopped feeling sustainable a long time ago.

This matters for your client because their instinct points the wrong direction. They want to resolve the task. The task is the least interesting thing in the room.

The moves your client has already tried

When authority feels questioned, your client’s instincts pull toward one of four responses. Each one is common, each one feels reasonable in the moment, and each one makes the dynamic worse. Name them so your client can hear themselves coming.

Pulling rank. “As your manager, I’m telling you that it is.” This closes the immediate debate and changes the relationship underneath it. Your client has converted a conversation about roles into a raw demonstration of power. They get compliance on this one task and trade away trust for it.

Minimizing the request. “Come on, it’ll take twenty minutes.” It sounds generous. It dismisses the real concern. The twenty minutes was never the issue. The issue is the precedent, the accumulating pattern, the principle of the thing, and shrinking the task tells the employee their manager is not listening to any of that.

Appealing to teamwork. “We all need to pitch in.” This is an accusation in a soft wrapper. It implies the employee is selfish, it shames rather than asks, and it lands hardest on the person who has in fact been pitching in all along. The one most likely to refuse is the one who has been carrying the most.

Litigating the job description. “Let’s look at your JD, it says other duties as assigned right here.” The most bureaucratic option, and the workplace version of because I said so. It tells the employee their manager has no interest in the lived experience of the job, only in what can be contractually extracted.

The error running under all four is the same. Your client is treating a signal about the role as a fight over a single task.

The shift to coach

Move your client off the task and onto the role. Their goal is not to win the argument and get the numbers pulled. Their goal is to use this moment to clarify the role for the next six months.

That single move changes their posture in the room. They stop being an authority enforcing compliance and become a manager diagnosing a fault in the work system. The question shifts from “Will you do this?” to something closer to “Help me understand the gap between what I asked and how you see your responsibilities.” Same competence, aimed somewhere useful.

Coach your client toward three outcomes that follow from the shift. The emotional temperature drops, because it is no longer a contest of wills. The employee sees their manager actually heard the real issue, clumsy as the delivery was. And a flashpoint turns into a working conversation about how the team functions. Your client is not trying to prove the employee wrong. They are trying to get aligned.

Language that fits the new position

Give your client these as illustrations of how the shift sounds out loud, rather than scripts to memorize. Each one opens a different kind of conversation than the four backfiring moves do.

Set the task aside and open the diagnosis. “Let’s pause the task for a second. When I asked you to do this, you said it’s not your job. Help me understand what part of it felt outside the lines for you.” This works because it de-escalates the instant the contested task leaves the table, and it turns the refusal into information about the role.

Validate the perception, then reconnect the request. “You’re right, this isn’t something you do every day. I brought it to you because it connects to your core work on the launch. Does that link make sense from where you sit, or does it still feel separate?” The opening words concede the employee’s read. The rest ties an unfamiliar task to an agreed purpose and invites the employee to author that tie rather than swallow it.

Name the buried concern. “It sounds like there’s a bigger thing here about workload, or about how your role is actually defined. Can we talk about that for a few minutes?” This says, out loud, that your client is listening for the message under the refusal instead of reacting to its surface.

Hand back the problem. “Let’s assume you’re right and this doesn’t fit your job description. The work still has to get done. From your side, who’s best placed for it, and how should we handle these requests going forward?” This bypasses the personal standoff entirely. It provisionally grants the employee’s premise and recruits them as a partner in fixing the structural fault that produced the standoff in the first place.

What to listen for in the next session

Ask your client which conversation they actually had. The one about the task, or the one about the role. If they tell you they got the numbers and moved on, the role question is still open and the refusal will return wearing a different task.

Listen for whether the employee’s tone shifted when your client set the task aside. A defended employee softens the moment the contest disappears. If the employee kept pointing, steadily, at the same workload gap even after the de-escalation, read it as accurate reporting about a real overload. Your client’s job there is to redistribute the work, and persuasion will only make the report louder.

Watch for your client’s own verdict that the talk “didn’t resolve anything” because no task got assigned on the spot. That judgment is the old frame reasserting itself. With this pattern, a conversation that surfaced the role mismatch and left it visible did the thing it was supposed to do.

When the refusal is not about the role

Sometimes the employee genuinely cannot do the task. Skill they do not have, a competing deadline already promised elsewhere, a conflict your client cannot see from where they stand. The phrase comes out the same, but the content is real, and coaching your client to diagnose a boundary will miss it. The tell is whether the employee can name a concrete obstacle when invited to. A defended employee relaxes into the conversation. An employee with an actual constraint keeps describing the constraint.

And some refusals sit downstream of something your client cannot fix from the manager’s chair. A culture that punishes anyone who sets a limit, a chronically understaffed team where every request is genuinely one too many, a history between these two people that predates the board deck by years. When the refusal is a symptom of a system that is itself the problem, no improved sentence will reach it. The work then is to help your client see clearly what they are actually managing, and how little of it any line can touch.