Get AI summaries of any video or article — Sign up free
Robert Greene And Ryan Holidays' note-taking system in Obsidian thumbnail

Robert Greene And Ryan Holidays' note-taking system in Obsidian

Joshua Duffney·
5 min read

Based on Joshua Duffney's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Separate project-specific notes into a dedicated Obsidian vault to prevent general knowledge from blending with writing work.

Briefing

A practical note-taking system for long-form writing is only useful if it stays aligned with the writer’s workflow—so the system should help a project “hold shape” instead of forcing the mind to constantly re-sort ideas. After months of using Zettelkasten-style methods (including Smart Notes) to organize research, the creator hit a capacity limit: general knowledge and project-specific notes started blending together until the project became hard to think about. The fix was to separate the writing effort into its own Obsidian vault and organize it using a Robert Greene / Ryan Holiday approach—built around research cycles, emergent themes, and a folder structure that mirrors how chapters take form.

Greene and Holiday’s research process begins with book structure. Once the outline’s parts are defined, research starts: books are read carefully, marked up heavily, and notes are taken in batches. The key rhythm is time-based filtering—notes are captured, then the material “sits” long enough for weaker ideas to fall away. After that, notes are produced in a focused session spanning multiple days. The creator reports that strong books typically yield around 20–30 notes, with fewer notes often correlating with lower note-taking payoff (not necessarily worse reading).

Instead of building a bottom-up knowledge graph, the system uses a top-down container first: three project “parts” (Part 1, Part 2, Part 3). New notes land in the vault root as a queue—analogous to stacking index cards before sorting them into boxes. As research accumulates, themes emerge naturally. Once a theme becomes clear, notes are dragged from the part folders into theme subfolders that can later become chapters or sections. A concrete example comes from reading Nicholas Carr’s The Shallows: after taking roughly 30 notes about neuroplasticity and how the internet differs from other media, the creator groups them under a “shallowing of the mind” theme, ready to become a chapter or section when writing begins.

The same structure supports later thematic development. After Cal Newport’s A World Without Email, the creator’s Part 3 theme becomes “Working the Depths” (working title), with a broader “Life of Less Convenience” / digital minimalism thread. Notes from Newport’s ideas also spawn sub-themes such as “Escape Your Inbox,” which then branches into practical concerns like task boards, improving meetings, and communication overload.

To make retrieval and citation reliable, each source gets a dedicated reference note. For each book or article, the reference note stores bibliographic metadata (author, title, publisher, publish date, ISBN, and editions) and links to all notes taken from that source. Notes follow templates and types: summary notes, paraphrases, and quotes. Quotes are formatted using a community plugin (Adminer/“admin nation” as referenced), which creates clean quote callouts.

Finally, the workflow borrows from software engineering: a Kanban board tracks reading and research progress. Columns include Backlog (prioritized reading), Ready (next up), Doing (currently paused for meta-learning on research craft), Waiting (e.g., “Escape Your Inbox” chapter work), and Done (e.g., Perennial Seller once notes are completed). The result is a system that helps the writer re-enter the project quickly, pause without losing context, and use folder-based bucketing to turn research into an outline for drafting.

Cornell Notes

The core shift is separating project notes into a dedicated Obsidian vault and organizing them with a Greene/Holiday workflow rather than a bottom-up knowledge graph. Research starts after the book’s parts are sketched, then books are read carefully, marked up, and followed by batched note-taking sessions that allow time to filter out weaker ideas. Notes begin in a root “queue” and get sorted into Part 1–3 folders; as enough notes accumulate, themes emerge and are dragged into theme subfolders that can later become chapters or sections. Each source gets a reference note with full bibliographic metadata and links to all related notes, using templates for summaries, paraphrases, and quotes. A Kanban board adds a progress layer—tracking what to read, what to take notes on, and what chapters are waiting to be written—so the system supports writing momentum instead of overwhelming the mind.

Why did the writer abandon Smart Notes/Zettelkasten-style organization for this project?

The main bottleneck was cognitive capacity: project-specific notes (writing process, life, programming learning) started blending together with general knowledge. Once notes couldn’t be compartmentalized cleanly, the project became hard to “hold” mentally, leading to seized-up thinking. The workaround was to move all project notes for the current book into a separate Obsidian vault and use a Greene/Holiday-style structure that matches how chapters form.

What does the Greene/Holiday-inspired research rhythm look like in practice?

First, the book’s structure is sketched so there’s a “bucket” for later notes. Then research begins with careful reading and heavy markup, including margin notes. After reading, notes are allowed to “sit” so time helps filter the best ideas. Finally, note-taking happens in batches over focused sessions spanning multiple days; the creator reports that strong books often yield about 20–30 notes, with fewer notes typically indicating less note-taking payoff.

How does the system turn scattered notes into an outline?

Notes start in the vault root directory as a queue (like stacking index cards before sorting). As research continues, themes emerge from skimming and grouping. Notes are dragged from Part folders into theme subfolders (e.g., “shallowing of the mind” from The Shallows). Those theme folders are treated as potential chapters or sections, even if the exact structure isn’t fully known yet.

What role do reference notes and templates play in retrieval and citation?

Each consumed source gets its own reference note containing bibliographic metadata (author, title, publisher, publish date, editions, ISBN). Individual notes link back to that reference and include page numbers for pinpointing. The creator uses templates for three note types: summary, paraphrase, and quote. Quotes are formatted with a community plugin that produces clean quote callouts, improving readability and organization.

How does the Kanban board support the research workflow beyond note storage?

The Kanban board tracks reading and processing status. A Backlog column holds prioritized reading items; Ready lists what will move next into Doing. Waiting marks work that’s not yet active (like a chapter still to be written), and Done captures completed items (e.g., a book once notes are finished). The creator also uses it during hiatuses for meta-learning about research craft, keeping progress visible even when writing pauses.

Review Questions

  1. How does the vault’s three-part structure (Part 1–3) change the way themes are formed compared with a bottom-up graph approach?
  2. What specific metadata and linking strategy makes reference notes useful when revisiting ideas later?
  3. In what ways does batching note-taking and allowing time to “sit” affect the quality of notes produced?

Key Points

  1. 1

    Separate project-specific notes into a dedicated Obsidian vault to prevent general knowledge from blending with writing work.

  2. 2

    Start with a high-level outline (three parts) so notes have a place to go before themes fully form.

  3. 3

    Use a root “queue” for new notes, then sort into part folders and later into theme subfolders as patterns emerge.

  4. 4

    Adopt source reference notes with full bibliographic metadata and link every note back to its source plus page numbers.

  5. 5

    Standardize note types with templates (summary, paraphrase, quote) to make retrieval and reuse faster.

  6. 6

    Track research progress with a Kanban board so reading, note-taking, and chapter writing states stay visible.

  7. 7

    Batch note-taking sessions and let ideas sit briefly to improve signal-to-noise before committing to themes.

Highlights

The system’s organizing principle is not building a knowledge graph; it’s using file/folder bucketing so themes emerge from accumulated notes and can directly become chapters.
Each source gets a dedicated reference note with bibliographic data (including ISBN) and links to all derived notes, with page numbers for fast re-checking.
A Kanban board turns research from an open-ended task into a visible pipeline: Backlog → Ready → Doing → Waiting → Done.
The creator reports a practical yield of about 20–30 notes from strong books, using note volume as a rough proxy for note-taking payoff.
Time-based filtering—reading, marking up, then letting material sit before batching notes—helps discard weaker ideas before they clutter the system.

Topics