Logical Fallacies

LogFall

A practical logical-fallacies reference with clear explanations, usable examples, and teaching tools.

Theory article

Argument Maps for Common Fallacies

Argument maps help because they force reasons to stand where everyone can see them. Once premises, assumptions, and conclusions are drawn out, some fallacies stop looking mysterious and start looking like plumbing failures. Water is being routed somewhere it cannot actually go, and the map makes that harder to miss.

What a map does well

It slows the argument down, separates claims from support, and reveals hidden premises that prose lets sneak around in dark glasses.

What a map does not do

It does not replace judgment. A beautiful map can still represent a weak argument, but at least the weakness becomes inspectable rather than atmospheric.

The basic parts of an argument map

Students do not need elaborate software to learn the essentials.

Conclusion

What is the claim being supported? If that cannot be stated clearly, the map will wobble before the fallacy even arrives.

Stated premises

These are the reasons explicitly offered in the passage. They should be written in simple sentence form, not copied as a tangled paragraph vine.

Hidden assumptions

These are the unspoken bridges the argument needs in order to move from the premises to the conclusion. Fallacies often live here rent-free.

Failure point

Mark the exact arrow, premise, or assumption where the support breaks. This is where the diagnosis becomes more than a label.

Common fallacies become easier to see on a map

Different maps expose different failure points.

Straw man

A map shows that the rebutted claim is not actually the opponent's original conclusion. The attacked node is a replacement mannequin, not the real person. See Straw man argument.

False dilemma

The map reveals a hidden premise that only two options exist. Once that premise is written down, students can test it instead of letting it pass in formalwear. See False dilemma.

Affirming the consequent

The structure becomes stark: If P then Q; Q; therefore P. In prose this may feel plausible. On a map it begins to look like a ladder missing a rung while still expecting applause. See Affirming the consequent.

Correlation errors

A map lets you write the observed association separately from the stronger causal conclusion, making the unsupported jump visible. See Correlation is not causation.

Begging the question

The map often reveals that the supposed support contains the conclusion in paraphrased clothing. Once drawn, the circle looks less majestic and more dizzy.

Red herring

The map shows that a new branch of material is being developed that never reconnects to the original conclusion under dispute. It is a side quest dressed as progress.

How to use maps in class

Mapping works best when it is lightweight and frequent.

Map short passages first

One sentence or one paragraph is enough. Long editorials can wait until students know how to separate branches and assumptions without panic.

Ask for competing maps

Different students will sometimes reconstruct the same argument differently. That disagreement is not a bug; it is the seminar finally doing something interesting.

Pair mapping with repair

Once the failure point is marked, ask students to redraw the map so the conclusion is supported properly or reduced to a narrower, honest form.

Use maps to compare near neighbors

Two arguments can sound alike but differ structurally. A map makes the difference between misrepresentation, diversion, and weak support easier to explain.

Takeaway

Argument maps do not replace logic; they make logic visible enough to teach.

If students can draw where the support is supposed to go, they become far better at seeing where it actually fails. That is why maps are such useful companions to fallacy study.

References and further reading

Sources that ground the article or push the discussion further.