01Overview
The argument from fallacy (fallacy fallacy) is rejecting a conclusion because the argument offered for it was bad — even when the conclusion itself might be correct. Wrong reasoning; right answer. We discard both.
Design critiques and research readouts are full of imperfect arguments: junior designers citing the wrong heuristic, PMs using bad analytics, stakeholders telling bad stories. The argument from fallacy tempts senior practitioners to dismiss the underlying signal along with the sloppy packaging.
02Detailed explanation
In review rooms:
- A researcher presents a poorly reasoned recommendation that is still directionally correct — and gets ignored because the methodology slide had gaps.
- A teammate argues for accessibility with incorrect legal claims; the team laughs off the accessibility work itself.
- A user's flawed explanation of their behaviour is discarded entirely instead of being unpacked for the valid need beneath it.
Good process separates the quality of reasoning from the quality of the insight. The fallacy collapses them.
03Why it exists
Spotting logical errors is cognitively satisfying — especially for experts. It offers a clean reason to stop listening.
Hierarchy amplifies the effect: senior designers who win on technicality can shut down ideas without engaging with the problem.
Fix the argument if you can. Do not auto-dismiss the conclusion because the argument was weak.
04Effects on users
Users give inaccurate reasons for their behaviour all the time — post-hoc rationalisations, borrowed jargon, confabulated stories. The behaviour is still real even when the explanation is not.
Dismissing user statements because they are logically inconsistent means losing valid needs wrapped in bad narratives.
05Effects on designers & teams
Teams pay a price when the fallacy runs unchecked:
- Critique as performance. Reviews become about winning rhetorical points, not improving outcomes.
- Junior silence. People with good instincts but weak frameworks stop speaking after being "corrected" once.
- Research waste. Valid findings are thrown out with flawed synthesis instead of being reframed.
6Introspective view
Look inward. Teams reject a sound conclusion because the argument for it was flawed, discarding good ideas.
From an introspective perspective, ask how Argument from Fallacy may already be shaping your research, critique, planning, and interpretation — not only what users encounter in the finished interface.
First comp on the wall
In critique, Argument from Fallacy ties later options to whichever direction was shown first — alternatives read as tweaks, not genuine forks. Teams reject a sound conclusion because the argument for it was flawed, discarding good ideas.
The loudest frame wins
Alignment workshops on Argument from Fallacy can converge on whoever articulated a direction first, even when the room never formally agreed. Teams reject a sound conclusion because the argument for it was flawed, discarding good ideas.
Themes that fit the deck
During synthesis, Argument from Fallacy nudges teams toward a tidy narrative — quotes that support the emerging story rise to the top; outliers stay in the spreadsheet. Teams reject a sound conclusion because the argument for it was flawed, discarding good ideas.
Sketches that look familiar
Brainstorms about Argument from Fallacy recycle what the room already knows — competitors, past launches, favourite patterns — rather than stretching into uncomfortable territory. Teams reject a sound conclusion because the argument for it was flawed, discarding good ideas.
07Practical takeaways
- Respond to the claim, not only the logic. Ask: "If they are wrong about why, could they still be right about what?"
- Separate synthesis from recommendation. Bad slides can contain good observations — extract before rejecting.
- Teach better arguments instead of dismissal. Upgrade reasoning rather than ending the conversation.
- Watch expert reflexes. If your first move is "that's a fallacy," your second move should be "what are they noticing?"
- Document the signal. Capture the insight even when you reject the framing — especially in user research.
08Design examples
Wrong law, right problem
A designer cites incorrect WCAG levels while advocating for contrast fixes. The room debates legal minutiae. Shipped contrast still fails users; the valid need got lost in the correction.
Confused explanation
A participant says they "don't trust the cloud" while describing a clear need for offline backup. The note-taker tags the quote as irrational; the offline feature never makes the backlog.
Bad chart, good alert
A PM misreads a chart type but correctly senses churn in a segment. Data team discredits the PM entirely. Two sprints later, the segment churns visibly.
Fallacy bingo
Brainstorm ideas get shot down for sloppy reasoning. Participation drops. Later, a polished deck resurrects the same ideas with better framing — credited to a senior lead.
09Ethical risks
When fallacy policing becomes a power move, quieter voices — often from underrepresented roles — lose influence over outcomes that affect diverse users.
Dismissing user narratives because they are logically messy is still dismissal. The need does not disappear because the story was imperfect.
Self-test: What valid signal did you last reject because the person arguing for it did not make the case cleanly?
10Suggested reading
Suggested reading is temporarily unavailable. Please check back later.