In Defence of Reading Slowly
Speed reading has been sold as a skill worth developing for decades. Read faster, cover more, get through your pile. The pitch is that you are losing information by reading slowly, that the mind can process at far higher rates than the average person reads and that training it to do so is simply efficiency. Some of this is true. Most of it misses the point.
Fast reading and slow reading are not the same activity running at different speeds. They are different activities. They engage the text differently, they engage the reader's mind differently, and they produce different outcomes in terms of what the reader retains, understands, and is able to use. Conflating them is like saying that a conversation and a broadcast are the same thing because both involve words.
What fast reading actually does
Fast reading is well suited to certain kinds of material. News, where you are scanning for facts and updates. Reports, where you need to extract a conclusion and a few data points. Email, where the relevant information is usually in the first two sentences. Anything where the goal is to determine whether the material warrants closer attention, fast reading is the appropriate tool.
What fast reading does poorly is give complex or precise material the time it requires. When you are moving quickly through a text, the brain is pattern-matching against what it already knows. It identifies the familiar shape of an argument and fills in the gaps from prior knowledge rather than reading what is actually on the page. This is efficient for confirming what you already know. It is unreliable for absorbing anything that challenges or complicates existing understanding.
This is why people who read quickly are often surprised to discover, when asked about a book they finished last month, that their recall is thinner than they expected. They covered it. They did not absorb it.
What slow reading produces
Slow reading forces a different kind of attention. When you are not rushing, you notice more: a word chosen precisely, a sentence that does not quite fit the argument around it, a claim that sounds confident but sits on nothing. You also notice what moves you and what does not, which turns out to matter more than most productivity frameworks admit.
There is research on this, though the mechanism is still debated. One reasonably robust finding is that reading comprehension drops significantly at speeds above about 200 to 300 words per minute for most people, especially with complex material. The popular speed-reading claim that comprehension is maintained at 600 or 800 words per minute has not held up well under controlled testing. What speed training mostly seems to do is increase skimming efficiency, which is useful, but not the same as reading.
The deeper argument for slowness is not about comprehension scores. It is about what reading is for. If the goal is to extract information, fast reading with occasional slow passes over the dense parts is reasonable. If the goal is to think differently, or to have your view of something genuinely altered, that requires the kind of sustained engagement that speed makes impossible. You cannot be changed by a text you have moved through before it had time to work.
Without it becoming a chore
Slow reading becomes a chore when it is applied uniformly, as an obligation rather than a choice. Not every book deserves the same pace. The question to ask when starting a book is what you are reading it for, and then read accordingly.
A novel being read for pleasure should move at whatever pace feels right. Rushing a novel is odd, but so is treating every page of a thriller like scripture. The slow reading argument applies most strongly to books where the argument matters, where precision matters, where you are trying to understand something difficult or unfamiliar.
For those books, a few practical habits help. Read in longer sessions rather than in snatched minutes, because complex arguments need accumulated context. Pause at the end of chapters and ask what the author just argued, in your own words, before moving forward. Mark passages that seem important before you know why, and come back to them. None of this is difficult. It is slower, which in our current environment is enough to feel radical.
There is nothing nostalgic about that. It is just an accurate description of how understanding works. The argument for speed reading was always a productivity argument, not a comprehension argument. If you are reading to cover ground, read fast. If you are reading to go somewhere, slow down.
One thing to do
Take a book you have been meaning to read seriously. Read it for thirty minutes without any other tab open, without your phone within reach, and at whatever pace the sentences require. Then write two sentences about what you actually understood from the session — not what it was about, but what you understood.