How do I process information faster?
You do not raise a ceiling. You pick a gear. Ronald Carver's account of reading rate gives the same college-level reader five, from about 600 words a minute while scanning to about 140 while memorizing, each with its own comprehension floor. Speed that survives the check comes from choosing the gear the material deserves.
The framework treats rate as a repertoire, not a skill level, and still anchors the literature on how fast reading can go before meaning thins (Carver's five gears, restated in a review of reading speed limits). Scanning near 600 words a minute does little more than find the words, so comprehension sits near zero. Skimming near 450 adds pulling meaning out of them. Ordinary reading, Carver's rauding, sits near 300 and links sentences together, where most real comprehension happens. Learning near 200 adds holding ideas, and memorizing near 140 adds rehearsing facts.
Treat those numbers as benchmarks from one theory, not laws. The ordering is what holds: every faster gear drops work a slower one did, and most people read at the rauding rate rather than choosing a gear.
That gives you two rates per document: your preferred rate, the one you fall into, and your optimal rate, the fastest speed at which comprehension is not yet lost, usually lower. The colleague who finishes the same report in twenty minutes may simply be scanning for two numbers at a much lower floor. That is not a faster mind, it is a cheaper job.
Why is reading speed not the same as understanding speed?
Because the constraint sits behind the eye. At speed you keep recognition and lose fidelity: the exact wording of a clause, a number, an exception that flips the recommendation. Comprehension, not eye movement, runs out first, and the loss is invisible while you are moving.
What a gist cannot carry is what decisions need. Scanning a contract or a board memo leaves you with a shape and a topic, not the sentence that says "unless" or the footnote that changes the base of a percentage. Cheap on familiar material, expensive on anything new. Word recognition is quick; integrating sentences is slow, which is how your eyes keep moving after the meaning stops.
Why does re-reading feel like failing when it is the repair?
Because the repair is invisible work. Readers hold meaning at a brisk pace by slowing down, pausing, looking back a few words and reading a sentence again. In Walczyk's experiments, less fluent readers did more of this and still finished with literal comprehension as good as the fluent readers'.
Reading researchers call it compensatory encoding (the model Walczyk and colleagues tested). The pause, the look back and the second pass are not the reading breaking down. They are the mechanism that keeps it together.
The load-bearing result is about control. When readers set their own pace, high-level comprehension stops depending on how efficiently they recognize words or how much they hold in working memory. Those matter enormously when the pace is fixed, and less once the reader may slow at a hard sentence. So a reread means the gear was too fast for that paragraph. Slow down rather than restarting.
What changes when someone else sets the pace?
Control is the whole variable. When you set the pace, the repair happens automatically at the hard sentence. When a meeting, a deadline or a shared screen sets it, the repair has nowhere to go, so the cost shows up later as a number you cannot place or an exception you missed.
The closest test is a 2026 experiment by Laura Schwalm, Ralph Radach and Victor Kuperman in Scientific Studies of Reading (the published abstract). It paced 46 students through twelve personal narratives at five speeds. Comprehension held near 57% across a broad range and dropped significantly only at 405 words a minute, roughly 150% of the group's own natural 273, where it fell to about 49%.
Hold that loosely. One laboratory, young skilled readers, easy narratives, speeds set by a researcher rather than a deadline, with the drop at the top of the range. A fixed pace costs most in readers with the least spare capacity.
How do I practice this on documents, reports and conversations?
Name the job before the first line, then give the hard parts your own pace. Preview the structure, group the material into three or four named parts, say the point in two sentences without looking, then check what you got wrong. The check is the only step that tells you which gear you actually used.
Preview means headings, first sentences and the last line, because headings carry the argument. Explaining the point without looking is retrieval, the best-evidenced step here, so it cannot be skipped. Charts need the same discipline compressed: read labels and scale before the pattern, because a truncated axis stays wrong at any speed.
That check is also what Absorb is built around: twelve-minute sessions of reading, listening and visual material where you answer from memory and see what you missed. Absorb's daily comprehension workout on the App Store gives you three scores and rising difficulty.
When can slower processing signal something worth checking?
When it is a change from your own baseline, not a trait you have always had. Slowness that appears abruptly, worsens over weeks, or arrives with trouble finding words or following familiar tasks is a medical question rather than a training question.
Ordinary slowness has ordinary causes: new material, fatigue, a badly written document. The signal to take seriously is deterioration other people notice too. Nothing here is a diagnosis, and practice is not treatment.