How to Read a Paper

A first-pass workflow for deciding what to skim, what to decode, and when a paper deserves deep proof reading.
Modified

April 26, 2026

Keywords

paper reading, reading workflow, theorem reading, literature navigation

1 Why This Page Matters

Most readers lose time on papers because they go deep too early.

They start chasing a proof before they know:

  • whether the paper is even worth a deep read
  • whether the real blocker is notation, theorem structure, or missing prerequisites
  • whether the main claim is theoretical, empirical, or mixed

This page gives the first-pass workflow for making that decision on purpose.

2 First-Pass Workflow

Use this order:

  1. skim for structure
  2. map the main claims
  3. separate theorem evidence from empirical evidence
  4. identify the real blocker
  5. decide whether to read deeply now, later, or not at all

3 Core Workflow

3.1 1. Skim for structure

Before reading any proof carefully, identify:

  • the problem the paper is addressing
  • the section structure
  • where the main theorem or main empirical result lives
  • whether the heavy details are in the main body or appendices

The goal of this pass is orientation, not mastery.

3.2 2. Map the main claims

Ask what the paper is actually claiming.

Typical claim buckets:

  • theoretical: theorem, bound, guarantee, impossibility, characterization
  • empirical: benchmark gains, ablations, robustness behavior
  • algorithmic: method design, runtime, optimization behavior
  • mixed: theorem plus experiments that illustrate or stress-test a regime

If you cannot name the paper’s core claim type, you are not ready for deep reading yet.

3.3 3. Identify the first blocker

At this point, decide what is blocking understanding most:

This branching step is what turns Paper Lab into a workflow instead of a loose set of pages.

3.4 4. Decide whether to read deeply now

A paper deserves deep reading now if:

  • the main question matters to your current trail
  • the core claim is readable after one of the branch workflows
  • the missing prerequisites are small enough to repair

Otherwise, postpone it deliberately instead of half-reading it.

4 What To Mark Up

While reading, highlight:

  • the main theorem or result
  • the assumptions
  • the notation you do not recognize
  • the paper’s evidence for each major claim

5 Worked Example

Suppose you open a paper and see:

  • one theorem in the introduction
  • six appendices
  • unfamiliar notation in the first displayed equation
  • experiments that appear before the proof details

A good first-pass reaction is:

  1. skim the abstract, introduction, and theorem statement
  2. decide whether the main claim is theoretical or mixed
  3. notice that notation is already blocking the theorem
  4. open Notation Translation before decoding the theorem
  5. then open Theorem Decoder if the statement is still dense
  6. only after that decide whether appendix proofs are worth deep time now

That is much better than jumping straight into Appendix C.

6 Common Failure Modes

  • reading linearly from page 1 to the appendix without deciding what matters
  • spending thirty minutes chasing a symbol before deciding whether the paper deserves deep reading
  • treating theorem statements and experiments as the same kind of evidence
  • assuming the first hard-looking theorem is automatically the right place to start
  • postponing every hard part until the reading session collapses into skimming

7 Sources and Further Reading

Back to top