What Marathon Runners Can Teach Us About Reading Long Books

Every marathon coach says some version of the same thing: the race is won or lost long before the part that feels hard. By the time a runner is struggling at mile 22, the outcome was mostly decided by pacing choices made in the first 30 minutes — choices that felt completely fine at the time, which is exactly why they're dangerous.

Long books fail for readers in almost the identical way. Nobody abandons a 400-page book on page 380. They abandon it on page 60, when the initial momentum of "this is interesting" runs out and nothing has replaced it — not because the book got worse, but because there was never a pacing plan for the middle, the part that doesn't have a new-book high or a finish-line adrenaline spike to carry it.

The fix endurance athletes use is deceptively simple: stop treating the whole distance as one effort, and break it into segments you can actually evaluate honestly. A marathoner doesn't think about mile 22 during mile 4 — they think about finishing mile 4 well. Applied to reading, that means picking a real, small unit — a chapter, 20 pages, one sitting — and finishing that unit, rather than measuring your progress against the intimidating total.

It also means accepting a "long book pace" the same way a runner accepts a "long race pace" — slower than you'd sprint at, sustainable past the point where sprinting stops feeling good. A 300-page cricket history read at 15 unhurried pages a night finishes in three weeks. The same book attacked in one ambitious weekend, and abandoned when that ambition runs out around page 80, doesn't finish at all.