How to keep up with reading for work

Short answer: nobody reads all of it, including the people who seem to. They triage by one question: does this affect a decision I have to make? Items that pass get read fully. Everything else gets a five-minute skim or a skip. Add one or two protected calendar blocks so the reading that matters actually happens.

The volume problem is real

Do the math on a normal week. A 10-page report is roughly 5,000 words: 20 to 25 minutes at an average 200 to 250 words per minute, longer if you need to think about it. Five reports, a dozen substantial memos, two dozen industry articles, plus the newsletters, and you are at 8 to 10 hours of reading against a calendar that has maybe 2. That gap is arithmetic. Ten hours of material does not fit into two hours of time, so selection is the only workable response.

Triage by decision-relevance

Filter every item with one question: what decision or action of mine does this change? “Is it important?” fails as a filter, because almost everything at work can be argued into importance. Decision-relevance sorts cleanly:

Read fully: anything feeding a decision you own, a meeting where you must have a position, or work you are reviewing. This pile is usually two or three items a week.

Skim for shape: things where you need awareness. Executive summary, headings, conclusion, five minutes. You are building a map of what exists so you can return if it becomes decision-relevant. For most industry news, the headline plus the first paragraph covers it.

Skip: everything that informs no decision and no conversation you will actually be in. Most FYI-cc’d documents live here. If one turns out to matter, someone will surface it. Organizations repeat important information many times, and you can rely on that.

Summaries vs. full reads

For most work documents, the summary carries the conclusion, because authors put it on the first page knowing how their audience reads. The remaining nine pages usually add evidence and detail. Reading them gives you the same conclusion with more confidence.

So match depth to stakes. For a high-stakes decision, or a document you will be challenged on, do the full read: the problems hide in the details, and summaries are written by people with incentives. For everything else, read the summary and move on. Avoid the middle path of half-reading everything, which costs full-read time and delivers skim-level understanding.

Batch it into calendar blocks

Reading scattered through the day in two-minute fragments accomplishes little, because each fragment is mostly spent re-finding your place. Instead, collect everything into one queue as it arrives, without reading on arrival, and process the queue in one or two scheduled blocks: say 45 minutes twice a week, on the calendar like a meeting, because unscheduled time gets taken by meetings.

Batching has a second benefit: at the top of each block you see the whole week’s pile at once, which makes triage natural. Sort first, then read in priority order. When the block ends, whatever is left unread below the line probably deserved to be.

One caveat: genuinely urgent items, like a document your boss needs a response on by 3 p.m., jump the queue. The blocks handle the recurring volume, and urgent items get handled as they arrive.

Industry news specifically

Industry news is the biggest time sink because it is endless and mostly repetitive. Pick one or two sources that aggregate well and drop the rest. Ten feeds covering the same story give you one story ten times. Fifteen minutes twice a week covers awareness for most fields, and anything genuinely large will reach you through colleagues anyway.

Common questions