Explaining with Analogies and Examples
Use concrete examples and well-chosen analogies to make abstract ideas clear, and learn to spot where every analogy breaks down.
Communication & Argumentation · Lesson 2
Use concrete examples and well-chosen analogies to make abstract ideas clear, and learn to spot where every analogy breaks down.
Abstract statements are hard to hold onto. Tell someone that a system "degrades gracefully under load" and the words slide past. Show them a staircase that keeps working when the elevator fails, and the idea suddenly has a shape they can picture. Concrete examples and analogies are the bridges that carry an abstract idea across into a listener's existing understanding.
But the same power that makes an analogy vivid can also mislead. Every analogy matches its target in some ways and departs from it in others. A well-chosen one highlights exactly the features that matter. A careless one imports features that do not belong, and the listener walks away confident and wrong. Learning to explain with examples means learning both how to build the bridge and where it ends.
Cognitive science and educational research broadly support the idea that concrete, familiar material is easier to grasp and recall than abstract statements, though the size of the effect depends on the learner and the task. A concrete example gives the mind something specific to attach to: a picture, a story, a case it can turn over. The Heath brothers make concreteness one of their central principles in "Made to Stick," arguing that abstract ideas become memorable when they are tied to something you can see and touch.
An analogy borrows structure from something the listener already understands, the source, and maps it onto the new idea, the target. When you say an atom is "like a tiny solar system," the source is the solar system and the target is the atom. The analogy works to the extent that the important relationships line up: small things orbiting a central mass. Choosing a good analogy means asking which features of the source you want to carry over, and whether the listener actually knows the source well.
No analogy is a perfect copy of its target, or it would simply be the thing itself. The atom-as-solar-system picture breaks down badly at the level of modern physics, where electrons do not follow neat planetary orbits. This does not make the analogy useless, but it does mean you must know its edge. The skill is to use an analogy for the features that map and to signal, out loud, where it stops being trustworthy.
Suppose you want to explain how a firewall works to someone non-technical. The abstract version, "it filters inbound and outbound network traffic according to a rule set," lands weakly. A concrete analogy lands better: a firewall is like a security guard at a building's entrance who checks each person against a list and only lets through those who are allowed. This maps the key relationship, selective admission based on rules, onto something familiar. Then you extend with a concrete example: the guard is told to turn away anyone not on today's visitor list, just as a firewall blocks connections that do not match its allowed rules. Familiar source, clear mapping, specific case.
Now watch the same analogy mislead. A listener might infer that, like a human guard, the firewall uses judgment, notices suspicious behavior, or gets tired and makes mistakes. None of that maps: a basic firewall applies fixed rules mechanically and notices nothing outside them. If you do not mark this edge, the listener over-extends the analogy and forms a false picture of what the firewall can protect against. The failure is not that the analogy was bad, but that its limits went unsignaled.
In their 2007 book "Made to Stick," Chip and Dan Heath identify concreteness as one of six qualities that make ideas memorable, alongside simplicity, unexpectedness, credibility, emotion, and stories. They argue that abstract language is the natural default of experts and a frequent cause of forgettable communication, and that concrete images and examples are what let an idea stick in memory and transfer between people.
The Heaths draw on a wide base of examples rather than a single controlled experiment, so their book is best read as a well-argued synthesis rather than a laboratory proof. Their core claim, that concreteness aids understanding and memory, is broadly consistent with findings in cognitive science, though researchers continue to study exactly when and how strongly the effect holds. Treated with that hedge, the principle is a reliable guide: when an explanation is not landing, one of the most dependable fixes is to make it more concrete.
Take an analogy you use often, such as "the brain is like a computer." List three ways the source and target genuinely map, then three ways they do not. Notice how the honest limits are often the most interesting part. Practice saying the edge out loud: "This comparison holds for storage and retrieval, but it breaks down because brains are not programmed and do not separate hardware from software."
Think Like a Maester: A good analogy is a bridge, not a home, so lead your listener across it and then tell them plainly where it ends.
Concrete examples and analogies make abstract ideas graspable by tying them to things a listener already understands. An analogy maps structure from a familiar source onto a new target, and it works to the degree that the important relationships line up. The evidence from cognitive science and the argument in "Made to Stick" both support concreteness as a dependable aid to understanding and memory, read with the honest hedge that the effect's exact size depends on the situation. Because every analogy eventually breaks down, the mature skill is to use it for the features that map, name its limits out loud, and never mistake a vivid comparison for proof.
Mark this lesson complete to track your progress.