Productivity
Reading More With AI Without Losing What You Read
By Jim Vernon, Editor, AI Intelligence International · Published 19 February 2026 · Reviewed against our editorial standards · About the author
Summaries let you cover far more material and remember much less of it. That trade is fine for information you only need once and expensive for anything you are trying to learn.
This article sets out when to summarise, when to read properly, and the small habits that keep comprehension intact while volume rises.
Key takeaways
- Why summaries weaken memory: Memory is built by effortful processing.
- When summarising is the right call: Deciding whether to read something at all.
- When to read properly: Anything you intend to build on.
- Habits that preserve comprehension: Write one sentence in your own words before reading any summary.
Why summaries weaken memory
Memory is built by effortful processing. A summary removes the effort, which is precisely the ingredient that made the reading stick.
Summaries also strip the structure of an argument down to its conclusions. Conclusions without the reasoning are hard to apply to a case that differs slightly from the original.
The result is a familiar sensation: recognising a topic without being able to say anything specific about it. That is recognition, not knowledge.
When summarising is the right call
Deciding whether to read something at all. A short summary is an excellent filter and costs almost nothing.
Extracting a specific fact from a document you will never need again — a policy detail, a figure, a date.
Catching up on a long thread or report where you need the current state rather than the history.
When to read properly
Anything you intend to build on. Foundational material read via summary produces confident misunderstanding that surfaces months later.
Anything where the argument matters as much as the conclusion — analysis, criticism, technical reasoning. The value is in how the author got there.
Anything you plan to disagree with in public. Arguing against a summary is how people embarrass themselves.
Habits that preserve comprehension
Write one sentence in your own words before reading any summary. It forces retrieval and takes ten seconds.
Ask the assistant questions about the text rather than for a recap. Answering questions requires the text; recaps require nothing from you.
Convert anything you want to retain into a few question-and-answer pairs and revisit them a week later. Spaced retrieval remains the highest-return study habit ever measured, and generation makes producing the cards trivial.
Watch the accuracy of the summary itself
Summaries invert meaning more often than people assume, particularly with hedged claims, negations and conditional statements. A paper saying an effect was not observed under certain conditions is routinely flattened into the opposite.
Spot-check one specific claim against the source each time. It takes under a minute and calibrates how much you can trust the rest.
Never quote from a summary. Quote from the original or do not quote.
A workable weekly reading system
Summarise everything in your queue, then choose two items to read properly. The summaries do the filtering; the two do the learning.
Keep a short list of claims you now believe and where they came from. When two sources conflict, you will want the provenance.
Review the list monthly and delete what turned out not to matter. Reading volume is not the goal; a small number of correct, usable beliefs is.
Decide the purpose before the first line
Reading speed is mostly a decision problem. Before opening a document, write one sentence saying what you need from it: a decision, three facts, an understanding of the argument, or reassurance that nothing changed.
That sentence determines the technique. Extracting three facts is a search task. Understanding an argument requires reading the reasoning in order and cannot be safely skimmed or summarised.
Most reading overload comes from treating every document as the second kind when it is the first.
Where summaries are safe and where they are not
Summaries are reliable for narrative and descriptive material where the structure is stable: meeting notes, status updates, long email threads, product documentation.
They are unreliable for anything where the exception matters — contracts, policies, technical specifications, medical or legal text — because summarisation removes precisely the conditional clauses that carry the risk.
A workable rule: summarise to decide whether to read, never to decide what to do. The summary chooses your attention; the source makes your decision.
Retention needs a small active step
Reading faster without retaining anything is not a saving. After finishing, write three sentences from memory: the claim, the evidence, and what you will do differently. Two minutes, and it roughly doubles what survives a week.
Where the material matters long term, turn those three sentences into two questions and review them once a few days later. Spacing beats rereading by a wide margin.
Keep the notes searchable and in one place. Retention is partly memory and mostly retrieval.
Frequently asked questions
Do AI summaries hurt comprehension?
For material you intend to build on, yes — memory depends on effortful processing that the summary removes. Use summaries to filter and read the important items properly.
How reliable are summaries of technical writing?
Hedged claims, negations and conditionals are frequently flattened or inverted. Spot-check one specific claim against the source every time, and never quote from a summary.
What is the best way to retain what I read?
Turn it into a handful of question-and-answer pairs and revisit them a week later. Spaced retrieval outperforms rereading by a wide margin.
Does speed reading work?
Techniques that reduce subvocalisation trade comprehension for pace. Deciding what not to read produces far larger gains with no cost.
Should I read the summary first?
Yes, as triage. Read the source for anything you will act on, quote, or be accountable for.