Obsidian for Learning Part II: Process

The video argues that most note-taking guides ignore the crucial "after" stage of the system—how to actually process and use notes once they are taken. The core philosophy is to build a single trusted system with one storage location and reliable daily processing, avoiding fragmented apps and unmanaged backlogs. The method uses atomic notes (Zettelkasten/FLAP) that are loosely coupled and combinable, but organized hierarchically through an up property rather than graph views, which don't scale. A unique feature is applied spaced repetition to review fleeting notes, rating them as good, medium, or hard, with instant actions for quick tasks and snoozing for ambiguous items, ensuring the backlog shrinks sustainably. Literature notes and highlights are transformed into atomic notes by referencing quotes and linking concepts, with a final check-off to mark processing complete. The system is presented as sustainable and scalable, with project time-boxing covered in a follow-up video.

• ▶ 0:06 Most note-taking guides miss the crucial "after" stage—what you actually do with your notes once they're taken, which is the central question of the system.

• ▶ 1:00 The system is built on atomic notes (Zettelkasten/FLAP) that are highly composable and cohesive but loosely coupled, so each note stands alone yet combines easily into essays.

• ▶ 2:39 Graph views don't scale—the original linear card-file metaphor works best, where you browse by thumbing through cards and titles, not by staring at a crowded node graph.

• ▶ 5:45 The core philosophy is to build a "single trusted system" for notes, a phrase borrowed from David Allen's Getting Things Done, requiring two vital components: a single storage location and reliable processing.
• ▶ 6:07 Storing fleeting notes in multiple places creates uncertainty and mental friction — like "five apps with screenshots of the other four on" — so you must commit fully to one trusted system.
• ▶ 6:48 The processing has two main parts: fleeting notes are rewritten into atomic notes (keeping the original wording and tagging as atomic), and unfiled literature notes are linked from those new atomic notes and retagged as literature.
• ▶ 7:15 Daily processing is critical, especially for fleeting notes, which carry a “temporal contract” where today’s you must handle what yesterday’s you jotted down.
• ▶ 7:36 Processing every highlight or note can become overwhelming, and when interests change, conventional refiling into lists or tags often spirals into an unmanageable backlog.
• ▶ 8:19 The proposed solution is a better method based on spaced repetition—reviewing items over time to flatten the forgetting curve—and is used to manage the fleeting note backlog.
• ▶ 9:44 Review only fleeting notes (not atomic notes) using the Spaced Repetition plugin, rating each as good, medium, or hard, which controls when it resurfaces.
• ▶ 10:19 For a small task like “ask Mom when she is free,” immediately do it if it takes under 2 minutes, then delete the note; if it belongs to another context (e.g., “buy oat milk”), copy/paste it into the relevant project note before deleting.
• ▶ 11:03 If a fleeting note is ambiguous, don’t stress — simply snooze it by rating it as easy (or “later”), letting the plugin schedule it for a future review automatically.
• ▶ 11:56 After repeated processing, the list shrinks to only hard/urgent notes; at that point, slow down and either complete, file, research, or delete them, since the system is designed to scale sustainably.
• ▶ 12:47 Capture other people’s words from lectures, talks, and videos, and while fresh expand them into atomic notes or tasks.
• ▶ 13:43 File each new atomic note behind exactly one other note using an up property to build a clear Zettelkasten tree, not a loose folder or graph.
• ▶ 14:24 Store verbatim knowledge (names, addresses, code, facts) as simple tagged notes for retrieval; at ▶ 14:53, process highlights into atomic notes by referencing the original quote and linking related concepts.
• [15:35-15:51] The new atomic note is slotted into the Zettelkasten by linking a related thought in the up property, anchoring it in the note tree.
• [15:51-16:02] Atomic notes need only two organizational features: related notes via normal links and an anchor parent via the up property.
• [16:03-16:30] The final processing step is checking off the highlight to mark it fully processed; the system is now two-thirds complete, with time-boxed projects covered in the next video.

• ▶ 0:01 Introduction and System Overview (0:01 - 5:28) - - Introduces the video, public-domain resources, atomic notes/Zettelkasten/FLAP, why card files beat graphs, note anatomy, the three-part system, and Obsidian setup.
• ▶ 5:28 Sponsor and the Single Trusted System (5:28 - 7:15) - - Covers the sponsor, the daily distilling practice, and processing raw notes into atomic notes in one trusted system.
• ▶ 7:15 Daily Processing and Spaced Repetition (7:15 - 9:29) - - Emphasizes daily processing, adapting to changing interests, using spaced repetition, and highlights the plugin and support options.
• ▶ 9:29 Demo: Processing Tasks and Fleeting Notes (9:29 - 12:47) - - Runs the plugin, handles tasks, snoozes ambiguous notes, reviews plugin changes, and routes deferred tasks to projects or notes.
• ▶ 12:47 Expanding Thoughts, Verbatim Knowledge, and Highlights (12:47 - 15:39) - - Covers capturing others' words, expanding fleeting thoughts into atomic notes, storing verbatim knowledge, and processing highlights.
• ▶ 15:39 Final Organization and Wrap-Up (15:39 - 17:10) - - Slots new atomic notes into the Zettelkasten, recaps the process, and closes with support and link information.