Scrolls
5 min read
On this page

Communication Anti-Patterns

Anti-patterns are common communication failures that persist because they feel natural or safe in the moment but consistently produce bad outcomes. Learning to recognize them is as valuable as learning any positive framework. This subtopic catalogs the most common anti-patterns that appear in tech and company contexts.

Why Anti-Patterns Matter

Most communication problems are not caused by lack of skill — they are caused by well-known traps that the communicator walked into unaware. Naming these traps gives you a vocabulary to spot them in yourself and others, and to correct course before the damage accumulates.

The Catalog

Burying the Lede

The most important information appears at the end of the message (or never). Readers bounce before they get there.

Bad:
  "I've been looking at the payment service metrics for the past week
   and noticed some interesting patterns. We've had a few deploys that
   changed behavior, and there was also that incident last Tuesday.
   Anyway, error rates are up 40% since Friday and we should roll back."

Good:
  "Error rates on the payment service are up 40% since Friday.
   Recommending we roll back deploy X. Details below."

Fix: Use BLUF. Lead with the conclusion; justify after.

Wall of Text

One massive paragraph that forces the reader to parse everything or skip it all.

Fix: Break into sections. Use headings, bullets, short paragraphs.
     If it exceeds 5 lines, it needs structure.

Meetings That Should Have Been Email

Sync meetings called for information sharing that could have been written and read asynchronously. Wastes 30-60 person-minutes for 30 seconds of content.

Fix: Before scheduling, ask: "Does this require real-time interaction, or can I just write it?" Default to writing.

Emails That Should Have Been Meetings

The opposite trap: a thorny interpersonal issue that needs tone, nuance, and reading the room gets flattened into written ping-pong that spirals over days.

Fix: If the third back-and-forth does not converge, switch to sync.

Status Theater

Updates that sound informative but contain no actionable signal.

Theater:
  "Making good progress on the migration. Hit a few blockers but
   working through them. On track."

Signal:
  "Migration is 60% done. Blocked on permissions for the DB proxy;
   waiting on SecOps ticket #123 since Tuesday. ETA slipping by 3 days
   unless we escalate."

Fix: Every update should include numbers, risks, and specific asks.

The Consensus Trap

Waiting for everyone to agree before deciding. Nothing moves. Loudest voices win by attrition.

Fix: Use explicit decision frameworks (DACI, RAPID). Name the decider. Document disagree-and-commit.

HIPPO Dominance

Highest-Paid Person's Opinion overrides data or better ideas because no one wants to push back.

Fix: Anonymous input channels for proposals. Written-first culture so ideas are evaluated before the room sees who wrote them.

Jargon Walls

Using internal or technical vocabulary that excludes part of the audience, intentionally or not.

Example:
  "We'll need to bump the SLO for the p99 latency on the auth
   service, because the upstream dependency has cardinality
   issues in their metrics emission."

Translation:
  "The login service is slow for 1% of users. The tool we use to
   measure it has too much data to handle. We need to relax our
   speed targets while we fix the tool."

Fix: Optimize for the least technical person in the audience who matters. Define terms on first use.

Passive Aggression & Vague Blame

"Some people on the team..." / "We need to be more careful..." / "It would be great if..." — criticism without a target or owner.

Fix: Name the behavior, the context, and the person (ideally in private). Use SBI.

Fire-and-Forget Communication

Sending a message, assuming it was read, understood, and agreed with — and being shocked when it was not.

Fix: Close the loop. Confirm receipt for important messages. "Reply with a thumbs-up to confirm" is not beneath you.

The Phantom Asker

Questions with no subject. "Can someone look at this?" in a channel of 50 people. Nobody does.

Fix: Directly tag the person you need. If you do not know who, write: "Not sure who owns this — @team who should I ask?"

Motte and Bailey

Making a strong, controversial claim (the bailey), then retreating to a weaker, defensible version (the motte) when challenged, while still acting on the stronger one.

Fix: State the claim at the strength you actually believe it. If you cannot defend it, do not make it.

Rage-Cloaked Formality

Using overly polite, structured language to mask frustration. The recipient feels the hostility but cannot point to it.

Example:
  "As previously discussed, per my earlier email, and as I believe
   I was clear on, the deliverable was expected Monday."

Reality:
  "You missed the deadline and I am angry."

Fix: If you are angry, wait. If you cannot wait, be direct but respectful: "I am frustrated because we agreed Monday and it is now Wednesday. What happened?"

Information Hoarding

Withholding context, data, or decisions — intentionally or through neglect — creating dependencies on the hoarder.

Fix: Default to sharing. Documentation, broadcast channels, inclusive invites. If you are the only person who knows something important, that is a bug, not a feature.

The Silent Disagreement

Agreeing in the meeting, complaining afterward. Corrosive to team trust and decision quality.

Fix: Create explicit space for disagreement: "Any objections? Last call before we commit." Reward the people who raise concerns, even if you proceed anyway.

Apology Theater

Performative apologies that do not acknowledge specifics or change behavior. "I'm sorry if anyone was offended."

Fix: Apologize for the specific action, acknowledge impact, state the change: "I interrupted you three times in that meeting. That was dismissive. I will catch myself next time."

Meta-Antipatterns

Framework-Shaped Hole

Using a framework as a checklist to feel productive, without actually communicating well. A perfectly formatted RFC that nobody reads or engages with is still a failure.

Over-Communication as Avoidance

Flooding channels with updates, messages, and notifications to appear engaged while avoiding the actual hard conversation that needs to happen.

The Well-Written Lie

Using strong writing craft to make a weak argument sound credible. Form deceiving function.

How to Spot Anti-Patterns in Yourself

Ask these questions after any communication:

1. Would my audience be able to restate my message correctly?
2. Did the communication actually produce the outcome I intended?
3. Did I use the right channel for the stakes?
4. Was I honest about my actual position?
5. Did I close the loop on follow-up?

Consistent "no" answers indicate which anti-patterns are your personal failure modes.

Further Reading

  • Kim Scott — Radical Candor (specifically on vague feedback and silent disagreement)
  • Patrick Lencioni — The Five Dysfunctions of a Team (on trust and constructive conflict)
  • Jerry Weinberg — The Secrets of Consulting (on communication failure modes in professional work)