An Analogy With Its Limits
One good analogy, then take it apart yourself
Explain [concept] with an analogy, and state where the analogy breaks. Requirements: 1) one main analogy, mapping which elements of the concept it covers; 2) at least two places where it fails, and the wrong inference each failure produces; 3) one backup analogy that is more accurate from a different angle; 4) a short walkthrough showing where following the main analogy leads you astray.
How to use
An analogy without stated limits stops being a scaffold and becomes the next misconception.
Good for
- You have to explain something abstract to a non-specialist — a client, an interviewer, a relative — and need one line they'll remember
- You understood a concept through an analogy and your judgment drifts on edge cases
Not for
- Precision is required (contract clauses, dosages), where every slip of the analogy becomes a real error
- The listener already has the background and only lacks a rigorous definition, so the analogy adds a layer they must then discard
Example
Input
Explain the difference between memory and disk to a colleague who isn't technical.
What you get
A workable main analogy is desk versus bookshelf: memory is the desk, disk is the shelf. It should flag at least two failures — the desk keeps its contents when the power goes out, and the desk doesn't fetch books by itself, a program has to do it. The bad inference to name is that files on the desktop survive a shutdown, and the counter-and-fridge backup is more accurate on the fetching step.
Common mistakes
- Giving the analogy without the failure points, so the listener files it as a definition and gets the first edge case wrong
- Stacking flashy comparisons (water, highways, the cosmos) until the image is remembered and the mechanism isn't
Try tweaking it like this
- Invert it: 'here's my analogy, tell me where it fails', a decent self-test of whether you actually understand it
- Add 'give me an 8-year-old version and an expert version of the same analogy' for mixed audiences