You reread the message again. "Thanks for finally getting to this." "Per my last email…" "Interesting choice." On the surface it's fine — nothing you could forward to HR, nothing you could even name out loud without sounding oversensitive. But you felt the edge in it. And now, hours later, you're still turning it over: Was that a dig? Am I imagining it? What did I even do?
That low, deniable friction is the hardest kind to deal with — precisely because it's deniable. There's nothing concrete to point to, so you can't address it head-on, and it lingers. This is a practical guide to responding to it: what's actually happening, how to answer in the moment, and how to stop carrying it home.
First: what passive-aggression actually is
Passive-aggression is indirect expression of a negative feeling. Your manager is feeling something — frustration, pressure, territoriality, their own stress from above — and instead of saying it directly, it's leaking out sideways: in tone, in a pointed word, in a cc'd email, in praise with a hook in it.
This matters for one practical reason: the sideways jab is rarely about the thing it's attached to. "Thanks for finally getting to this" is probably not really about the timing of your task. It's a feeling looking for an exit. Understanding that doesn't excuse it — but it changes how you respond, because it tells you the bait isn't the real thing, and you don't have to take it.
The core move: respond to the content, not the tone
This is the single most effective technique, and it feels almost too simple: answer what was literally said, and let the tone fall flat.
When someone sends "Thanks for finally getting to this," there are two messages: the content ("you completed the task") and the tone (the dig). If you respond to the tone — defensive, apologetic, or matching their edge — you step into the conflict they baited, and now it escalates sideways where you can't win. If you respond only to the content, calmly and professionally, the jab has nowhere to land:
"All done — let me know if you'd like any changes."
No defensiveness, no apology, no taking the bait. You've answered the real question and quietly declined the fight. Most passive-aggression deflates when it doesn't get a reaction, because the reaction was the point. This isn't about being a pushover — it's about refusing to play a game rigged against you, and staying the calm professional in the exchange.
When you genuinely can't tell if it was a dig
Half the exhaustion of passive-aggression is the ambiguity — the hours spent wondering if you imagined it. There's a clean tool for this: the sincere clarifying question.
If a message is genuinely unclear or feels loaded, you can surface it without accusation by asking — straight, no edge:
"Want to make sure I'm reading this right — are you looking for a different approach here, or is the timeline the concern?"
This does two things. It calls the vagueness into the open (so they have to say what they actually mean, which passive-aggression hates), and it does so in good faith, so you stay reasonable. Often the answer defuses it entirely — "oh, no, the timeline's fine, just stressed about the client." Sometimes it forces a real conversation that needed to happen. Either way, you've moved from guessing to knowing, which is the thing that stops the rumination.
Don't diagnose it in writing
A tempting trap: replying with something that names the behavior — "I'm sensing some frustration here." Resist it over email or Slack. Naming someone's passive-aggression in writing almost always escalates, because it's a charged read they can deny, and now it's on the record. If something genuinely needs addressing, do it in a live conversation (or a call), where tone and nuance exist and nothing is preserved to be reread out of context.
When it's a pattern, not a one-off
A single sideways comment you can let roll off. A pattern — recurring digs, consistent undermining, a manager whose default is the deniable jab — is different, and "respond to the content" stops being enough on its own. A few things help:
Create a clear record, neutrally. Not a grievance file — just keeping your own work and communications clear and documented, so that if the ambiguity ever becomes a real problem, you have facts, not feelings, to point to.
Address the pattern directly, once, in person. Not the individual jabs (each is deniable), but the pattern, calmly: "I want to make sure we're communicating well — sometimes I'm not sure where I stand on my work. Can we set up a quick regular check-in?" You're naming the need (clarity), not the crime (their behavior), which is far harder to deflect and keeps you the reasonable one.
Know the line. If it crosses from frustrating into genuinely undermining your work or wellbeing over time, that's a real workplace issue, and it may be worth a conversation with someone you trust or HR. That's a higher bar than everyday friction — but it's worth knowing the line exists, so you're not just absorbing it indefinitely.
The part nobody talks about: the residue
Here's the thing the tactics don't fix. You can respond perfectly — answer the content, stay calm, decline the bait — and still carry it home. The unfairness of it sits with you. You replay the exchange. You draft the reply you wish you'd sent. You wonder if you're too sensitive. The interaction is over, but it's still running in your head at 9pm.
That residue is real, and it's worth dealing with on purpose, because responding well at work doesn't automatically discharge it. A few things help:
Name what you actually felt — not "that was annoying," but the specific thing: dismissed, undermined, not trusted, made to feel small. Putting the precise feeling into words takes a surprising amount of the charge out of it. The vague hum is worse than the named thing.
Separate what you can act on from what you can't. You can control your next response; you can't control whether your manager is fair. Sorting the two — here's my move tomorrow, and here's the part I have to set down — is what lets the loop actually close. The stress comes from the tangle; untangling it is the relief.
Get it out of your head before you try to rest. The exchange keeps circling partly because your brain is holding it open, afraid to let go of something unresolved. Saying it out loud or writing it down — even just to yourself — signals handled, and the brain loosens its grip.
The honest bottom line
You can't make your manager communicate directly. What you can do is refuse the bait, answer the real question, surface the ambiguity in good faith, and — when it matters — name the pattern calmly. And then, separately, you can deal with what it left behind, so a deniable jab at 3pm doesn't get to own your evening.
The goal isn't to win the sideways war. It's to stay the calm, reasonable professional in the exchange — and to not let someone else's indirectness become the thing you carry to bed.