How to Get Through a Week's Worth of Reading in Twenty Minutes
A simple system for handling the reports, threads, and documents piling up — no speed reading, no new app, no extra hours in the day.
There's a folder on your desktop with four things in it you've been meaning to read.
Not because they don't matter. Because reading them properly costs an hour you never quite have — and skimming them badly feels worse than not opening them at all.
Most of what lands on your desk wasn't written to be read. It was written to be filed.
Reports padded to look thorough. Proposals that bury the number on page six. Threads with forty messages and one decision hiding in the last four.
The skill worth having isn't reading faster. It's getting to the decision without reading all of it.
Here's the practice, start to finish.
Paste the whole thing in. The report, the thread, the forty-page PDF. Don't tidy it first — formatting doesn't matter and cleaning it up is the part that stops people bothering.
Then ask three questions, in this order.
What is this actually asking me to do or decide? That's the only question that matters, and it's the one long documents are best at hiding.
What would I disagree with if I read this closely? This surfaces the soft claims, the assumptions doing quiet work, the numbers that don't hold up.
What's missing that I'd expect to see here? The gaps tell you more than the content. A proposal with no timeline. A report with no comparison. An agreement with nothing about what happens when things go wrong.
Four minutes. And now you know whether the hour is worth spending.
Now the part most people skip.
Read the section that matters yourself. Properly, with your own eyes.
A summary is excellent at telling you where to look and unreliable at telling you what to think. The two or three paragraphs carrying the actual decision still deserve your attention.
● In a proposal, that's scope and payment terms — never the summary of them.
● In a report, it's the method, not the headline. The headline is written to be quoted.
● In an agreement, it's whatever happens when things go wrong. That's the only part you'll ever need.
● In a long thread, it's the last four messages. That's where everyone's real position finally shows up.
Two things worth knowing. Never act on a summary of something you haven't opened. And when the stakes involve money or a signature, treat the summary as the map, not the territory.
Twenty minutes on the backlog today. Paste, ask three questions, then read only what earns it.
❯❯❯❯ And if you'd like the wider set of systems that make weeks like this run themselves, take a look
The reading was never the work. The deciding was.
— AI Business Builder
