25 How to Read Scholarly Articles and Books
Prerequisites (read first if unfamiliar): Chapter 2, Chapter 3.
See also: Chapter 26, Chapter 29, Chapter 35, Chapter 31.
Purpose

Your seminar assigns five journal articles for next week. You open the first, and it doesn’t feel like reading. The abstract uses three terms you’ve never seen, the introduction starts a polite argument with people you’ve never heard of, and page six is a table of regression coefficients studded with asterisks. You read every sentence in order anyway, highlight half of them, and two hours later you can’t tell a friend in one sentence what the paper found. Then you remember there are four more, and your Downloads folder is filling up with files named 1-s2.0-S0747563219302213-main.pdf.
If that sounds familiar, you’re not a slow reader, and you’re not missing a talent everyone else was born with. Research papers are written for a small group of specialists, and nobody hands students the routine those specialists use to read them. That routine is learnable: working researchers skim most papers, read a few carefully, and keep what they read in a system they can search months later. It’s craft, and it improves quickly once someone shows you how it’s done.
This chapter covers that craft: triaging a paper before you commit to it, reading at three depths, adjusting to HCI, machine-learning, social-science, and humanities writing, getting a paywalled paper legally and judging whether it’s any good, taking notes and managing references with Zotero, and turning a pile of papers into a literature map. Writing papers is Chapter 26, and typesetting them is Chapter 29.
Why read this chapter
- You read an article start to finish, highlighted half of it, and a day later couldn’t say in one sentence what it found.
- You hit a methods section full of equations or regression tables and stalled, unsure whether you’re allowed to skip it.
- Your Downloads folder holds forty PDFs named like
1-s2.0-S0747563219302213-main.pdf, and the one you need to cite is in there somewhere. - A paper you need offers to sell you a copy, and nobody told you about the legal ways to read it for free.
- You found a paper through Google or arXiv and can’t tell whether it was peer reviewed, whether anyone takes it seriously, or whether it has since been retracted.
- Your instructor wants a literature review, and you have a stack of summaries but no idea how to turn them into an argument.
- You asked a chatbot for sources and got a citation that looked perfect and doesn’t exist.
Running theme: you are not reading to finish; you are reading to decide what to read more carefully
You’ll meet far more papers than you could ever read closely, so the skill isn’t reading faster: it’s reading each paper at the depth your purpose calls for, and knowing how to decide what that is.
25.1 Why reading is hard (and why nobody taught you)
Most students arrive at their first research paper with habits built on textbooks: start at the top, read every sentence in order, highlight what seems important. That works for a textbook, where every sentence was written for you and the author’s job is to be clear. It fails on a research paper, which is written for a small community of specialists and whose main goal is to convince skeptical reviewers that it makes a contribution, not to teach you.
So when a paper seems to be written in another language, you’re not imagining it. Papers are condensed correspondence between specialists: they use jargon as shorthand because the intended reader knows it, and they cite earlier work in passing because the intended reader has read it. Even the abstract is a compressed pitch to experts. None of that is your fault. The fix isn’t to read harder; it’s to read with a different routine.
That routine rests on two ideas. Most papers don’t deserve a full read. A paper you cite once in passing may need ten minutes, and a paper you build your project on may need an afternoon; you get to decide which is which. And you read in passes, not in one sweep. Each pass adds depth, and you start the next only if the last one showed the paper was worth it.
25.2 The three-pass method
A widely shared version of that routine is a two-page article by the computer scientist S. Keshav, “How to Read a Paper.”1 He wrote it because reading papers efficiently is, in his words, “a critical but rarely taught skill,” which leaves new graduate students to learn by trial and error. It takes ten minutes to read; read it before your next assigned paper. The idea is to read a paper in up to three passes instead of plowing from the first word to the last.
1 S. Keshav, “How to Read a Paper,” ACM SIGCOMM Computer Communication Review 37, no. 3 (2007): 83–84. A free copy is linked in Further reading.
The first pass takes five to ten minutes and decides whether to keep going. Read the title, abstract, and introduction carefully; read the section headings but nothing under them; read the conclusions; and glance over the references for any you’ve already read. Then answer what Keshav calls the five Cs: category (a measurement study, an analysis of an existing system, a new prototype?), context (which papers and theories does it build on?), correctness (do its assumptions look valid?), contributions (what are they, in your own words?), and clarity (is it well written?). Stopping here is often the right call, whether because the paper doesn’t interest you, you don’t yet know enough to follow it, or its assumptions don’t hold up.
The second pass takes up to an hour and grasps the content without the details. Read with more care, but skip proofs. Look closely at the figures and graphs, which are often where the argument lives: are the axes labeled, and do results come with error bars, so you can tell whether a difference is real? Jot key points in the margins and mark unread references to chase later. At the end you should be able to summarize the paper’s main thrust, with its evidence, to someone else.
If the paper still makes no sense after the second pass, that’s normal. Keshav’s list of reasons includes unfamiliar terms, a technique you don’t know, bad writing, and “it’s late at night and you’re tired.” Set it aside, come back after some background reading (a review article on the topic is often the best start), or push on.
The third pass is the deep read, for a paper you’ll build on. The key, Keshav says, is to “virtually re-implement” the paper: make the authors’ assumptions, re-create the work yourself, and compare your version with theirs. That shows you both what’s new and what’s hidden, the failings and assumptions the paper doesn’t advertise. He estimates four or five hours for a beginner and about an hour for an experienced reader.
The first pass is cheap and the third is expensive, and most students spend them backwards, burning two hours on a careful read of a paper that ten minutes of skimming would have set aside.
25.3 Skimming vs. deep reading: deciding what a paper is for
The passes only help if you know which one a paper needs, and that depends on why you’re reading it. Name your purpose before you open the PDF.
Reading to cite. You need to know what the paper says so you can refer to it accurately. A first pass is often enough, but watch for the most common failure in student writing: citing a paper for a claim it doesn’t make. Before you write “Smith (2021) found that…”, check that the paper really says so, in its body and not just its abstract.
Reading to build on. You’ll reuse the method, extend the analysis, or reproduce the results. That’s a third pass; plan the hours instead of hoping to squeeze them in.
Reading to learn a concept. You’re using a paper as a textbook. Usually there’s something better: a review article, a textbook chapter, or the related-work section of the newest paper on the topic, which is a guided tour written by someone who just had to understand the field. Keshav gives the same advice for starting a literature survey: if the papers you find point to a survey, read it, “congratulating yourself on your good luck.”
25.4 Reading across disciplines
Information science borrows from so many fields that you may read four writing traditions in one semester, and each puts “the contribution” in a different place. Read one with another’s habits and it will feel either impenetrable or trivially obvious.
HCI and social computing (CHI, CSCW, ICWSM, FAccT). Papers from venues like CHI and CSCW usually follow some version of IMRaD (introduction, methods, results, and discussion), with a related-work section after the introduction and “findings” in place of results. Qualitative and mixed-methods studies are common. The introduction states the gap and the contribution, so look for the sentence beginning “In this paper, we…” or a bulleted list of contributions; if you can’t find either in the first two pages, the paper may be weak, or you may be skimming too fast. The discussion often closes with “implications for design,” advice for the people who build systems. Much of the argument rides on how the introduction frames the problem, so read it twice.
Machine learning and data science. These are denser, and the argument lives in figures, tables, and benchmark results. The contribution is usually a method, a benchmark result, or a dataset. On a first pass, find the figure or table with the main result (often near the front) and the experimental setup; the related work in a fast-moving field can wait. When a paper claims state-of-the-art results, check what it compared against and whether differences come with error bars or repeated runs. Many of these papers appear first as preprints on arXiv, before peer review or without it.
Social-science empirical work (JASIST, JCMC, New Media & Society, Information, Communication & Society). These follow theory, method, results, and discussion fairly strictly. The theory section tells you what the authors think they’re measuring and why, and most of the action is in operationalization, where an abstract idea like “political engagement” becomes something you can count. Notice what kind of claim the design supports (a causal effect, a description, or an exploration), and read the limitations section, which tends to be more substantive than in many computing venues.
Humanities scholarship. The article is an argument, and its structure follows the argument rather than a template; the abstract may only pose the question. Somewhere in the first few pages there’s usually a thesis statement saying what the author claims, and the rest defends it move by move. Find that sentence first, then read the article as moves on it: what is the author conceding, whom are they arguing against, and where does the evidence come in?
25.5 Getting a copy without paying for it
Sooner or later you’ll click a promising title and land on a publisher’s page offering to sell you the article. Don’t pay, and don’t give up: most papers you need can be read legally for free.
Start with your library. Your university pays for subscriptions so you don’t have to, though access often works only on the campus network or after signing in through the library. Search from the library’s website, or use Google Scholar, which shows library links (such as “Find it@” plus your school’s name) beside results your library subscribes to; its help page says what to do if yours don’t appear.
Look for a free version. Many papers also exist as a preprint on arXiv or a similar server, in the authors’ university repository, or on their own website. In Google Scholar, click “All versions” under a result and look for a [PDF] link. The free Unpaywall browser extension does that search for you and flags a legal open-access copy when it finds one.
Ask. Email the author; many researchers will happily send a copy. For a book chapter or an article your library lacks, interlibrary loan can usually get a scan from another library, often at no charge to students.
A preprint can differ from the published version, because it came before peer review, so cite the version you actually read.
25.6 Is this paper any good?
You found a paper that says exactly what you hoped, and now you have to decide whether to trust it. Nobody expects you to audit a method you’ve never studied, but a few questions tell you a lot.
Was it peer reviewed? Peer review means other researchers read the paper before publication and could demand changes or reject it. It’s a filter, not a guarantee. A preprint hasn’t passed through it: arXiv screens submissions but says plainly that material there “is not peer-reviewed by arXiv.” Preprints are normal and often excellent, especially in machine learning; treat their claims as provisional.
Where did it appear? A venue the field’s other papers cite regularly has usually given the paper a tougher review than one nobody has heard of. Be wary of predatory journals, which publish nearly anything for a fee, and ask a librarian when you can’t tell.
Is it still standing? Papers are sometimes retracted for serious errors or misconduct, and the PDF you downloaded doesn’t know. Look it up in the Retraction Watch database, or let Zotero do it: it checks your library against that database and warns you about retracted items.
What do later papers say? Google Scholar’s “Cited by” link lists the papers that cite this one. A big number means the paper is widely discussed, not that it’s right, so skim a few recent citing papers to see whether they build on it or push back.
How did they measure it? The questions so far judge the paper from the outside; this one looks inside. Find the two or three key variables (usually the outcome and whatever is supposed to explain it) and, for each one, how the authors turned the concept into something they could count, the operationalization from “Reading across disciplines” above. Then ask whether that measure really captures the concept, which methodologists call construct validity. A study of “political engagement” that counts retweets of politicians, or of “learning” that counts minutes logged into a course site, may be measuring something narrower than its title promises, or something else entirely. The methods section says what was measured, and the limitations section is often where the authors admit how far the measure falls short. A paper can be peer reviewed, widely cited, and never retracted, and still rest on a number that doesn’t mean what the abstract says it means.
25.7 Note-taking systems
Six months after reading a paper, you open it again and can’t remember why you saved it or what it found. Highlights don’t prevent that; notes in your own words do. Three approaches cover most of what researchers use. Pick one and give it a semester before you judge it.
Cornell notes, devised in the 1950s by the Cornell education professor Walter Pauk, divide a page into a narrow cue column on the left, a wide notes column on the right, and a summary strip at the bottom. You take notes on the right as you read, write questions in the cue column afterwards, and finish with a two- or three-sentence summary. The Cornell method is excellent for studying one dense source, and less help for connecting many.
A Zettelkasten (“slip box”) is built from atomic notes: one idea per note, in your own words, linked to related notes. The sociologist Niklas Luhmann kept one of some 90,000 index cards and credited it with his prolific writing. Today people build them in apps like Obsidian2 and Logseq.3 Its strength is synthesis: when you sit down to write a literature review, the connections are already there. Its risk is overhead: if you build the system and never write from it, you’ve built a very pretty filing cabinet.
2 Obsidian, https://obsidian.md/, a free note-taking app that stores your notes as plain Markdown files on your own computer.
3 Logseq, https://logseq.com/, a free, open-source app for building linked notes.
4 Hypothes.is, https://web.hypothes.is/, a free tool for annotating web pages and online PDFs right in your browser.
Annotation-first means highlighting and commenting on the PDF itself, on the web with Hypothes.is4 or inside your library with Zotero’s PDF reader, which can gather a paper’s annotations into a note in one step. It’s low overhead and good for fast triage. The catch is that highlights aren’t knowledge: unless you go back and turn them into ideas in your own words, they rot.
Many researchers blend the last two: annotate everything, and write Zettelkasten-style notes only for the ideas that matter.
25.8 Reference management with Zotero
Over a degree you’ll collect hundreds of papers, and without a system they end up scattered across Downloads, a cloud drive, and a bibliography that no longer matches your paper. A reference manager keeps each paper’s details, its PDF, and your notes together in one searchable library. Use Zotero. It’s free, open source, actively maintained (version 10 came out in August 2026), and it works with Word, Google Docs, LibreOffice, and LaTeX.
Install Zotero5 and the Zotero Connector for your browser; the Quick Start Guide covers both. The Connector is the part that feels like magic: on a Google Scholar result, a publisher’s page, or an arXiv abstract, one click saves the item with its authors, title, and journal, attaches the PDF when it can, and files it in a collection, with a popup where you can change the collection or add tags. Make a collection for each course or project, and tag freely by method, population, theory, or just to-read.
5 Zotero, https://www.zotero.org/, from the nonprofit Digital Scholar.
6 Better BibTeX for Zotero, https://retorque.re/zotero-better-bibtex/.
If you write in LaTeX or Markdown, add the Better BibTeX plugin.6 It gives every item a stable citation key, the short label like keshav2007 that you type in \cite{} or [@...], instead of recomputing keys at every export, and it can keep a .bib file up to date automatically, so your bibliography is always current. The worked example below sets both up, and Chapter 29 covers the writing side.
Two practical notes. Syncing your library’s data with a free Zotero account is unlimited, but PDFs count against a 300 MB free storage allowance, so a PDF-heavy library eventually needs a paid plan or another way to sync files. And if you’re weighing alternatives: Mendeley has been owned by the publisher Elsevier since 2013, and in 2018 it began encrypting its local database, which, as Zotero’s import guide explains, stopped other tools from reading it; Paperpile is a paid subscription. For a library you can take with you when you graduate, Zotero is the safe default.
25.9 Synthesis: building a literature map
At some point reading turns into writing: an instructor asks for a literature review, or your paper needs a related-work section. Many students freeze here, holding one summary per paper when the review is supposed to be an argument. The missing step is a literature map, the organized notes you write from.
The simplest is a concept matrix, from Webster and Watson’s guide to literature reviews.7 Rows are papers; columns are concepts, methods, populations, or theoretical frames; each cell holds a phrase about how that paper treats that concept. Fill it in for ten or fifteen papers, and the columns become the sections of your review, organized by idea instead of paper by paper, while the empty cells show where the literature is thin, which is where your contribution might go.
7 Jane Webster and Richard T. Watson, “Analyzing the Past to Prepare for the Future: Writing a Literature Review,” MIS Quarterly 26, no. 2 (2002): xiii–xxiii. Linked in Further reading.
8 Connected Papers, https://www.connectedpapers.com/, draws a graph of papers similar to one you choose, based on shared citations.
9 Litmaps, https://www.litmaps.com/, maps the citation network around a set of seed papers.
To find the papers, trace citations both ways. Backward: read a key paper’s reference list for the work it builds on. Forward: look it up in Google Scholar and click “Cited by” for the work that builds on it. Connected Papers8 and Litmaps9 map the neighborhood around a paper for you, and either is worth ten minutes at the start of a project. Watch for the papers that show up in many bibliographies and the names that keep recurring: Keshav calls them the key papers and key researchers of an area, and reading the key researchers’ newest work is the fastest way to catch up.
Keep the map small: fifteen well-organized papers beat fifty disorganized ones. (A systematic review, which tries to find and assess every study on a question by a written protocol, is a much bigger job; you’ll know if you’ve been asked for one.) Chapter 26 picks up where the map becomes prose.
25.10 Reading with AI: legitimate uses and traps
Large language models change the economics of reading, for better and worse. Chapter 35 covers these tools in general; here’s what matters for scholarly reading.
Used well, they help. Ask for a summary to support your first pass (never to replace it), for the meaning of unfamiliar notation or jargon, or for a critique of your own one-paragraph summary. Ask for related papers too, and then verify each one in Zotero or Google Scholar, because language models invent citations that look completely real: plausible authors, a plausible title, a real journal, and no such paper. That failure is called hallucination, and a fabricated citation in your bibliography is the kind of mistake instructors notice.
The trap is letting a summary stand in for the paper. It catches up with you the first time you cite a paper for a claim it doesn’t make. Models sound equally confident when they’re wrong, and they can blur a paper’s own findings with its description of other people’s.
A protocol that works: get a summary, do your own first pass, and compare. Where they disagree, the paper wins, and anything the model mentions that you didn’t see in the paper is suspect until you check it. Chapter 38 has more on checking what these tools tell you.
25.11 Stakes and politics
On February 28, 2019, the University of California, whose ten campuses account for nearly 10 percent of U.S. research publishing, announced it was ending its subscriptions with Elsevier, the world’s largest scientific publisher, after talks over price and open access broke down. For two years, until a new agreement in 2021, researchers at one of the best-funded university systems in the world worked around a paywall on new Elsevier articles. Now picture a student at a small college, a researcher in a country whose libraries can’t afford the bundle, or a taxpayer who funded the research. For them the paywall isn’t a two-year dispute; it’s the default. Shadow libraries like Sci-Hub, which has lost copyright lawsuits in U.S. courts, exist because that gradient is so steep.
Access shapes what gets read, and what gets read shapes what gets cited. A 2020 study of five top neuroscience journals found that reference lists included more papers with men as first and last authors than would be expected if gender were unrelated to citing, and a 2018 study of communication journals, “#CommunicationSoWhite,” found non-White scholars underrepresented in publication, citation, and editorial roles. The venues that count most for hiring are mostly English-language and reward particular genres, so community-engaged and practitioner work is harder to publish and harder to find. Each time you cite what was easiest to find, you make it easier for the next reader to find, too.
See Chapter 8 for the broader framework. The concrete prompt to carry forward: when you build a literature map, ask whose work was easy to find and whose work the system you searched in routinely buries.
25.12 Worked examples
First-pass a CHI paper in eight minutes
Pick a recent CHI paper on a topic you care about, say an interview study of how data-science students use AI assistants, and set a timer for eight minutes. This version of the first pass adds one thing Keshav saves for the second, a look at the figures, since in an HCI paper they’re often the quickest route to the main claim.
Minutes 0–1. Read the title and abstract, and write one sentence: what does the paper claim? If you can’t, read the abstract once more.
Minutes 1–3. Read the introduction, slowing down for the first paragraph (the problem) and the last (usually the contribution). Skim the middle, which is typically the gap and the framing, for the names of competing approaches.
Minutes 3–5. Look at every figure and read every caption. The main result is usually the figure with the prominent comparison or the most annotation. In a qualitative paper the equivalent may be a table of themes or a set of participant quotes.
Minutes 5–7. Read the section headings, skim the discussion for “implications” or “design considerations,” and glance at the references for names you recognize.
Minutes 7–8. Write three things: a one-sentence summary, the contribution in your own words, and one question you’d ask the authors.
If you can fill in all three, you can decide whether it deserves a second pass. If you can’t, the paper is poorly written or beyond your current background, and either way that’s useful to know.
Setting up a Zotero library for a semester project
You’re starting a term paper and want the references handled before the first draft, not the night before it’s due.
- Install Zotero and the Zotero Connector from the download page. Create a free Zotero account and sign in under Zotero’s Sync settings, so your library follows you between computers.
- In Zotero, right-click “My Library,” choose “New Collection…,” and name it “INFO 4XXX – Term Paper.”
- Install Better BibTeX. Download the latest
.xpifile from its installation page (in Firefox, right-click and save it rather than clicking the link). In Zotero, choose Tools → Plugins, click the gear icon, choose “Install Plugin From File…,” and pick the.xpi. - Open Zotero’s settings (Edit → Settings on Windows and Linux, Zotero → Settings on a Mac), go to the Better BibTeX pane, and set the citation key formula to
auth.lower + year, which gives keys likekeshav2007(Better BibTeX adds a letter, as inkeshav2007a, when two would clash). Do this before you collect much: the default formula also includes words from the title, and changing the formula doesn’t rewrite keys that already exist. - Right-click your collection, choose “Export Collection…,” pick the “Better BibTeX” format, tick “Keep updated,” and save the file as
~/code/term-paper/references.bib. From now on, whenever you add or edit an item in the collection, that file updates itself. - Find five papers through Google Scholar. On each, click the Connector’s save button and check that the popup names your term-paper collection. Add tags in the same popup.
- Open
references.bibin your text editor. You should see five BibTeX entries, each starting with a key you can cite.
It takes about twenty minutes the first time and seconds per paper after that.
Synthesizing five papers into a one-page literature map
You’ve read five papers on how moderation policies on online platforms affect user behavior, and you need a literature review section.
Build a concept matrix with the five papers as rows and these columns: platform studied, moderation intervention, outcome measure, method, primary finding, and limitation. Fill each cell with a phrase.
Now read down the columns instead of across the rows. Outcome measure might split into behavioral outcomes (post counts, users leaving) and linguistic ones (toxicity, civility): that’s a section of your review. Method might split into natural experiments and interview studies: another section. An empty region, say that nobody has measured behavioral outcomes after a policy change on a small platform, is a candidate gap for your own work.
The synthesis nearly writes itself. Paragraph one describes the scope of the literature, paragraph two where it agrees (the columns most papers fill the same way), and paragraph three where it disagrees or is silent. You haven’t done anything magical; you’ve made the structure visible.
25.13 Templates
A reading-note template you can paste at the top of every new note:
# {Paper title}
**Citation:** {full citation in your preferred style}
**Zotero key:** {citation key from Better BibTeX}
**Pass:** {1, 2, or 3}
**Date read:** {YYYY-MM-DD}
## One-sentence summary
(In your own words.)
## Claim
(What does the paper argue? Note the page: p. 14.)
## Evidence
(How is the claim supported? Methods, data, key results, each with its page.)
## Critique / gap
(What did they not address? What would you challenge?)
## Connections
- See also: {[[other-note]] or @sec-... or paper key}
- Cites: {key works the paper builds on}
- Cited by: {if known, key works that build on it}
## Quotes worth keeping
(Copied word for word, always in quotation marks, with the page.)
> "..." (p. 14)Two habits in that template will save you later. Note the page for every quote and claim (p. 14, or a section name for a web article without page numbers), so you can cite it without hunting and check it against the original. And anything you copy from the source keeps its quotation marks in your notes, even half a sentence. Months from now, when you’re drafting from these notes, an unmarked line looks exactly like something you wrote, and that’s a common way accidental plagiarism happens: not a decision to cheat, just a note that forgot where its words came from. When you paraphrase, write it in your own words from the start, and note the page anyway.
A literature-map concept-matrix template (paste into a new Markdown file and edit):
| Paper | Population | Method | Outcome | Theoretical frame | Finding |
|---|---|---|---|---|---|
| @key1 | ... | ... | ... | ... | ... |
| @key2 | ... | ... | ... | ... | ... |25.14 Exercises
- Apply Keshav’s first and second passes to an assigned paper. Write a one-page summary with the contribution in your own words, the method, the main finding, and one limitation.
- Set up a Zotero library with Better BibTeX and export a
.bibfile containing at least five papers on a topic you care about. - Pick an HCI paper and a data-science paper on similar topics. Write a 300-word note on how each genre privileges different kinds of evidence and contribution.
- Use Connected Papers to find five neighbors of a paper you’ve read. Identify the author who appears most often in the cluster, and do a first pass on their most recent paper.
- Find a paywalled paper and get a legal copy without paying: try your library’s links, Google Scholar’s “All versions,” and Unpaywall. Note which one worked.
- Annotate a publicly available paper with Hypothes.is. Share the link with a classmate and compare what you each highlighted.
25.15 One-page checklist
- Did you decide before reading what depth this paper deserves?
- Did you read the abstract, introduction, and conclusions before the body?
- Did you look at every figure and read every caption?
- Did you write a one-sentence summary in your own words?
- Does every line you copied into your notes keep its quotation marks and a page number?
- Did you check whether it was peer reviewed, whether it has been retracted, and how it measured its key variables?
- Did you save it to Zotero with the right tags and collection, and note its citation key?
- For second-pass papers, did you write a structured note (claim / evidence / critique / connections)?
- For third-pass papers, did you try to re-create the core method yourself?
- When you used an AI tool, did you check its summary, and every citation it gave you, against the real paper?
- Did you tag at least one connection to another paper or note?
25.16 Quick reference: matching reading depth to your goal
| Goal | How far to read | What you come away with |
|---|---|---|
| Decide whether to cite | Pass 1 (5–10 min) | A yes or no, and one line |
| Summarize for a literature review | Passes 1 and 2 (about an hour) | A short structured note |
| Replicate or build on the work | All three passes (4–5 hours at first) | Notes detailed enough to re-create it |
| Teach yourself a concept | Passes 1 and 2, or a review article instead | Notes you could teach from |
- S. Keshav, How to Read a Paper (ACM SIGCOMM Computer Communication Review, 2007) — the two-page article behind the three-pass method; worth re-reading before every literature search.
- Jane Webster and Richard T. Watson, Analyzing the Past to Prepare for the Future: Writing a Literature Review (MIS Quarterly, 2002) — the standard reference for concept-centric literature reviews in information systems and neighboring fields.
- Sönke Ahrens, How to Take Smart Notes (2017) — a popular modern guide to the Zettelkasten; a useful pairing with Zotero for serious reading habits.
- Zotero, Documentation — the official guide to the free, open-source reference manager, from browser connectors to group libraries.
- Jenny Bryan, Naming things — short slides on file-naming conventions that apply directly to the PDFs and notes files in a reading workflow.
- DOAJ, Directory of Open Access Journals — an index of vetted open-access journals; useful when you want to search journals that are free to read by default.
- ACM, Open Access Initiatives, and arXiv, About arXiv — two of the largest open-access channels for computing and information-science work; they pair with “Stakes and politics” above.