Sharan Initiatives
๐Ÿ“š
๐Ÿ“šLiterature

Speed Reading Doesn't Work. Skimming Does, and That's Fine.

The research on reading rate is unusually clear and unusually unpopular: you cannot read much faster without understanding less. What you can do is decide, deliberately, what deserves understanding.

By Taresh Sharan ยท PhD, IIT BHUโ€ขJanuary 27, 2026โ€ข8 min read

Every few years someone tries to sell me a course that will triple my reading speed with no loss of comprehension. I have now read enough of the underlying research to be confident about the response, which is that this is not a thing that happens, and that the courses are selling skimming with a better name.

That sounds discouraging. It is actually liberating, because once you stop trying to read everything faster you can start making the decision that matters, which is what to read slowly and what not to read at all.

What the evidence says

The most useful single source here is a review by Keith Rayner and colleagues in Psychological Science in the Public Interest, which surveyed decades of eye-movement and comprehension research and concluded that there is a straightforward trade-off between reading speed and comprehension, and that the dramatic gains claimed by speed-reading programmes do not survive testing.

The constraints are physical and they are not negotiable by training.

Your eyes do not sweep smoothly along a line. They jump, pause, jump again. Understanding happens during the pauses, and each pause takes a certain amount of time because that is how long visual and language processing take. Sharp vision covers a very small region โ€” a handful of characters around the fixation point โ€” so the idea of absorbing a whole line, let alone a whole page, in one look is not a skill anyone is withholding from you. It is anatomy.

Skilled adults reading normal prose in a language they know well run somewhere in the range of a couple of hundred to around four hundred words a minute. This range has been measured repeatedly and it is remarkably stable. Someone reporting a thousand words a minute with full comprehension is either skimming, reading something they already essentially know, or testing themselves with questions that could be answered without reading.

The common techniques fail for identifiable reasons. Suppressing the inner voice does not free up capacity; that subvocal representation appears to be part of how comprehension works, particularly for difficult text. Eliminating regressions โ€” the small backward jumps your eyes make several times a page โ€” removes a repair mechanism you need, because the regressions happen precisely when something did not parse. And presenting words one at a time at high speed in a fixed position, which several apps do, prevents regressions entirely and leaves you with no way to recover from a sentence you missed.

The one thing that genuinely makes you faster

Knowing the subject.

This is the finding people skip past because it cannot be sold as a technique. Reading rate on familiar material is substantially higher than on unfamiliar material, for the simple reason that prediction is doing part of the work. When you know the field, you know roughly where a sentence is going, and confirming a prediction is faster than constructing a meaning from nothing.

Which means the reliable route to reading a technical literature quickly is to read a lot of it slowly first. The fifth paper in a subfield takes a fraction of the time of the first. There is no shortcut, but there is a compounding return, and it is the only one on offer.

Skimming is a real skill and worth doing well

None of this means you should read everything at full attention. Most of what arrives in front of you does not deserve it, and reading everything carefully is its own failure โ€” it usually means never finishing anything.

The honest framing is that skimming is not fast reading. It is selective non-reading: you are choosing which parts to actually read and discarding the rest, and the skill is in choosing well.

For an article, the structure is usually doing the work for you. Title, opening, section headings, first sentence of each section, conclusion. Five minutes of that tells you what the piece claims and whether the claim is worth the rest of your time. For a research paper: abstract, then figures, then methods only if the result matters enough to check how it was obtained. For a business book, which is typically one idea and a lot of illustrative anecdote: the contents page and the chapter openings will usually get you the idea, and you can stop.

What skimming cannot do is give you understanding you can use later. You will come away with a gist and a false confidence that you know the material. That is fine when the gist was the goal. It is a problem when you were supposed to be learning something and mistook coverage for comprehension.

When to slow down

Deliberate slowness is the correct response to a smaller set of material than most people's reading lists suggest, but for that set it is not optional.

Anything you intend to act on. Anything where a misunderstanding is expensive โ€” contracts, specifications, medical information. Anything genuinely new to you, where you have no prior structure to hang the sentences on. Anything where the writing itself is part of the value, which covers most poetry and most good fiction. And anything you expect to still be using in a year.

For hard material, the technique that has consistently earned its keep for me is closing the book and trying to say what it just said. Not re-reading the paragraph. Saying it, out loud or on paper, in ordinary words. The gaps appear instantly and they are never where you expected. Then go back and read only the part that failed.

The second is writing in the margin, which forces a judgment on every paragraph instead of allowing your eyes to keep moving while your mind does not. A question mark is enough.

The third is reading difficult things twice, deliberately: once fast to get the shape, once slowly with the shape in hand. This is genuinely faster than one careful pass, because the first pass tells the second one where to spend its effort.

The actual decision

The useful question was never "how fast can I read." It is: what is this text for, and therefore what does it deserve.

For most of what crosses your desk the answer is a few minutes of structured skimming and then a decision to stop. For a small fraction the answer is slow, annotated, repeated reading, and for that fraction trying to be efficient is self-defeating. The mistake people make is not reading too slowly. It is applying one speed to everything, and then feeling guilty about the volume they are not getting through.

There is also an entire category where speed is simply the wrong frame. Nobody finishes a novel they loved and wishes they had got through it quicker. Reading for pleasure at maximum rate is like eating for nutritional throughput โ€” technically the calories arrive, and you have removed the reason for doing it.

The readers I know who get the most out of what they read are not fast. They are decisive. They abandon things quickly, they skim without apology, and when something is worth it they slow down much further than most people ever do.

That is the whole technique. There is no course.

Tags

ReadingSpeed ReadingDeep ReadingLearningProductivityLiterature2026

About the Author

S

Taresh Sharan

PhD ยท IIT BHU

Research Scientist ยท Bangalore, India

PhD in Biomedical Engineering from IIT (BHU) Varanasi. Research Scientist based in Bangalore. Author of 200+ articles across AI, finance, photography, technical writing, careers, literature, and corporate ethics. Builder of the free Money and Health apps on this site.

Medical AITechnical WritingPhotographyPersonal FinanceLiterature
Full profile
Speed Reading Doesn't Work. Skimming Does, and That's Fine. | Sharan Initiatives | Sharan Initiatives