How to Take Book Notes: A Digital System (feat. Obsidian & Readwise)

TL;DR

Use Kindle (or another syncing reader) so highlights and notes can be captured digitally and later exported reliably.

Briefing Cornell Notes

Briefing

A practical two-app workflow—Readwise plus Obsidian—turns Kindle highlights into a searchable, actively learned knowledge base instead of a pile of pasted quotes. The core idea is to centralize every highlight and note while reading, export them into Obsidian with precise source locations, then add your own chapter-level summaries from memory to strengthen recall and deepen understanding.

The system starts with reading on a device that syncs highlights cleanly, such as a Kindle. As the reader encounters passages worth keeping—new learning, strong quotes, or ideas that connect to earlier thoughts—they highlight sentences or write short prompts (for example, tagging a connection like “topic X”). Those saved highlights and notes become the raw material for later refinement.

Readwise sits in the middle. It connects to many reading and capture services (including Kindle, Twitter, Instagram, Pocket, and paper-based workflows) and centralizes highlights and notes into one place. Just as important, it can export that collected material into note-taking or knowledge-management tools. While Obsidian is the example used here, the same pipeline can be applied to other systems such as Notion, Roam, or Evernote.

Once exported, Obsidian receives a structured “raw output” for each book: the title, author metadata, tags, and a section containing the highlights. A standout feature is location sourcing—each highlight is tied to the exact page or location where it was captured. That means a reader can click back to the original spot in the Kindle app to verify context, skim around the quote, or revisit the surrounding argument.

The workflow then shifts from collection to learning. Instead of leaving highlights as a long paste of quotations, the reader adds chapter summaries. After finishing each chapter, they stop, open a note, and write a short summary from memory under the chapter heading—referencing key topics that emerged. Only after that recall attempt do they fill gaps by returning to the original quotes and notes. This is framed as active recall (and the testing effect), aiming to improve memory, clarify understanding, and make stronger connections across ideas.

Finally, the process culminates in book-level organization. With chapter summaries already in place, the reader returns to the full book note to extract overarching themes and write a general summary. They also add “concept notes” as related ideas appear across other books—building a growing web of linked concepts over time. The approach is presented as adjustable: if the goal is pure enjoyment or quick nuggets, highlights alone may be enough; if the goal is deeper retention and synthesis, the extra summarization and linking work can pay off.

Cornell Notes

The workflow pairs Readwise with Obsidian to turn Kindle (and other sources) highlights into a structured knowledge base. Readwise centralizes saved highlights/notes from many services and exports them into Obsidian, preserving metadata and the exact source location for each highlight. In Obsidian, highlights arrive as raw pasted material, but the system becomes more valuable when chapter summaries are written from memory after each chapter. That recall step—then gap-filling by checking quotes—uses active recall to strengthen understanding and retention. Over time, book-level themes and linked concept notes create an expandable reference system for future reading.

Why does the workflow rely on Readwise before Obsidian?

Readwise acts as a hub that collects highlights and notes from multiple reading/capture services (including Kindle, Twitter, Instagram, paper workflows, and Pocket). It then exports that collected material into a note-taking or knowledge-management app. In the example, Obsidian receives the exported book notes with structure (title, author metadata, tags) and with each highlight tied to its exact source location so it can be revisited in the Kindle app.

What does “raw output” in Obsidian look like after exporting from Readwise?

After export, Obsidian shows a book note containing the book title, author metadata, tagging, and a section that includes essentially every highlight from the book. Each highlight is sourced to the precise location where it was captured, and clicking it can jump back to the corresponding page or location in the Kindle app for context.

How do chapter summaries improve the value of highlights?

Highlights alone can become a long list of quotes that’s harder to use later. The workflow adds a step: after finishing a chapter, the reader writes a short summary from memory under that chapter heading, referencing key topics that appeared. Only afterward do they check the original highlights/notes to fill in missing details, which both clarifies understanding and organizes the material around chapters.

What learning mechanism is used to justify writing summaries from memory?

The method is tied to active recall and the testing effect: forcing retrieval from memory strengthens retention. The process is: stop reading at chapter end, write what was understood without looking back, then return to quotes to correct and complete the summary.

How does the system evolve from chapter notes into a long-term knowledge base?

Once chapter summaries exist, the reader creates a book-level synthesis: identifying key themes and writing a general summary that links to other ideas. They also add concept notes when related ideas appear in other books (for example, creating notes for concepts like deliberate practice or a “metric black hole” reference). This builds a network of linked concepts that’s easier to reference later.

Review Questions

What specific feature of Readwise export makes it easier to revisit the original context of a highlight?
Describe the sequence used after finishing a chapter to apply active recall.
How does the workflow differ between using highlights only and using chapter summaries plus book-level synthesis?

Key Points

1
Use Kindle (or another syncing reader) so highlights and notes can be captured digitally and later exported reliably.
2
Highlight key sentences or quotes while reading, and optionally add short prompts (e.g., “topic X”) to preserve the connection you’re making.
3
Centralize highlights and notes in Readwise, which can pull from multiple sources and export into a chosen knowledge system like Obsidian.
4
In Obsidian, preserve the benefit of location sourcing by clicking highlights to jump back to the exact Kindle page or location when you need context.
5
After each chapter, write a short summary from memory before checking notes to strengthen recall and understanding.
6
Finish by synthesizing across the whole book: extract overarching themes, add general summaries, and create or expand linked concept notes over time.
7
Adjust effort to the goal: highlights may be enough for enjoyment, while deeper summarization and linking support retention and synthesis.

Highlights

Readwise exports book highlights into Obsidian with exact source locations, letting readers jump back to the precise Kindle page for context.

The workflow’s main upgrade over pasted highlights is chapter summaries written from memory, then corrected using the original quotes.

Book-level notes become more useful when themes are synthesized across chapters and linked concept notes are added as new ideas appear.

The method is intentionally not one-size-fits-all: it scales from lightweight quote capture to deeper retrieval-based learning.