Learn

Book notes: a complete guide

The problem with reading without notes

Most people have read a book they found useful and then, six months later, could not recall a single specific idea from it. They remember the feeling of the book, the general territory, maybe a title or a name. But the specific insight, the argument, the thing that changed how they thought about something? Gone.

This isn't a failure of intelligence. It's just how memory works. The Curve of Forgetting suggests that within 24 hours of encountering information, we forget around 70% of it. Within a week, that rises to 90%. Reading without capturing is reading to forget.

Taking notes while you read doesn't solve this entirely, but it changes the equation significantly. Active reading, pausing to think about what you've just read and write it in your own words, is itself a form of processing that improves retention. And the notes become an external record you can return to, search, and build on, in a way that memory alone cannot.

What to capture

The goal isn't to summarise the book or copy out the best lines. It's to capture the ideas that are actually useful or interesting to you, in a way that will be meaningful when you return to them.

A few types of things worth capturing:

Ideas that change or challenge how you think. Not just ideas you agree with but ones that introduce a framework, a distinction, or a perspective you didn't have before.

Arguments you want to be able to reconstruct. If the book makes a case you'll want to use or argue with later, capture the logic, not just the conclusion.

Specific facts, data, or examples that are vivid and usable. Numbers, stories, comparisons that make abstract ideas concrete.

Questions the book raises. Things you don't know, things you're not sure about, things you want to follow up on.

Connections to other things you know. When an idea reminds you of something you've read elsewhere or an experience you've had, note the connection. These cross-references are often where the most useful thinking happens.

What you don't need to capture: anything that can be found easily by opening the book again, anything you already know well, anything that seemed interesting in the moment but doesn't connect to anything you care about.

How to read actively

Active reading means engaging with the text rather than receiving it passively. A few practices that help:

Mark as you read. Underline or highlight passages that seem important. Write in the margins: reactions, connections, questions. If you're reading a physical book you own, use it. If it's a library book or you prefer not to mark it, use sticky notes or a separate notebook. A PDF with annotations in a digital tool works well for this.

Pause at the end of sections. Before turning the page or moving to the next chapter, briefly recall what you've just read. What was the main point? Did anything surprise you? What questions does it raise? This brief pause is a form of retrieval practice that significantly improves retention.

Write in your own words. When you capture an idea, don't copy the author's sentence. Paraphrase it. If you can't express the idea in your own words, you probably haven't understood it yet, and writing forces you to find out.

Distinguish between summarising and thinking. A summary describes what the author said. A note that captures your thinking goes further: what do you make of it? What does it remind you of? What would need to be true for this to be wrong? The difference between a summary and a note that will be useful a year later is usually the presence of your own perspective.

Structure for different purposes

Different reading situations call for different note structures.

Reading to learn (courses, textbooks, professional development)

The Cornell method works well here. Main notes in the right column during reading, cues and questions in the left column during review, summary at the bottom after you've processed the page. The structured review is particularly valuable for material you need to retain for assessments or application.

Reading to research (gathering material for a project, paper, or piece of writing)

Keep source notes: for each book, record the bibliographic information (author, title, year, publisher), then your notes organised by the concepts in the book. When a passage is relevant to your research question, note the page number alongside it.

Group notes by theme or question rather than by book. If you're researching attention and focus, you want all your notes on attention in one place, not scattered across notes on five different books you happened to read in that order. The Zettelkasten principle of concept-oriented notes is particularly useful for research reading.

Reading to think (philosophy, essays, challenging nonfiction)

Less structure, more dialogue. Write responses to arguments. Push back where you disagree. Follow tangents. The goal is to think with the book, not just about it. These notes are often the most personal and the most valuable to return to.

Reading for pleasure (fiction, biography, memoir)

Most fiction doesn't benefit from elaborate note-taking, and trying to impose a system on pleasurable reading tends to make both the reading and the notes worse. For novels that move you, a brief note capturing what mattered about the book and why is usually sufficient. Specific passages, characters, or scenes that stay with you are worth noting. The question isn't "what did the book say" but "what will I carry from this."

A simple structure for non-fiction book notes

For most non-fiction, a one-page note per book (or per significant section of a longer book) that covers:

Basic info. Title, author, year. Where you encountered it and why you read it.

The main argument. One or two sentences summarising the book's central claim in your own words.

Key ideas. Three to five ideas from the book that you want to remember or use. Not a full summary; the ideas that actually matter to you.

Best passages. Two or three quotes that capture something important better than you could paraphrase. Fewer than that: a reminder to copy sparingly.

Your response. What do you think of the argument? What does it connect to? What questions does it raise? What do you want to follow up on?

Follow-up. Books, articles, or ideas the book points toward that you want to explore.

This structure can be completed in fifteen to thirty minutes after finishing a book, while the reading is still fresh. It produces a note that's actually useful when you return to it, unlike a pure summary, because it captures both the content and your engagement with it.

The progressive summarisation approach

Building a Second Brain uses a technique called progressive summarisation for reading notes: you take notes during reading (first layer), then highlight the most important parts of those notes during review (second layer), then bold the most important of the highlighted parts (third layer), and optionally write a summary in your own words at the top (fourth layer).

This produces notes that distil over time without losing the original material. The top layer is a quick reference; the full notes are there if you need more detail. Each layer can be added at a different time: initial notes during reading, first highlight pass a few days later, bolder pass before you need to use the material.

This works well for books you return to repeatedly or material you need to use in your work. For books you read once and move on from, the simpler one-page structure above is usually sufficient.

Making reading compound over time

The value of book notes compounds the same way the commonplace book or Zettelkasten traditions claim it does: each book you read connects to previous reading, and the notes make those connections explicit and findable rather than leaving them to chance memory.

A few practices that build this:

Link to existing notes. When a new book idea connects to something you've noted before, link the two. Over time, concepts that recur across books accumulate a richer picture than any single source provides.

Review before starting a related book. If you're about to read something on a topic you've read about before, spend ten minutes reviewing your existing notes first. This primes you to notice connections and disagreements that you'd miss if you came to the new book cold.

Use search by meaning rather than by title. When you need to recall what you've read on a topic, searching for the concept rather than trying to remember which book covered it is usually faster and more complete. "Notes on attention and focus" will surface passages from multiple books; remembering "I read something about this in that book about deep work" is less reliable.

Keep a reading list with brief notes. Not just titles but why you read each book and what you took from it. Goodreads works for this; so does a simple note. The list itself becomes a record of your intellectual development over time and a useful reference when recommending books to others.

Where book notes live

Book notes fit in a few places depending on your system:

In a PARA setup, notes on books related to active projects live in the relevant project folder. Notes on books that feed an ongoing interest live in Resources. Books you've finished and whose notes you no longer need for active work move to Archives.

In a Zettelkasten, literature notes (your notes on a specific source) are separate from permanent notes (your developed ideas). The literature note documents your encounter with the book; the permanent notes develop the ideas the book generated.

In Fabric, book notes alongside annotated PDFs and web clips from related articles create a unified library where everything is searchable together. The AI can synthesise across your reading in ways that browsing individual notes cannot.

Frequently asked questions

Should I take notes while reading or after?

Both have advantages. Notes during reading capture your immediate responses and catch details that fade quickly. Notes after reading force you to consolidate and recall, which improves retention. Most people find a combination works best: light marking during reading (underlines, margin notes), followed by a structured note session after finishing the book or a significant section.

How detailed should book notes be?

Detailed enough to be useful when you return to them, no more. Notes that are a complete summary of the book's content are probably too detailed: you've done the work of re-reading without the benefit of selection. Notes that are just "good book, thought-provoking" are probably too thin. The test is: if you came back to these notes in a year, would they tell you something useful you couldn't reconstruct from memory alone?

What about audiobooks?

Audiobooks make active annotation harder but not impossible. Voice memos work well for capturing reactions and ideas in the moment. Some audiobook apps allow highlighting or timestamping. After finishing a section, a brief spoken summary or a few written notes while the material is fresh is usually enough. The main challenge is pausing often enough to actually process rather than listening passively.

Do I need a special app for book notes?

No. Book notes work in any notes app, a physical notebook, or a spreadsheet. The format matters less than the habit. That said, tools with search, tagging, and links between notes make the notes more usable over time than a flat text file.

How do I stop highlighting everything?

By reading with the question "would I write this down?" rather than "is this interesting?" Everything in a good book is interesting. What you're looking for is what's actually useful or important to you specifically. If you're still highlighting too much, try writing notes instead: the constraint of having to summarise forces selectivity in a way that highlighting doesn't.