How to Read a Paper Without Reading All of It

Nobody teaches you how to read a research paper. You're handed a reading list, you open the first PDF, you start at the abstract and grind toward the references, and somewhere around the third page of the methods section you realize you've absorbed nothing. Then you do it again with the next paper. By paper four it's midnight.

The problem isn't your focus. It's the order. A paper is not a story, and reading it like one is the slowest possible approach. Experienced researchers almost never read top to bottom. They triage.

Read in passes, not in order

The single most useful idea here comes from a short, widely-circulated note by S. Keshav called "How to Read a Paper." The core of it is the three-pass method, and once you've used it you won't go back.

Pass one — five to ten minutes. Decide if this paper is worth your time at all. Read the title, the abstract, and the section headings. Look at the figures and tables. Read the conclusion. Skip everything else. At the end you should be able to answer: what is this paper claiming, and is it relevant to me? Most papers should be rejected at this stage. That's the point — the first pass is a filter, and a good researcher rejects far more than they read.

Pass two — about an hour. Understand the argument, not the proof. Now read the body, but lightly. Look hard at the figures — in most empirical papers, the figures are the result, and a well-made figure tells you the finding faster than the prose around it. Mark the parts you don't understand and the references you'll want to chase. You're after the shape of the argument: what they did, what they found, and whether you believe it. You are not yet trying to reproduce it.

Pass three — only for the few papers that matter. Read it like you'll have to defend it. This is the deep read: methods in detail, assumptions questioned, the parts you'd need to actually build on or critique. You'll only do this for a handful of papers in any project. That's correct. Not every paper deserves three passes; some deserve none past the abstract.

A few things that speed all of this up

• The abstract oversells. The discussion is more honest. Authors hedge in the discussion section — limitations, threats to validity, what they couldn't show. That's often where the real information is.
• Read the figures before the prose. If you can't tell what a figure is showing, that's a sign to slow down. If you can, you may not need the surrounding paragraphs at all.
• It's fine to bail. Putting a paper down after the first pass is a skill, not a failure. Time spent finishing a paper you've already decided is irrelevant is time stolen from one that matters.
• Keep the quote, not just the citation. When something is genuinely useful, pull the exact passage and note where it came from, while you're looking at it. Re-finding "that one line from that one paper" three weeks later is its own special misery.

Where tools help (and where they don't)

A good reader and a tool that can search inside your sources are a strong combination. Once a paper is in your library, you can ask a pointed question — "how did they handle sample size?" — and jump straight to the passage instead of re-skimming the whole methods section. That's a real accelerator for pass two and pass three.

What no tool replaces is the judgment in pass one: deciding what's worth reading at all. That stays yours. The skill isn't reading faster. It's reading less, on purpose, and reading the right things deeply.

Folio keeps your sources, highlights, and notes in one place — and lets you ask questions straight to the passage. Join the waitlist.