# Examples of Passive Aggressive Behavior at Work — and How to Answer It Canonical URL: https://headwayskills.com/knowledge/professional-behaviors/examples-of-passive-aggressive-behavior/ Markdown URL: https://headwayskills.com/knowledge/professional-behaviors/examples-of-passive-aggressive-behavior.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving professional behaviors at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Eight examples of passive aggressive behavior at work — the backhanded compliment, the silent treatment, the vanishing file — and what to say instead of the label. ## Key facts - Title: Examples of Passive Aggressive Behavior at Work — and How to Answer It - Category: Professional Behaviors - Primary skill: Professional Behaviors - Related skills: Communication, Teamwork - Primary keyword: examples of passive aggressive behavior - Source page: https://headwayskills.com/knowledge/professional-behaviors/examples-of-passive-aggressive-behavior/ ## What this page covers - Eight examples of passive aggressive behavior at work — the backhanded compliment, the silent treatment, the vanishing file — and what to say instead of the label. - Practical guidance for examples of passive aggressive behavior - How this topic connects to Professional Behaviors ## Detailed explanation You asked a colleague for a file on Tuesday. On Thursday it still hasn't arrived, and the follow-up gets you a cheerful *So sorry — completely slipped my mind!* for the third time this month. The most common examples of passive aggressive behavior at work look exactly like that: the backhanded compliment, the silent treatment, the yes that quietly becomes a no, the request that keeps getting forgotten, the pointed *per my last email*. Each one carries a negative feeling sideways instead of saying it, and each one is built so that objecting makes you look like the unreasonable party. That last piece is the whole difficulty. It is also the part with a workable answer. ## Eight examples of passive aggressive behavior at work These are the forms that recur most across workplace and psychology coverage of the topic. They look unrelated on the surface, but they share one piece of engineering: every one of them comes with a ready-made innocent explanation. Spotting that escape hatch is what turns a vague bad feeling into something you can name. ### 1. The backhanded compliment Praise with a hook in it. The version Indeed cites is a colleague telling a new hire, "You're catching on quickly. I mean, I was worried at first, but you're getting there." Read once, it is encouragement. Read twice, it is a note that you were assumed incompetent. The escape hatch is the compliment itself: object to it and you become the person who can't take a nice word. Targeted sarcasm works on the same principle — the joke format supplies "I was only joking" as a permanent retreat. In both cases the wrapper is why it lands, and why it goes unanswered. ### 2. Yes out loud, no in the work Someone agrees to the task and then does it at the minimum. Psychology Today's rundown of workplace red flags describes it plainly: agreeing to something you didn't want to do and then doing it poorly or half-heartedly as a form of protest, or simply doing less when you were asked for more. Nothing was refused, so there is nothing to point at — the work exists, it is just thin. This one costs more than most, because by the time the gap is visible the deadline has usually passed and the repair lands on you. ### 3. "Per my last email" The written form, and common enough to have generated its own genre of advice — LanguageTool, Yesware and The Muse all publish lists of what to write instead. The trouble isn't the words but the direction they point: at the reader's inattention rather than at the information. The recommended replacements are unglamorous and they work. *I'm following up on this request.* Or a straight restatement — *To recap, the key point is...* — which hands the person the thing they need instead of a demerit for missing it. This is also the entry where plenty of readers recognize themselves rather than a colleague, which is a fair reason to get an outside read on [how your own emails land](https://assessment.headwayskills.com/) before going looking for the pattern in someone else. ### 4. The file that never arrives, the invite you weren't on Career sources describe both together: a co-worker who "accidentally" leaves you off a meeting, or "forgets" to send the information you need for a project. Genuine oversight happens constantly, which is exactly what makes this one usable — the escape hatch is administrative. The tell is selectivity. Somebody who forgets everyone's requests has a system problem; somebody who only forgets yours does not. It is also the most consequential form on this list, because the damage shows up in your work rather than your mood. ### 5. The silent treatment Replies that used to arrive in an hour now take a day. Answers shrink to one word. Nothing is said about why, which leaves you to guess — and the guessing is the point. The escape hatch here is workload, because everyone is busy. What breaks it is naming the ambiguity rather than the person. The consultant Liane Davey suggests something close to *I don't know how to interpret your silence — how do you feel about this issue?*, which asks for the missing information without accusing anyone of withholding it. ### 6. The opinion withheld until it's too late You ask for input on the plan and get nothing. The plan goes ahead, hits a problem, and now the concerns arrive in detail — to other people. Monster lists this among its workplace examples: withholding opinions when feedback is requested, only to criticize the result afterward. The escape hatch is that the criticism is often correct, which makes it awkward to object to. What was withheld was the timing, not the judgment, and the timing was the part that would have helped. ### 7. Going around you instead of to you The disagreement never reaches you. It reaches your manager, on a bcc, or the rest of the team, as running commentary. Sources describe both moves: bcc'ing someone's boss into a thread when they aren't getting their way, and going over a manager's head in a way designed to make them look incompetent. The escape hatch is procedural — keeping people in the loop, raising it with the right person. The signal that it isn't that: you find out afterward, and from someone else. ### 8. The meetings you're always late to Chronic lateness to the meeting whose timing you resent, lunch breaks that run long, sick days that land on inconvenient mornings. Psychology Today groups these as time-based protest, and taken individually each one is unremarkable — traffic, a calendar clash, a genuine bug. The pattern carries the message, and the pattern is deliberately hard to raise, because addressing it means attributing a motive on evidence that is only ever circumstantial. ## What to say instead of naming it Here the advice is unusually consistent, and it opens with a prohibition: don't tell the person they're being passive-aggressive. The psychologist Mark Travers, writing in Forbes, and career sources such as Indeed converge on the same reason. The label produces denial or a counter-accusation, and within a minute you are arguing about a word instead of about what happened. What works is describing the observable thing and then asking. Let's Grow Leaders offers a shape worth borrowing — *What I hear you saying is that you feel like I'm getting more opportunities than I deserve. Is that right?* — or, for a barbed remark, something like *It sounds like there's something important underneath that.* Said calmly, these hand the person a way to say the direct version out loud, which is the thing they avoided in the first place. The second move is to change the channel. Several sources note that email gets chosen precisely because it avoids the face-to-face version, and the standard fix for a thread that has gone sideways is to stop writing and call, or walk over. Tone survives a conversation. It rarely survives a paragraph. ## The skills that make this easier to handle Notice how little of the above depended on knowing more examples. What changed the outcome each time was something small and repeatable: how you name a behavior, when you say the direct thing, whether you raise a broken commitment or wait for it to happen again. **Professional Behaviors** gives you a better vocabulary than the pop-psychology label does. The conduct it treats as unprofessional includes the passive kind, the aggressive kind and the manipulative kind — indirect communication, and talking about people behind their backs. That is a description of behavior rather than a diagnosis of a person, and the distinction is practical. You can't ask someone to stop having a personality. You can point at a norm, and a norm is the kind of thing a workplace has already agreed on. The same set covers speaking about colleagues as though they were in the room, which is the direct answer to the seventh item on that list. **Communication** occupies the space where all of this grows. Indirectness fills a gap where a direct sentence should have gone — a disagreement not voiced, a request not declined, an irritation not raised while it was still small. Speaking up, and being clear and direct, are the habits that keep the gap from opening in the first place. Direct isn't the same as blunt; the point is to say the thing in a way that leaves the relationship standing. It also settles the channel question the email examples make so concrete: anything sensitive belongs in a conversation, not in a paper trail. **Teamwork** covers the part that involves people you depend on. Trust there is built out of two ordinary things — meaning what you say, and doing what you committed to — and both are precisely what the half-done task and the vanishing file break. The answer this skill supplies isn't patience. It's accountability: raise the missed commitment specifically, and early, before the fifth repetition has turned it into the way things are. Necessary disagreements are meant to be had, as long as they stay on the topic and off the person. Of the three, the hardest to judge from the inside is your own directness — almost nobody thinks they're the indirect one. That is the gap the Job Skills Test is built for. It's free, it covers these three alongside the nine others that keep recurring across working life, and what it gives back is a sorting rather than a score. Instead of trying to work on all three at once, it's worth finding out [which one to work on](https://assessment.headwayskills.com/) first. Some of this may already describe how you operate. Plenty of people reach the end of a list like this and realize they've been doing the direct version for years — raising the thing while it was still small, asking instead of assuming — without ever calling it a skill. Where that isn't true yet, it's a question of habit rather than temperament, and habits are the part of yourself you get to write. You don't have to become a more confrontational person to stop absorbing sideways remarks, or to stop sending them. What does shift is the cost: the further into a career you go, the more of the work runs through people you can't simply route around, and the more an unspoken grievance ends up buying. Reading up on it before responding isn't the obvious move — the obvious move is a sharp reply, or another week of saying nothing. That choice is already the useful part. What's left is narrower: which of these habits is solid for you, and which one would repay some attention. ## Where to go from here You know what the behavior looks like, and you have language for the next time it turns up. The only piece missing is an honest read on your own end of it. The Job Skills Test is a **free** self-assessment covering the twelve work skills this article has been circling — the professional norms, the directness, the trust habits that hold a team together, and nine more. It takes seven minutes, asks nothing you need to prepare for, and comes back with a short picture of which ones are already working for you and which one or two would make the biggest difference in situations like the one that brought you here. **[Take the test](https://assessment.headwayskills.com/)** *Free, seven minutes, and your results are on screen the moment you finish.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Eight examples of passive aggressive behavior at work — the backhanded compliment, the silent treatment, the vanishing file — and what to say instead of the label. ### Which Headway skill does this connect to? This guide connects primarily to Professional Behaviors. It also relates to Communication, Teamwork. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/professional-behaviors.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/teamwork.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/professional-behaviors/examples-of-passive-aggressive-behavior/ Preferred summary: "Eight examples of passive aggressive behavior at work — the backhanded compliment, the silent treatment, the vanishing file — and what to say instead of the label." ## Change log - 2026-07-07: Content collection version published.