AI Guides › Claude Mastery

The Difference Between Summarising And Understanding

By Nigel Guy · 2 min read

A good summary is a genuinely seductive thing. You paste in a report, get back four clean paragraphs that read well and cover the obvious points, and it feels like you now understand the document. Often you don't — you understand the summary, which is a different and smaller object, and the gap between the two only shows up later, at the worst possible moment, when someone asks a question the summary didn't cover.

The rule: a summary tells you what the document says; it doesn't tell you whether you could defend, apply, or challenge what's in it — that's a different check, and it's on you to run it.

The mechanism: the Explain-Back Test

After any summary — of a report, a contract, a meeting transcript, a paper — run this before treating the summary as your working understanding:

  1. Ask a question the summary didn't answer. Not "what does this say" again, but something one level more specific: "what would change if X condition weren't true," or "what's the weakest part of this argument." A good summary survives this; a shallow one exposes itself immediately because there's nothing underneath it to draw on.
  2. Ask it to point to where in the source a specific claim comes from. If a claim can't be traced back to a specific passage, that's worth noticing — either it's an inference (fine, but say so) or it's drifted from the source.
  3. Try restating the core point in your own words, out loud or in writing, without looking at the summary. If you can't, you have a summary, not an understanding — and that's the moment to go back to the source material rather than the moment to move on.
  4. Ask what the summary left out and why. Every summary is a compression; a useful one can tell you what got cut, so you can judge whether the cut was safe.

What to skip

Skip demanding an exhaustive line-by-line summary as a substitute for this check — length doesn't fix the underlying issue, since a long summary can be just as shallow as a short one, only slower to read. And skip running the full test on genuinely low-stakes material; save it for anything you'll act on, cite, or be asked about later.

Guardrails

All 751 AI guides · JulieMango plans from £17/mo