F001 • Formal - Propositional Logic
Also known as: Converse Error, Fallacy of the Converse
The conditional only guarantees direction forward, not backward.
We hear "if A then B" and quietly assume it works in reverse -- that seeing B means A must be true. It is a natural leap. Our minds are built to run stories forward and then retrace them, and most of the time that works. But in logic, the arrow only points one way.
Loading examples...
Pattern: If P then Q; observe Q; conclude P
Terms:
P = the proposed cause or conditionQ = the observed outcomeSteps:
P happens, then Q followsQ is presentP must have occurredIn everyday life, running the story backward usually gets us close enough. If the street is wet, rain is a perfectly reasonable guess. That heuristic -- seeing a result and jumping to its most likely cause -- is one of the most useful shortcuts we have. It becomes a problem when we stop noticing that it is a shortcut. The conditional "if P then Q" only guarantees Q when P is true; it says nothing about what made Q true. The street could be wet because of a sprinkler, a burst pipe, or a cleaning crew. When we treat the backward inference as certain rather than as a guess worth checking, we have mistaken a useful habit for a logical guarantee.
| In everyday reasoning, we often have background knowledge that makes the backward inference reliable. If you know the only thing that makes your smoke detector go off is actual smoke, then hearing the alarm and concluding there is smoke is perfectly reasonable -- you have turned an inclusive conditional into an exclusive one with context. |
| When you are generating hypotheses rather than drawing conclusions, running the story backward is exactly the right move. The problem is not in asking "could A explain B?" but in stopping there and treating the question as an answer. |
| You might notice yourself feeling certain about a cause the moment you see a result -- that speed is the tell. |
| Watch for the pattern: you know "if A then B" and you have just observed B. If your mind has already landed on A without pausing, that is worth a second look. |
| Ask yourself: could anything else have produced this result? If the answer is yes, you are working with a guess, not a proof. |
| Notice when you feel the pull of a tidy story -- the effect showed up, so the cause must have too. That tidiness is the heuristic doing its job, but it is not the same as certainty. |
| Pay attention to the word "must" in your own thinking. "It must have rained" is doing more work than "it probably rained," and the gap between those two is exactly where this pattern lives. |
| Confusing this with modus ponens, which is valid: if P then Q, P is true, therefore Q. Affirming the consequent runs the other direction -- starting from Q and concluding P -- which is where the error lives. |
| Dismissing every backward inference as wrong. In practice, running the story backward is often a reasonable starting point. The mistake is not in making the guess but in forgetting that it is a guess. |
| Missing cases where additional context actually does make the backward inference reliable. If you know rain is the only possible cause of wet streets in a given situation, the inference is fine. The fallacy is about assuming that exclusivity without checking. |
| Affirming the Consequent |
|---|
| Inferring the truth of the antecedent from the truth of the consequent in a conditional statement. |
| The consequent can be true for reasons other than the antecedent being true. The conditional only guarantees Q when P is true, not vice versa. |
Hover to see definition, click to view full details