Communication PatternPractical Playbook

How to deal with passive-aggressive coworkers

Passive-aggressive coworkers express resistance indirectly: missed commitments, sarcasm, or backhanded remarks instead of direct disagreement. This pattern undermines collaboration, creates mistrust, and inflates coordination costs. Practical responses focus on clarifying expectations, one-on-one feedback, and changes to team processes rather than blame.

3 min readUpdated May 23, 2026Category: Communication & Conflict
Illustration: How to deal with passive-aggressive coworkers

What passive-aggressive behavior looks like at work

Common on-the-job behaviors include:

  • Silent treatment or brief, clipped replies that stall conversations
  • Backhanded compliments or sarcasm in meetings
  • Repeatedly missing deadlines while insisting there was no problem
  • “Forgetting” to include someone in a thread or pass along needed documents
  • Agreeing in a meeting and then not following through
  • Overly indirect emails that signal annoyance instead of naming the issue

These actions share a core pattern: the stated message and the actual behavior conflict. That inconsistency creates ambiguity, so colleagues waste time guessing intent, double-checking work, or compensating for missed tasks.

How the pattern gets reinforced

These causes often interact. For example, a team with unclear accountability and a culture that downplays feedback creates low-risk conditions for passive-aggressive moves. Over time those behaviors become a default coping strategy rather than an occasional lapse.

**Fear of confrontation:** people avoid direct conflict to reduce immediate discomfort.

**Perceived power imbalance:** those low in formal influence may use indirect resistance to push back.

**Reward structures that tolerate outcome gaps:** when missed commitments carry few consequences, the behavior persists.

**Poor communication norms:** teams that normalize vague language encourage indirect signals.

**Emotional regulation style:** some employees lack practice giving or receiving candid feedback.

How to respond day-to-day: practical steps

  • Start with clear documentation of specific incidents (dates, what was said, what happened).
  • Use fact-focused, private conversations: name the behaviour (“I noticed the report arrived late without heads-up”) rather than attributing motive.
  • Ask clarifying questions: “What happened that prevented the delivery?” This invites information instead of escalation.
  • Set firm, testable expectations: deadlines, deliverables, and how updates should be communicated.
  • Offer simple accountability mechanisms: shared checklists, short status updates, or pairing on tasks.
  • Follow up promptly if the pattern repeats; escalate to a manager or HR only after you’ve tried direct but documented steps.

Start with low-escalation options. Many situations resolve when ambiguity is removed and the person sees that missed actions will be noticed and addressed. If the pattern continues, switch to short, documented follow-ups and clearer consequences.

A workplace example and an edge case

A quick workplace scenario

Maria and Jonah collaborate on a client deck. Jonah says in the meeting, “I’ll handle slides 4–6,” then submits slides with minimal content and no notes on time. When Maria follows up, Jonah replies, “I thought you had asked me to leave them for you.”

How Maria can respond: clarify the agreed assignment in a private, factual message; request a short catch-up to align; set an explicit due time and a shared draft link; ask whether Jonah needs support or a role adjustment.

Edge case — deliberate resistance vs. mismatched capacity: sometimes the behavior is an intentional pushback; other times it stems from overload, unclear role boundaries, or different communication preferences. The initial response—curiosity and evidence-gathering—helps distinguish motive from capacity, which determines the corrective step.

Common confusions and closely related patterns

  • Passive-aggression vs. procrastination: procrastination is often about time management; passive-aggression carries an interpersonal signal of resistance.
  • Passive-aggression vs. poor skill fit: missing work due to lack of ability is a capability issue, not covert hostility.
  • Passive-aggression vs. cultural indirectness: some cultures prefer indirect speech; context matters before labeling behavior as problematic.
  • Passive-aggression vs. burnout or overload: repeated missed commitments can be a stress signal, not a deliberate tactic.

Distinguishing among these requires looking for patterns over time and correlating behaviors with situational factors (workload spikes, unclear responsibilities, or team changes). Quick judgments increase the risk of mislabeling and worsening relations.

Questions worth asking before escalating

  • Was the expectation explicit and documented? If not, clarify and record it.
  • Is there a recent change (role, workload, personal stressor) that could explain behavior?
  • Have I used a non-accusatory, private approach to check in?
  • What small process change could reduce ambiguity (shared task tracker, brief stand-up updates)?
  • If it continues, what specific outcome will prompt a formal step, and what will that step be?

Use these questions to convert frustration into a clear diagnosis and action plan. A measured approach protects team relationships and increases the chance of correcting the behavior rather than escalating needless conflict.

Related topics worth exploring

These suggestions are picked from nearby themes and article context, not just a flat alphabetical list.

Open category hub →

Passive-aggressive email patterns and fixes

How to spot, interpret, and reduce passive-aggressive email patterns at work—practical examples, why they happen, and step-by-step fixes teams can use.

Communication & Conflict

Meeting norms to prevent passive resistance and hidden obstruction

Practical meeting norms to surface hidden objections and stop quiet sabotage—how to spot passive resistance, redesign rituals, and reduce late-stage blocking in team decisions.

Communication & Conflict

Request Framing

How the wording, context, and implied expectations around a work ask shape responses—and practical ways to reframe requests to reduce friction.

Communication & Conflict

Feedback aversion

Feedback aversion is the avoidance of candid performance conversations at work; it shows up as silence, shallow reviews, and missed learning—practical fixes for leaders.

Communication & Conflict

Tacit norm conflicts

When unspoken workplace rules clash, teamwork stalls. Learn how tacit norm conflicts show up in meetings, why they form, and practical steps teams can use to surface and resolve them.

Communication & Conflict

Message Friction

Message friction is the extra effort communications require—unclear asks, wrong channels, or missing ownership—that slows decisions. Learn signs, causes, and practical fixes for work.

Communication & Conflict
Browse by letter