The Logical Fallacies Field Guide

Why this matters

A logical fallacy is a move that feels like an argument but doesn't actually support its conclusion. They matter to advocates for two opposite reasons. First, the opposition will use them — because fallacies are persuasive even though they're invalid, which is exactly why they persist — and if you can spot and name them, you can defuse them. Second, and more important, you will be tempted to use them, because they're easy and they work in the short term, and every time you do, you trade a piece of the credibility that is an ordinary advocate's scarcest asset. This module is a field guide: the six you'll actually encounter, how to catch them, and how to stay clean.

The six you'll actually meet

1. Straw man. Misrepresenting the other side's position as a weaker or more extreme version, then knocking down the fake instead of the real one. "So you're saying we should just let anyone build anything anywhere." You didn't say that. The straw man is the most common fallacy in live advocacy, because it's tempting to argue against the easy version. Spot it: your position comes back to you distorted into something more extreme. Name it: "That's not what I'm asking for — let me restate what I actually proposed," then say the real thing plainly. Avoid it: state your opponent's position so fairly they'd agree with your summary, then respond. Steelman, never straw man — it's both more honest and more persuasive, because beating the real argument is impressive and beating a fake one is transparent.

2. False dichotomy. Presenting two options when more exist. "Either we approve this development or the town dies economically." "You're either with the kids or with the budget." Advocacy runs on false dichotomies because they're clarifying and dramatic. Spot it: only two doors are offered, and both are extreme. Name it: "That's not the only choice — there's a third option, which is what I'm actually proposing." Avoid it: watch your own "either/or" framings; if your whole case depends on the audience believing there are only two possibilities, check whether that's true or just convenient.

3. Slippery slope. Claiming one step leads inevitably to a distant, dire outcome, with no evidence for the chain. "If we approve one ADU, next it's apartment towers, then the whole neighborhood is gone." The slope is only a fallacy when the chain is asserted, not shown — sometimes step A really does lead to step B, and saying so is fine if you can demonstrate the mechanism. Spot it: a small proposal is argued against by its imagined catastrophic end-state. Name it: "That skips a lot of steps — what's actually in front of you is one garage conversion, decided on its own merits." Avoid it: the most tempting fallacy for passionate advocates, because you genuinely fear the slope. If you can't show the mechanism from here to the dire end, don't argue the end — argue the thing actually on the table.

4. Ad hominem. Attacking the person instead of their argument. "Of course the developer's consultant says it's safe." "She doesn't even live in this district." Spot it: the response is about who's speaking, not what they said. Name it: "Whether or not I live here, the traffic number is either right or it isn't — let's look at it." Avoid it: this is the one that feels most justified in a heated fight, because the other side often is acting in bad faith. Name the bad faith if it's relevant to their reliability, but never let it replace answering the argument — an argument from a person you dislike can still be correct, and dodging it by attacking them tells the room you couldn't answer it.

5. Appeal to (false) authority. Citing an authority who isn't actually an expert on the question, or treating an expert's opinion as beyond challenge. "The city engineer signed off, so it's fine" — when the engineer assessed structural safety, not the traffic question you're raising. Spot it: an authority is invoked to end a discussion they're not actually expert in. Name it: "The engineer's sign-off was on the structure — no one has assessed the school-hours traffic, which is my point." Avoid it: cite authorities for what they actually studied, and don't inflate a friendly expert's opinion into settled fact.

6. Whataboutism (tu quoque). Deflecting a point by pointing at a different problem or the accuser's own conduct. "You're worried about our parking? What about the mess the last council made?" Spot it: your point is answered with a change of subject to someone else's fault. Name it: "That may be a real problem too, and we can talk about it — but it doesn't change the parking math on this proposal." Avoid it: when your case is weak on a point, the urge to point elsewhere is strong. Resist it; it reads as an admission you can't answer the actual point.

Naming without sounding like a robot

Here's the practical craft: you rarely want to say the fallacy's name in a real room. "That's a straw man" and "that's an ad hominem" sound like a debate-club reflex and often alienate the exact people you're trying to reach — it feels like you're scoring points instead of solving a problem. Instead, name the move in plain language and correct it: "That's not what I said — here's what I actually proposed." "That skips some steps." "Whether I live here or not, the number's the number." You get all the value of catching the fallacy and none of the smugness. Save the technical vocabulary for your own preparation; use plain re-framing in the room.

The self-audit is the point

You will be more tempted by these than your opponents are, because you care, and caring makes the slippery slope feel true and the false dichotomy feel clarifying and the ad hominem feel deserved. The discipline that separates a durable advocate from a burned-out one is the habit of auditing your own arguments for these before you deliver them. Read your strongest case and ask: Am I steelmanning or strawmanning their side? Is my "either/or" real? Can I actually show this slope, or am I just afraid of it? Am I answering the argument or attacking the arguer? An argument cleaned of fallacies is not weaker — it's the only kind that survives a smart opponent and doesn't cost you your credibility when someone catches the gap.

A warning

Knowing the fallacies creates a specific temptation: to treat every disagreement as a fallacy to be named, weaponizing the list to dodge real points. Not every simplification is a false dichotomy; not every strong claim about consequences is a slippery slope; not every mention of someone's interest is ad hominem. Used as a bludgeon, this vocabulary makes you the insufferable person in the room who wins the technical point and loses everyone's goodwill. The field guide is for keeping reasoning honest — theirs and especially yours — not for winning by accusation.

Exercise

Spot three real fallacies in the wild, then audit your own argument for one and fix it. The full prompt is below. The self-audit is the assignment that matters.

What's next

You've sharpened narrative and argument. The tier's last skill-instrument returns to the audience — and past the standard archetypes to the ones you have to build yourself. Craft 3.8: Build Your Own Archetype teaches the custom-profiling method for the audience the Five Archetypes don't cover, using Erick's signature "Country Raised" profile as the worked example.