You send the message. Three dots appear, disappear, appear again. Then: “Sure. Whatever works.” No punctuation has ever felt colder than that period. You read it four times trying to decide whether you’re inventing the chill, and you land where you always land: probably overreacting, better not to make it weird. So you say nothing. The task comes back late, or half-done, or with a sigh loud enough to carry across the room, and underneath the annoyance sits a quieter question you can’t shake. If you actually name this out loud, does it get worse?
That question is the reason passive-aggressive behavior works. It stays deniable, and as HBR’s Amy Gallo lays out in her guide to the passive-aggressive colleague, the behavior survives because each individual move is small enough that calling it out feels like an overreaction. The person can always answer “I said it was fine” with a completely straight face. So most people wait and hope it burns off on its own. It rarely does. What follows is a way to name what’s happening in language calm enough that it can’t be turned back on you, plus the exact lines for the six moments this shows up most.
What counts as passive-aggressive behavior at work
Passive-aggressive behavior at work is the indirect expression of a negative feeling. Instead of saying “I disagree” or “I’m swamped,” the person routes the resistance through tone, delay, or a deniable dig. The American Psychological Association describes it as showing negative feelings like resentment through unassertive, roundabout channels rather than open ones.
Two things matter before you do anything with that. First, you’re reading a pattern of moves, not diagnosing a person. You’re not qualified to hand a coworker a clinical label, and you don’t need one, so skip the urge to brand someone’s whole character passive-aggressive or reach for the internet-diagnosis version. Second, one bad day is not a pattern. Everyone gets clipped and short when they’re buried. What you’re watching for is the same move, repeating, pointed at you or your work. Telling a real pattern apart from a stray mood is mostly a question of how well you read people, so it’s worth being honest with yourself about that before you act.
Here’s what the pattern looks like on the ground. If you recognize one of these, there’s a script for it further down:
- The loud sigh followed by “no, it’s fine” when it clearly isn’t.
- The icy “sure, whatever you think is best” that ends the conversation and quietly withdraws the effort.
- The compliment with a hook in it, delivered in front of other people.
- The reply-all with a small dig buried inside an otherwise professional email.
- The “I didn’t realize that was urgent” that surfaces exactly as your deadline slips.
- The sudden silence in Slack or Teams, where someone who used to answer fast now leaves you on read.
How to name it without starting a fight
You name passive-aggressive behavior without starting a fight by describing what you can observe and dropping what you can only guess. The fight starts the moment you name the motive. “You’re obviously annoyed with me” is a mind-reading accusation, and the only available reply to it is denial, because nobody can prove what’s in another person’s head. Point at the thing you both actually witnessed instead, and there’s nothing left to deny. A companion piece on Amy Gallo’s site makes the same case from the other direction: you can’t simply avoid these coworkers, and dropping the accusatory language is what stops the exchange from escalating.
The line that does this has three parts, and it holds up peer to peer because none of it pulls rank.
- Name the observable action, not the motive. “That came across as clipped,” or “the update didn’t land the way I think you meant it.” You’re pointing at something that happened in the room, not at their inner state. They can’t argue you out of what you saw.
- State the impact or the need in your own terms. “I’d rather know now if the timeline’s a problem, because I’m planning my whole week around it.” You’re not accusing them of causing a feeling. You’re telling them what you need to get your job done.
- Invite a real, answerable response. Not “is everything okay?” which begs a reflexive “fine” and closes the door. Ask something they actually have to answer: “Is Thursday still realistic, or should I move it?” A closed, specific question is far harder to wave off than a vague check-in.
Notice what’s missing from all three: any version of “as the person running this, I need you to.” That’s on purpose. Most advice assumes you can lean on a title and make an expectation stick. As a peer you can’t, and borrowing a manager’s framework reads as bossy, which just hands the person a fresh reason to resent you. The neutral line works because it claims no authority. It states what you saw and what you need, then leaves a clean way to respond. This is the core rep of conflict resolution between peers, and it’s a skill you can measure and build, not a personality trait you either have or don’t.
Six passive-aggressive moments and the exact line for each
Below are the six moments this shows up most. Each one has what’s driving it underneath, the neutral line to use, what to do when the line doesn’t land, and the point where it stops being worth handling on your own.
1. The loud sigh and “no, it’s fine”
Underneath, the sigh is a bid for you to notice without them having to ask for anything. “It’s fine” protects them from owning a request they aren’t sure is reasonable.
The line: “That landed more like a sigh than a fine. If there’s something in the plan you’d change, I’d genuinely rather hear it now than find out Thursday.”
If it doesn’t land: take them at their literal word, once, out loud. “Okay, I’ll treat that as a yes to the plan then.” It quietly closes the deniability, and now the “fine” is on record as agreement.
When it crosses into escalate: when the sighing is daily and the “fine” keeps turning into missed or half-finished work, it has stopped being a mood and started costing you delivery.
2. The icy “sure, whatever you think is best”
This is a withdrawal. They’ve decided that arguing isn’t worth it, so they’re handing you the decision and, very quietly, the blame if it goes sideways.
The line: “I can tell this isn’t your first choice, and I’d honestly rather have your real read than a rubber stamp. What would you do differently?”
If it doesn’t land: make the handoff explicit and flat. “Okay. I’m going to go with option A, and I’ll note that you were good with me making the call.” No sarcasm. You’re simply refusing to carry blame nobody assigned out loud.
When it crosses into escalate: if “whatever you think” is followed by them relitigating the same decision to other people afterward, that’s undermining, and it earns a direct or escalated conversation.
3. The backhanded compliment in front of others
The audience is the whole point. “Wow, look who finally cracked the deck” scores a point on you while staying deniable as a joke.
The line, light and in the moment: “I’ll take the compliment and leave the ‘finally.’” Said evenly, with a small smile, you’ve named the hook without making a scene.
If it doesn’t land or it keeps happening: take it out of the audience. Later, one on one: “In standup you said I finally figured it out. I’m sure it was a joke, and it landed as a dig. I’d rather we skip the public zingers.” Observable, need, done.
When it crosses into escalate: a running habit of public put-downs is a reputational cost, not just a sting. If it continues after you’ve named it privately once, loop in whoever runs the meeting or a shared stakeholder.
4. The reply-all dig
The email version is calculated because it’s written down, saved, and witnessed. The dig is usually a quiet claim about your competence, dressed up as a helpful clarification. This is the “passive aggressive email” that sits in your chest for an hour.
The line, reply-all, in the same even register they used: “Thanks for flagging. To close the loop for everyone, the slip on the launch date was the vendor timeline, not the brief. Happy to walk through it live if that’s useful.” You’ve corrected the record in the same public channel, with no change in temperature.
If it doesn’t land: move it off the thread. Reply to them alone: “The reply-all read as pointed. If you’ve got a concern about how I’m handling this, I’d rather hear it directly.” Don’t fight in the public channel a second time.
When it crosses into escalate: a paper trail of digs aimed at your credibility is exactly the sort of thing to keep, and to bring to a manager with the receipts if it continues.
5. The “I didn’t realize that was urgent” deadline slip
This runs on plausible deniability built over a genuine gray area. Maybe the priority really wasn’t crystal clear, and they’re using that gap to avoid owning the miss.
The line, which removes the gray area going forward without relitigating the past: “Fair enough, that’s on me for not flagging the date hard enough. So we’re aligned, this needs to be done by Wednesday at 5, and I’ll drop a reminder Tuesday. Does that work on your end?”
If it doesn’t land: when the deadline slips again after you’ve made it explicit and confirmed, the “I didn’t realize” excuse is spent. Make the dependency visible to whoever owns the deadline so the delay is a shared fact instead of a private frustration.
When it crosses into escalate: repeated missed commitments after clear, confirmed deadlines is a delivery problem. Document the dates and escalate the decision, not the person.
6. The sudden Slack or Teams silent treatment
Withholding a reply expresses displeasure while never saying a thing they could be held to. It punishes you with pure ambiguity.
The line, which names the change in behavior rather than the reason you’re imagining: “I’ve noticed my messages are getting slower replies than they used to. If I did something that landed wrong, I’d rather know so I can fix it. If it’s just bandwidth, tell me and I’ll stop wondering.”
If it doesn’t land: switch channels once. A quick “got two minutes to sync on this?” in person or on a call removes the medium they’re using to stonewall. If they dodge that too, you have your answer about whether it’s really bandwidth.
When it crosses into escalate: when the silence starts blocking your actual work, like approvals you can’t get or information only they hold, it’s a work blocker whatever the emotion behind it. Route around it to their manager or your shared lead, framed as a stuck deliverable.
Escalate or let it go: a quick self-check
Not every passive-aggressive moment is worth a conversation, and a few are worth far more. Run three checks before you decide.
- Frequency. Is this a one-off, or the same move on repeat? A single icy reply on a rough day is weather. The same person, same dig, week after week, is a pattern.
- Impact on your deliverables. Is it merely unpleasant, or is it costing you something real: deadlines you’re accountable for, decisions reopened behind your back, information you can’t get?
- Response to being named once. You’ve used the neutral line, calmly, one time. Did anything shift, even a little, or did it roll on exactly as before?
Score it plainly. Two or more of these pointing to “yes, this is real” means escalate, and escalate with specifics: the dates, the concrete cost to the work, and the fact that you already tried to sort it out directly. Zero or one means let it go for now and keep a quiet eye on it. Escalating a single sigh burns credibility you’ll want later. Sitting on a documented, repeating, delivery-damaging pattern just teaches the person that it works. Doing this well means escalating the decision and not the coworker, which is the whole art of resolving conflict as an IC without a title.
Rehearse the line before the moment, not during it
The reason these lines fail usually isn’t the wording. It’s that the first time you ever say them out loud is to the actual coworker, with your pulse up and their face doing something you didn’t plan for. You can’t practice on them. The real conversation is the only rep you get.
So practice somewhere the stakes are zero. Read the neutral line for your specific situation out loud a few times until it stops sounding stiff, and get someone to throw the pushback back at you: the flat “I said it was fine,” the wounded “wow, okay,” the wall of silence. Merlin can play the difficult coworker and push back the way they actually will, so you get to hear your line land badly, feel the flinch, and fix the wording before it counts for real. One note on privacy, since people always ask: coaching you start yourself is private to you, and only journeys your company assigns ever produce a manager-visible summary, which shows engagement and skill level and never the transcript.