Elaboration: explain and connect#

Here’s a small experiment. Read this fact: the hungry rat ran down the maze faster. Now read this one: the hungry rat ran down the maze faster—because it had learned the food was at the end. Same sentence, almost. One extra clause. But you will remember the second version far better, and the reason is the whole subject of this page.

The bare fact gave your memory nothing to grip. The second version handed you a why, and your brain did something with it—it connected “hungry” to “food” to “ran faster” into a little chain of sense. That act of connecting is elaboration, and it is one of the most reliable ways to turn a fact you’ve just met into one you actually keep. The good news is you don’t need anyone to add the “because” for you. You can do it yourself, on purpose, with nothing but a couple of questions—and that’s the skill I want to give you here.

Why explaining beats memorising#

When you try to memorise something flat—repeat it, stare at it, highlight it—you are treating your memory like a bucket you pour facts into. But memory isn’t a bucket. It’s a web. A new fact survives in proportion to how many threads connect it to things you already know. The more you weave it in, the more routes there are to find it again later.

Elaboration is the deliberate weaving. Instead of asking “what does this say?” you ask “why is this true?” and “how does this fit with what I already know?” Those questions force you to go and find the connections—to retrieve related ideas, line them up against the new one, and build the link. That retrieval-and-construction is real cognitive work, the effortful kind that lays down durable memory rather than the smooth, forgettable kind you get from re-reading. (If that trade—harder now, better later—sounds familiar, it’s the same engine behind desirable difficulties .)

There’s a bonus. When you genuinely explain something, you bump into the bits you can’t explain. The gap reveals itself. You discover, mid-sentence, that you don’t actually know why the rule holds—and now you know exactly what to go back and study. Passive re-reading hides those gaps behind a comfortable feeling of familiarity. Explaining drags them into the light.

Two questions that do the work#

Researchers have boiled the most-studied versions of this down to two simple moves. You don’t need both at once; reach for whichever fits the moment.

Elaborative interrogation—ask “why?” When a fact asserts something, challenge it: Why would that be true? Why this and not the opposite? Reading that veins carry blood back to the heart? Ask why veins and not arteries, and you have to dredge up what arteries do, which cements both. The trick is most powerful when you already know a little about the topic—you need some existing knowledge to connect to. Met with something totally foreign, your “why?” comes up empty, so build a little groundwork first.
Self-explanation—narrate your own thinking. As you work through material or a worked example, explain each step to yourself, out loud or on paper: What’s happening here? Why did they do that step? How does this line follow from the last one? How does this connect to the thing I learned yesterday? You’re not summarising what the page says—you’re generating the reasoning that links it together. This works on procedures and problem-solving especially well, where the “why this step” is exactly the knowledge you’re trying to build.

Notice both are just talking to yourself with intent. No apps, no materials, no setup. That’s the beauty of elaboration—it costs nothing but the willingness to stop and ask.

Make it concrete#

Prompts you can keep on a sticky note and aim at almost anything you’re studying:

Why is this true? What makes it work the way it does?
How does this connect to what I already know? What does it remind me of?
How is this different from the thing next to it that looks similar?
What’s a concrete example of this from my own life or work?
Could I explain this to a friend with no notes in front of me? Where do I stumble?
What would happen if this weren’t true—what breaks?

A few honest notes so you use this well. Generate, don’t just receive. Being handed a tidy explanation helps far less than struggling to build your own—the effort is the point, so don’t peek too soon. Watch your accuracy. A confident but wrong self-explanation can stick just as well as a right one, so check your reasoning against the source once you’ve made the attempt. And lean on what you know. Elaboration thrives on prior knowledge; the richer the web you’re connecting to, the more places the new fact can anchor. With a brand-new topic, get a toehold of basics first, then let the “why?” questions loose.

The takeaway#

Don’t swallow facts whole. The moment you meet something worth keeping, stop and ask why it’s true and how it links to what you already know, then say the answer in your own words. Those few seconds of explaining—done by you, not for you—are what move a fact from “I just read that” to “I understand that.” It’s the cheapest upgrade in this whole manual: no tools, no cost, just two questions and the discipline to actually ask them.