Pomodoro for Reading: Why the 25-Minute Block Fails (And What Actually Works) | Chapterly Blog
Pomodoro for Reading: Why the 25-Minute Block Fails (And What Actually Works) Quick Answer: The Pomodoro Technique was designed for office work — small, interrupt-friendly tasks where the cost of stopping at an arbitrary 25-minute mark is near zero. Reading is the opposite kind of task. Comprehension depends on building a situation model in working memory, which takes 8-15 minutes to load and is destroyed every time the timer rips you out of it. If you read in 25-minute Pomodoros with 5-minute breaks, you spend roughly half your "reading" time re-loading the previous chapter's context. Three protocols work better: a 50/10 deep-reading block for narrative and argument, a 90-minute ultradian session for difficult nonfiction, and a 15-minute "edge" session protected by a wake-up retrieval pass. Skip Pomodoros for reading. Use the timer for the things Pomodoro was actually designed for. The Pomodoro Technique is the most-recommended productivity protocol of the last twenty years. Twenty-five minutes of focused work, five minutes of break, four cycles to a "set," then a longer rest. Francesco Cirillo developed it in the late 1980s for university coursework, named it after a tomato-shaped kitchen timer, and watched it spread into a cult. It is a useful...