How to Finally Get Through Your Reading Backlog
Reading backlogs shrink when three things line up: the queue is honest (only things you still actually want to read), sessions are short and easy to start, and picking up where you left off costs nothing. Add a modestly faster reading pace and the math flips — the pile starts going down faster than it grows.
Everyone has the pile: half-read books, a "read later" list older than some of its articles, PDFs saved with genuine intent. The pile isn't a discipline problem. It's friction — every item requires deciding what to read, finding where you were, and re-loading the context. Remove the friction and reading happens in the gaps of a normal day.
1. Prune the queue ruthlessly
A backlog you don't believe in repels you. Go through the list once and delete everything you kept out of guilt — the article that was relevant to a project that shipped, the book you "should" read. What survives is a queue you're actually curious about, and curiosity is the fuel everything else runs on.
2. Make sessions small enough to always start
"I'll read for an hour tonight" fails on most nights. "I'll read for eight minutes now" almost never does. Ten minutes of focused reading at 300–400 WPM is 3,000–4,000 words — a long article, or a solid slice of a book chapter. Three of those a day finishes a typical non-fiction book in under a week. The trick is treating reading as something you do in found time, not a scheduled event that has to compete with your evening.
3. Kill the restart cost
The moment that actually kills books is the resume: you open the book after four days, don't remember where you were or what was happening, flip back a chapter, feel tired, close it. What fixes it:
- Exact-word resume — reopening puts you on the word you stopped at, not the top of a page.
- A short replay — seeing the last few words again rebuilds context in two seconds.
- One place for everything — books, articles, and PDFs in one library means "what do I read now?" has an instant answer.
4. Read faster — even a little
Speed is the multiplier on all of the above. Moving from an average 240 WPM to a comfortable 360 — a gain most readers reach within weeks of deliberate practice — cuts a five-hour book to about three and a half hours. Across a year, that difference alone is several extra books read in the same time you already spend.
Tip: keep a visible streak and a "time saved" number. Backlogs are demoralizing because progress is invisible — a counter that shows words read this week and hours saved makes the pile feel like it's losing.
5. Match the tool to the material
Linear non-fiction, articles, and reports are perfect for RSVP speed reading — streamed one word at a time, they simply go by faster. Fiction you read for the prose, or technical material you study, deserves the slow lane. A backlog system that lets you switch between a fast word stream and the full text keeps both kinds of reading in one place.
Put it together with Velo
Velo, coming soon to the App Store for iPhone, is designed as a backlog machine: import books (EPUB), PDFs, and web articles into one on-device library, read them one word at a time from 100 to 1000 WPM, resume on the exact word with a 3-2-1 countdown and ghost replay, and watch your streak, words read, and time saved climb. No account, no servers, no analytics — just the pile, going down.
