Influence & Persuasion Anti-Patterns

Influence and persuasion live on a spectrum from honest argument to manipulation. The frameworks in this topic (Cialdini, Ethos/Pathos/Logos, SPIN, BATNA/ZOPA) are powerful, and they can be misused. These anti-patterns capture the most common failures — both ethical and tactical — that undermine long-term influence in tech and company contexts.

Ethical Anti-Patterns

Manufactured Scarcity

Creating the appearance of a deadline or constraint to pressure a decision that would not otherwise be made. "We need to decide by Friday or we lose the window" — when Friday is arbitrary.

Signals:
  - The deadline cannot be explained in terms of external constraints
  - Skeptics have to accept the urgency on your authority
  - The same "urgent" request reappears weeks later, still urgent

Why it backfires: Sophisticated stakeholders quickly notice patterns of manufactured scarcity and discount future urgency from you.

Fix: Be honest about real timelines. If a decision genuinely can wait, say so. If you want urgency, create real stakes, not false ones.

Citing adoption or agreement that is exaggerated or misrepresented. "Everyone else is using this," when you mean "I know three people at three companies who have evaluated it."

Fix: Cite specific sources you can name. Let the size speak for itself. If adoption is genuinely thin, present the case on its merits — do not inflate.

Borrowed Authority

Invoking an authority figure's view without their knowledge, consent, or actual endorsement. "I was talking to the CTO and they think..."

Fix: If an authority endorses something, they can say so themselves. Paraphrasing them without their sign-off damages your credibility when they find out (and they usually do).

Cherry-Picked Data

Presenting data that supports your view while suppressing data that doesn't. Technically accurate; substantively dishonest.

Fix: Present the full picture. Sophisticated audiences will find the missing data; presenting it yourself is an Ethos move.

Emotion as Cudgel

Weaponizing Pathos — using fear, outrage, or guilt to bypass rational evaluation. "Do you want to be responsible for customer harm?"

Fix: Pathos should illuminate stakes, not coerce. If your argument only works when people are scared, it is not actually a good argument.

False Balance / Straw Man

Presenting alternatives in a deliberately weak form to make your preferred option look superior. Technical: "we could do X (straw man) or Y (my proposal, clearly better)."

Fix: Steelman the alternatives. If your proposal still wins against the strongest version of the alternatives, that is real influence.

Pre-Committed Processes

Running a "fair process" (RFC, committee, decision framework) where the outcome is predetermined. Stakeholders recognize the theater and disengage.

Fix: If you have decided, announce the decision. Do not fake a process. If you genuinely are uncertain, run the process honestly.

Tactical Anti-Patterns

The All-In Opener

Leading with your most extreme position, intending to "negotiate back." Usually signals bad faith and often leads the other side to break off entirely.

Fix: Open with a defensible position that can be adjusted. Keep some room but do not anchor at absurd numbers — sophisticated counterparts reset the baseline to punish the tactic.

Ignoring BATNA

Entering a negotiation without knowing your BATNA. You will accept bad terms because you have nothing to walk to.

Fix: Before any serious negotiation, spend time strengthening your BATNA. Your leverage is your BATNA, not your rhetoric.

The Undiagnosed Pitch

Delivering a solution without understanding the buyer's actual problem. Common with technical evangelists who assume the benefits are obvious.

Fix: Use SPIN. Ask before you tell. Listen twice as long as you speak in discovery.

Pitch Mode

Treating every conversation as a sales opportunity. "Here are 12 reasons to adopt..." without any invitation for the counterpart to engage.

Fix: Conversations, not pitches. Dialogue, not monologue. You are trying to find alignment, not deliver a speech.

Feature-List Persuasion

Arguing a proposal by listing its features rather than by naming the problems it solves or the outcomes it produces.

Weak:  "LaunchDarkly has percentage rollouts, user targeting,
        and A/B testing."
Strong: "LaunchDarkly lets you turn off a bad deploy in 30 seconds
         instead of re-deploying. That's our #1 incident-recovery
         pain."

Fix: Lead with problems solved. Features are support; outcomes are the argument.

The Stacked Ask

Piggybacking additional asks onto a seemingly-agreed item. "Great that we've aligned on X. Also, can we do Y and Z?"

Fix: Make your full ask up front. Stacked asks feel manipulative even when innocent, and they train the other side to scrutinize "agreed" items for hidden asks.

Escalation Warfare

Running to a higher authority when a peer negotiation does not go your way, before exhausting peer-level options.

Fix: Escalate transparently and only after genuine peer attempts. "I've tried X, Y, and Z with [peer]. We are stuck. I'd like your help."

The Passive-Aggressive Deadline

"No pressure, but could we have this by EOD?" The politeness makes the pressure deniable; the pressure is still felt.

Fix: If the deadline is real, name it and the reason. If there is no real deadline, do not invent one.

Stakeholder & Audience Anti-Patterns

The Single-Stakeholder Strategy

Building support with one person in the belief that their endorsement will carry the whole room. Works rarely; fails often when the endorser does not actually lobby for you in the room.

Fix: Map stakeholders explicitly. Build coalition breadth. No single person can usually carry a decision.

Under-Engaging "Keep Informed"

Treating low-power stakeholders as irrelevant until they collectively block adoption. The "Keep Informed" quadrant is where technical veto power often secretly lives.

Fix: Senior engineers, individual PMs, and ICs often have de-facto blocking power even if they are not formal deciders. Engage them as if they matter — because they do.

Over-Engaging "Keep Satisfied"

Dragging low-interest senior stakeholders into details they did not want to be in. Creates unwanted scrutiny and wastes their goodwill.

Fix: Brief on outcomes, not process. High-level updates. Avoid surprises, do not create work.

The Invisible Blocker

A critical stakeholder is not on your map. You get 90% of the way there and then get blocked by someone you did not know existed.

Fix: Before major pushes, ask "who else has an opinion or stake?" to several people outside the core group. The names you do not recognize are the invisible blockers.

Culture-Deaf Persuasion

Using rhetorical moves that work in your culture but do not translate. Direct challenge reads as assertive in one culture and rude in another; indirect suggestion reads as collegial in one and wishy-washy in another.

Fix: Study the rhetorical norms of the audience. When in doubt, ask a trusted local. Persuasion is always culturally situated.

Coalition Anti-Patterns

The Echo Chamber

Building your coalition only from people who already agree with you. When resistance emerges, you are blindsided.

Fix: Actively seek out skeptics. Understand their objections. A coalition that includes some skeptics-turned-supporters is more robust than one of pre-aligned believers.

The Horse-Trading Spiral

Trading favors for support until you have accumulated too many open promises. Eventually you cannot deliver, and the whole coalition collapses.

Fix: Keep horse-trading minimal. Build support on the merits where possible.

The Paper Coalition

People "agree" in private but do not actively support in public. When it comes time to vote or act, they go quiet.

Fix: Before calling the decision, ask for active support, not passive agreement. "Will you speak in favor in the meeting?" is different from "Do you agree?"

Receiver-Side Anti-Patterns

The Default No

Reflexive opposition to any change or new proposal, regardless of merit. Often comes from stakeholders who have been burned before.

Fix (as receiver): Notice when your "no" is reflex rather than reasoned. Separate the messenger from the message. Ask "what would change my mind?"

Fix (as proposer): Build Ethos over time with chronic skeptics. Trust deficit is the real issue; the current proposal is just where it surfaces.

1. Would I be comfortable if my tactics were visible to all stakeholders?
2. Is my ask good for the organization, or good for me at the
   organization's expense?
3. Have I steelmanned the opposition's view?
4. Do I actually know each key stakeholder's BATNA and mine?
5. Have I built Ethos over time, or am I trying to conjure it now?

During and after:

1. Am I adjusting based on what I'm hearing, or just delivering my plan?
2. Are stakeholders feeling persuaded or managed?
3. Would I describe what I just did to a mentor with pride?
4. Can the people I influenced articulate the decision in their own words?
5. Will this move be sustainable, or will it unravel when scrutinized?