How the right comparison does the work of three paragraphs — and how to know when it quietly lies.
Lesson 2 of The Art of Being Understood · see all five lessons →
Read each part, then pause for the questions. The whole idea turns on a single, beautiful, wrong picture.
In 1911, Ernest Rutherford proposed a model of the atom that almost everyone alive has since carried around in their head: a dense little nucleus at the centre, with electrons sweeping around it in orbits — a tiny solar system, the sun and its planets shrunk to the scale of the impossibly small. It was an extraordinary gift. The atom is unpicturable: too small to see, too strange to intuit. And here was a picture anyone could hold. Suddenly the invisible had a shape.
The model spread because it worked as a way in. A child could draw it. A textbook could print it. A whole century of imagery — the swirling rings, the orbiting dots — descends from that one comparison. It let millions of people feel they understood something they had no other way to grasp.
There was just one difficulty. As a picture of what an atom actually is, it is wrong. Electrons are not little planets. They do not travel in neat orbits. The real picture — fuzzy clouds of probability, where an electron is best described as a smear of likelihood rather than a moving dot — is far stranger, and far harder to draw. The solar-system atom is not a simplified truth. It is, strictly, a falsehood that happens to be useful.
An analogy works by mapping. It takes something the listener already understands — the source — and lays its structure over something they do not — the target. "The atom is like a solar system" hands you a ready-made set of relationships: a heavy thing at the centre, lighter things going around it, a force holding them in place. You don't have to build that structure from scratch; you already own it from the sky. The analogy simply lends it out. That is why a single good comparison can do the work of three paragraphs: it imports a whole frame at once, and understanding arrives almost instantly.
But every analogy does two things at the same time, and they pull in opposite directions. It reveals — it lights up the features the source and target share. And it conceals — it pushes into shadow every feature they do not share. The solar-system atom reveals "centre plus orbiting satellites" and conceals the quantum strangeness underneath. You cannot have the revealing without the concealing. They are the same act seen from two sides.
An analogy goes wrong in three recognisable ways. First, it can leak: it holds for a while, then breaks down the moment you push it too far. "The atom is a solar system" leaks the instant you ask why the electron doesn't spiral into the nucleus the way a planet, losing energy, would fall into the sun. Push it one step past its limit and it spills falsehood. Second, it can map the wrong feature: the source and target really are alike, but not in the way that matters — you compared the colour when the point was the shape. Third, and most seductive, it can flatter but mislead: it feels so apt, so satisfying, that it shuts down thought rather than opening it. The pleasure of the comparison gets mistaken for the truth of it.
So the skill has two halves, and the second is the one most people skip. The first half is building an apt analogy — finding the source that maps the feature that matters. The second half is naming, out loud, exactly where it breaks down — drawing the line past which the comparison no longer holds. An analogy with its limit named is a tool. An analogy without one is a trap, and the cleverer it is, the better it hides.
The vocabulary of comparison. These are the words you need to talk about analogies — to build them, judge them, and say precisely where they fail. Tap each card for a definition and a usable example.
One idea, told three ways. Notice how the flat version informs but doesn't land, the leaky one lands but lies, and only the third both lands and stays honest.
| Version | Explaining "the immune system builds memory" |
|---|---|
| Flat / literal | "After infection, specific lymphocytes persist and enable a faster secondary response upon re-exposure to the same antigen." (Accurate. Lands on no one.) |
| Leaky analogy | "Your immune system remembers the virus, just like you remember a face you've seen before." (Vivid — but it smuggles in a conscious, perfect "memory" the body doesn't have.) |
| Apt — with its limit named | "Think of it as a wanted poster the body keeps on file: next time that exact intruder shows up, recognition is instant. Where the comparison breaks down is that there's no clerk reading it — it's chemistry, not a memory you could ever recall." |
These are the precision tools of a C2 communicator: not just reaching for a comparison, but choosing the right one, stress-testing it, and knowing when to drop it. Try each before you reveal the model answers.
Before you offer a comparison, finish this sentence silently: "I'm saying X is like Y in that…". The "in that" is the whole game. Two things can resemble each other in a dozen ways; only one of them is the point. For each pair, name the single feature that should map.
1. "An electrical circuit is like water in pipes" — the feature that maps is:
2. "A vaccine is like a wanted poster" — the feature that maps is:
3. "Compound interest is like a snowball rolling downhill" — the feature that maps is:
1. …in that pressure drives flow against resistance (voltage = pressure, current = flow, resistance = a narrow pipe). NOT in that electricity is wet or fills a container.
2. …in that it lets the body recognise a specific threat instantly next time. NOT in that it is printed, paper, or seen with eyes.
3. …in that growth feeds on itself, so it accelerates the bigger it gets. NOT in that it is cold, white, or eventually melts.
The move: say the "in that" out loud first. If you can't finish it cleanly, the analogy isn't ready.
A handful of frames carry the mapping for you. Keep them ready: "X is to Y what A is to B", "much as…", "think of it as…", "it's the equivalent of…". Complete each frame for the target idea given.
1. "An enzyme is to its molecule what a is to a ."
2. "Much as , a country's central bank cools an overheating economy."
3. "DNA — think of it as ."
1. "…what a key is to a lock." (The shape has to fit; the wrong key does nothing.)
2. "Much as a thermostat eases off the heating once a room is warm enough, a central bank cools an overheating economy."
3. "…think of it as a recipe written in four letters — instructions, not the dish itself."
The move: the frame does the grammatical work, so you can spend your attention on choosing the source.
The honest move, and the one most people skip. Push your own analogy until it leaks, then announce the leak before your listener finds it. The phrase "the analogy holds up to here, but breaks when…" is worth memorising. For each comparison, name where it breaks down.
1. "The brain is like a computer." Breaks down when:
2. "Running a country is like running a household budget." Breaks down when:
1. "…breaks down when you remember the brain has no separate hardware and software, rewires itself as it runs, and doesn't store memories as exact files. The map is 'input → processing → output', and not much further."
2. "…breaks down when you remember a country issues its own currency, borrows on completely different terms, and can't be grounded for a month. A household can't print money; a state can. That's not a detail — it's the whole disanalogy."
The move: naming the limit doesn't weaken your explanation — it's what makes it trustworthy.
The best source domain is one the listener has physically lived. Don't explain one abstraction with another; reach for the everyday — the kitchen, the body, a journey, money, weather. Replace each abstract source with a lived one.
1. Instead of "like a feedback loop in a dynamical system", try a lived source:
2. Instead of "like the allocation of finite computational resources", try:
1. "…like a microphone held too close to its speaker — the squeal feeds itself and grows." / "…like a thermostat fighting an open window."
2. "…like a single pair of hands in a busy kitchen: start a third pan and something burns." / "…like a household with one wallet and three bills due."
The move: if your source is itself abstract, you haven't explained anything — you've just moved the difficulty.
Some analogies reward extending: you can ride them through several points before they tire. Others should be dropped the instant they've done their one job, before they start lying. The skill is sensing which is which — and being willing to say "the comparison ends there" rather than forcing it on. Decide: extend or abandon?
1. "Electricity is like water in pipes" — to explain a capacitor (a store of charge)?
2. "Evolution is like a designer choosing the best parts" — to explain the eye?
1. Extend. A capacitor maps neatly onto a flexible tank that fills and discharges — the water analogy keeps paying off, so ride it.
2. Abandon (or use only with a loud warning). "Designer" smuggles in intention and foresight, which is the one thing evolution lacks — it flatters but misleads. Better: "much as wind shapes a dune, with no plan at all."
The move: ask whether the next step of the analogy still tells the truth. If it doesn't, stop — and say so.
Here is one genuinely hard idea — encryption — explained twice. Read the flat version, then watch a single comparison do the heavy lifting, limit and all.
"Asymmetric encryption uses a mathematically linked key pair. The public key, freely distributed, performs an operation that only the corresponding private key can reverse, owing to the computational intractability of factoring the product of two large primes. Data encrypted under the public key is therefore recoverable solely by the holder of the private key."
"Think of it as an open padlock. (frame) I hand out thousands of open padlocks — anyone can have one — but I keep the only key. (lived source) You want to send me something secret? Put it in a box, click one of my padlocks shut, and post it. Now nobody can open it, not even you — because only my key fits. (maps the right feature: easy to lock, impossible to unlock without the key.) That's the whole trick: locking is public, unlocking is private. (the key feature, named) Where the comparison breaks down is that real padlocks could be picked or smashed; this one rests on a sum so hard that every computer on Earth working together couldn't force it in any useful time. So it's a padlock — just an unpickable one made of arithmetic. (limit named, then the disanalogy turned into the punchline.)"
Same idea. The padlock didn't dumb it down — it gave the listener somewhere to stand, then told them exactly how far the floor extends.
Now move to the last tab. Everything above is about to be tested out loud.
Do all four, in order. The first warms up the idea; the rest put the toolkit under pressure. The timer is there to stop you escaping into vagueness — fill the time with precision instead.
Before anything else, explain in your own words how analogies actually work — and why they both help and mislead. Cover the mapping of a source onto a target, the way a comparison reveals and conceals at the same time, and the three ways an analogy can lie.
Use at least five of the Key Language terms (to map onto, source / target domain, to leak, apt, figurative, false equivalence, simile, metaphor…) — and notice whether you reach for a comparison to explain comparisons.
Take a genuinely difficult idea from a field you know well. Build a working analogy for it: choose a lived source, map the feature that matters, and deliver it cleanly using one of the comparison frames.
Then — and this is the half that counts — name exactly where it breaks down. Push your own comparison until it leaks, and say the line out loud: "the analogy holds up to here, but breaks when…". Leave your listener with the tool and the warning label.
Take one abstract term — pick anything: inflation, entropy, a recession, immunity, a market, a habit. Offer three different analogies for it in quick succession, from three different source domains (say, the body, the kitchen, and money).
Then choose the best one and justify it: which maps the feature that matters, and which merely flatters? Speed is the point — fluency under a little pressure.