Most researchers have accumulated, somewhere in their file system or note-taking tool of choice, a collection of notes from projects that were completed months or years ago. These notes contain real research: reading done carefully, judgments formed, specific passages extracted. And yet, when the researcher returns to them for a related project, the notes are frequently unusable. Not because the content is gone, but because the context in which the content made sense is gone.
A note that says "interesting counterpoint to the standard argument" means something specific on the day it was written, when the researcher had the standard argument loaded in working memory and could immediately understand what the counterpoint was countering. Three months later, it means nothing. The content of the note is identical. Its usefulness has dropped to zero.
Notes Are Written in Context, Not in Isolation
The abandonment of research notes is rarely a failure of organization. Notes do not get abandoned because they are filed in the wrong folder or tagged incorrectly. They get abandoned because they were written with an implicit context that no longer exists when the researcher returns to them.
When a researcher writes a note during active engagement with a source, they have access to three things that they do not record in the note. They have the full source available in front of them, providing context for any quotation or paraphrase. They have the question they were trying to answer loaded in working memory, providing context for why the source was relevant. And they have the structure of the larger project in mind, providing context for where the source's contribution would fit.
Notes written against this background tend to be elliptical. They record the conclusion of a judgment without recording the reasoning behind it. They indicate that something is relevant without recording why. They point to a passage without explaining what work the passage was supposed to do. At the time of writing, this is efficient. The researcher does not need to write down what they already know. But the knowledge that makes the note legible is held in working memory, not in the note, and when that working memory is cleared, the note loses much of its meaning.
The Decay Curve
The usability of a research note is not constant over time. It decays, and the rate of decay depends on the type of context the note depended on.
Notes that depended primarily on the content of the source (quotations, specific data points, the paper's main claim) retain their value well. The source content does not change, and the note can be checked against the source if needed. These notes are genuinely reusable across projects because their meaning is anchored to something external and stable.
Notes that depended on the researcher's current question (why this matters, what argument it supports, what it counters) decay much faster. The question changes. The argument structure evolves. What seemed like a counterargument on one project may be irrelevant or even supportive on the next. These notes require the researcher to reconstruct the original reasoning, and if that reasoning was not recorded, reconstruction may be impossible.
Notes that depended on implicit connections between sources decay fastest. "This contrasts interestingly with the earlier paper" records a comparison that existed in the researcher's mind at the time but was not fully articulated. Without the earlier paper in mind, and without knowing which earlier paper is meant, the note is uninterpretable.
The Note-Taking Trap
The behavior pattern that leads to abandoned notes is entirely rational at the moment of writing. Taking thorough notes feels like it is taking too long relative to the reading. Adding context to every note, explaining why a passage was extracted and what work it will do in an argument, feels like unnecessary writing. The researcher is already writing the paper in their head; writing it again in the notes seems redundant.
This is the trap. The note is not written for the researcher who is currently reading, who has all the context in working memory. It is written for the researcher who will be writing weeks or months later, who has none of that context. The audience for a research note is the future self, not the present self, and the present self consistently underestimates how much context the future self will need.
The result is a large collection of notes that represent real intellectual work but cannot be used without re-reading the sources. The notes act as a reading list rather than a research resource. They remind the researcher that they read something relevant, but they do not transfer the judgment formed during that reading into a form the future researcher can work from directly.
What Makes Notes Reusable
The characteristic that distinguishes reusable notes from abandoned ones is almost never the depth of the note or the quality of the summary. It is whether the note records the judgment alongside the content.
A reusable note contains: the specific claim or passage from the source, the question the source was gathered to address, and the specific argumentative function the researcher intended the source to serve. These three elements together preserve enough context to reconstruct the original judgment without re-reading the source.
This standard is higher than what most researchers apply in practice. It requires writing two or three sentences of context for what might otherwise be a one-sentence extraction. For a 30-source project, this represents a substantial additional annotation effort, perhaps 30-50 minutes of writing spread across the reading phase.
The return on this investment appears later: faster drafting, less re-reading, and notes that remain genuinely useful not just for the current project but potentially for related work years later. For researchers who work in the same area repeatedly, or who build on earlier projects, the compounding value of reusable notes can be significant.
The Cross-Project Reuse Problem
Even notes written with sufficient context for their original project often fail at cross-project reuse, because the argumentative function they were assigned was specific to the original project's structure. "Supports the third mechanism in section 4" is useful context for project A and useless for project B, which has a different structure and different sections.
Cross-project note reuse requires a different kind of annotation: notes written in terms of the source's content and claims, independent of any particular project's structure. A note that says "argues for X on the basis of Y, with Z caveat, using a longitudinal study design" can be applied to any project that needs that claim. A note that says "good for section 4" cannot.
Most researchers do not distinguish between these two annotation styles, not because they are unaware of the difference, but because during active project work the project-specific frame is always present and it requires discipline to step back from it and annotate in project-neutral terms.
The Design Response
When we were building Pilgrim's annotation layer, the abandoned-notes problem shaped several design decisions. The annotation interface prompts for the question the source addresses alongside the specific claim, not just the claim in isolation. Sources stay connected to the question they were gathered under, so returning to a project weeks later presents the sources in question-first order rather than reading-order.
We are not under the illusion that this solves the problem entirely. The fundamental issue is that full context preservation requires more effort at annotation time than most researchers will invest consistently. What we can do is make the minimum viable annotation lower-friction, so that the context that is most likely to matter later, the question and the claim, is captured without requiring the researcher to think explicitly about what their future self will need. The habit is what matters. The tool can support the habit, but it cannot substitute for it.