How long should literature notes be?
Based on Martin Adams's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Treat literature notes as atomic building blocks: one core idea per note, written in the reader’s own words and understanding.
Briefing
Literature notes stay manageable when they’re treated as atomic building blocks—single ideas written in the reader’s own words that can stand alone and be linked precisely. The core problem is notes that swell into long, book-sized chunks, which then become hard to retrieve, hard to explain from memory, and awkward to connect to other ideas. The fix is to enforce a boundary: if a section can be pulled out and still make sense on its own, it deserves to be its own note; if it can’t, the note is either too vague or too broad and needs to be split.
The discussion frames two common workflows for organizing notes. One approach groups everything under a single title—useful for fleeting notes meant for rapid capture, later broken into literature notes. The other approach creates new notes as each idea emerges, producing many smaller entries from the start. Neither method is inherently wrong; the real challenge is managing note size and granularity. Tooling can help with this “fluidity,” because software that makes it easy to break information into smaller units reduces the temptation to keep everything in one growing document. The transcript contrasts this with systems like Obsidian, where the user must be more deliberate about splitting and structuring.
A practical example centers on Angela Duckworth’s book “Grit.” A book often contains one core theme reinforced through stories and references, but other books range across subjects or go deep on a single topic. The temptation is to create one large literature note—rewriting the entire book’s key points into a note titled “Grit by Angela Duckworth.” The problem is that literature notes are meant to translate what was learned into the reader’s own understanding, not just preserve recognizable phrasing from the text. Without that translation, recall becomes shallow: it’s easier to recognize ideas when reading than to reproduce them when explaining or writing.
The transcript then addresses a second granularity issue: duplication. If multiple sections of the book express the same underlying idea, creating separate notes for each instance can lead to redundancy. The guidance is to keep the best version and disregard the second when it adds no new value.
Under the Zettelkasten-inspired “smart notes” mindset, atomic notes function like index cards: each note expresses one core idea, written so it makes sense in isolation. Equally important, literature notes should reference other notes or sources that support why the understanding is held—so linking works at the level of specific claims, not at the level of an entire book that won’t be reread. The boundary rule is straightforward: the moment a note starts combining multiple ideas, it’s a red flag that it’s too large and should be broken down for better organization and more useful linking.
Cornell Notes
The transcript argues that literature notes should be kept atomic—each note should capture one core idea in the reader’s own words and make sense on its own, like an index card. Two workflows are described: grouping material under a single title first, or creating new notes as each idea appears; neither is inherently wrong, but note size depends on how well the system helps split ideas. A literature note is valuable because it supports recall and explanation from one’s own understanding, not just recognition of the original text. When a note starts containing multiple ideas, it’s too big and should be divided; if two notes express the same idea, redundancy can be removed by keeping the more useful one. Atomic notes also improve linking by letting connections target specific claims rather than whole books.
What makes a literature note “atomic,” and why does that matter for retrieval and explanation?
How do the two note-creation mindsets differ, and what’s the practical challenge they share?
Why does the transcript use “Grit” as an example, and what decision does it force about note boundaries?
What should happen when two parts of a book seem to express the same idea?
What’s the “red flag” for note size, and how does it affect linking?
How do literature notes relate to references and support?
Review Questions
- When does a note become “too big” under the atomic-note rule, and what specific action should follow?
- Why does writing literature notes in one’s own words improve the ability to explain ideas to someone else?
- How should redundancy be handled when two notes end up expressing the same underlying idea?
Key Points
- 1
Treat literature notes as atomic building blocks: one core idea per note, written in the reader’s own words and understanding.
- 2
Use a boundary rule: if a section can stand alone and still make sense, it can be its own note; if not, the note is too broad or unclear.
- 3
Avoid multi-idea notes; the moment multiple ideas appear in one entry, split it into separate notes.
- 4
When two notes express the same idea without adding new value, keep the better one and discard the redundant one.
- 5
Link at the level of specific claims: atomic notes make linking useful, while book-sized notes are too coarse to connect effectively.
- 6
Literature notes improve recall and explanation because they translate recognition of text into reproducible understanding.