After reading a passage, it is easy to mistake recall for understanding. Repeating the author’s conclusion is useful, but it mainly demonstrates successful storage and retrieval. The words may be available while the argument remains foreign.
Return from the conclusion to the problem#
One test of understanding is to set the conclusion aside and ask what problem the explanation was designed to solve. Its value lies not only in what it asserts, but also in the tempting alternatives it rules out.
If all we remember is “do this,” a small change in conditions leaves us stranded. If we know why the action works and which causal link matters most, we can derive a new answer when the situation changes.
Rebuild the causal chain#
Useful restatement is not a swap of synonyms. Without looking at the source, try to describe the observed phenomenon, the mechanism that matters, and how that mechanism produces the result.
Words such as “obviously” and “naturally” often hide the weakest step. Asking one more question at those points turns a smooth summary into a testable explanation.
State where the explanation stops working#
An explanation without boundaries easily becomes a slogan. At what scale and over what time span does it apply? Which conditions are essential? What counterexample would force a revision?
Knowing the failure conditions does not weaken an idea. It makes the idea more reliable because we are treating it as a model that can be tested and improved, not as a sentence that must fit everything.
Keep notes that can generate new answers#
A durable reading note can preserve four things: the original problem, the central explanation, the causal chain, and the boundary of application. Add one unresolved question at the end.
Understanding is not moving information into memory. It is gaining the ability to generate the answer again.