Cognitive Bias in Your Own First Draft
Logical fallacies are errors in an argument's structure. Cognitive biases are errors in the thinking that produced it — and because they operate before you write a word, they're much harder to see in your own work. The one-sided draft, the too-tidy conclusion, the objection you never considered: these usually aren't laziness. They're bias doing its quiet work.
The biases that shape a draft
A few show up again and again in writing meant to persuade:
- Confirmation bias — you notice, remember, and cite the evidence that supports your view, and skim past the rest. The result is a draft that feels airtight to you and cherry-picked to everyone else.
- Anchoring — the first figure, framing, or example you encountered sets the terms for everything after it, even when a later fact should have moved you.
- The availability heuristic — the vivid, recent, or memorable example feels representative, so you build a general claim on a single striking case.
- Overconfidence — you state a probable claim as a certain one, and skip the hedging the evidence actually warrants.
You can't argue your way out of your own blind spot. You can only build a process that looks where you won't.
Why your own bias is invisible
Bias is easy to spot in writing you disagree with and nearly impossible in writing you produced, because you already accept the conclusion. Everything that supports it feels like evidence; everything against it feels like an edge case. This is the same mechanism behind confirmation bias — and knowing about it isn't enough to switch it off. You need a method that compensates for it.
How to edit bias out
- Argue the other side first. Before finalizing, write the strongest case against your conclusion. If you can't, you don't understand the issue well enough to write about it yet.
- Count your sources. If every citation points one direction, you've likely gathered confirming evidence and stopped. Go looking for the disconfirming kind.
- Check your certainty language. Underline every "clearly," "obviously," and "always." Each is a place you may have skipped the reasoning because it felt self-evident to you.
- Get an outside read. Someone who doesn't share your conclusion will see the gaps instantly. A tool that reads for bias is the next best thing when no one's around.
Bias and fallacy, together
The two problems compound: a cognitive bias produces a lopsided view, and then a logical fallacy smuggles it into the argument as if it were reasoned. Catching them means editing at both levels — the thinking and the structure. Do that consistently and your writing stops merely expressing what you already believed, and starts making a case a skeptical reader can actually follow.