My FULL Zettelkasten & Obsidian Workflow

TL;DR

Start with a Vault and decide on a backup strategy (cloud storage plus frequent backups, or Obsidian Sync if you want automatic syncing).

Briefing Cornell Notes

Briefing

A practical Zettelkasten workflow in Obsidian hinges on one decision: treat notes as a pipeline. Capture ideas fast in “fleeting notes,” store references in “literature notes,” and convert only the most useful insights into short, atomic “permanent notes” that link to related ideas. The payoff is a system that turns reading and brainstorming into reusable knowledge—without drowning in clutter or endless customization.

The setup starts with building an Obsidian Vault and choosing where it lives. The workflow recommends keeping the Vault on a cloud drive (iCloud, Google Drive, or OneDrive) and creating backups regularly; if someone wants automatic syncing across devices, Obsidian Sync is positioned as an option because Obsidian keeps data local rather than hosting it elsewhere. Once the Vault is created, the welcome file can be removed and the default location for new notes can be redirected so new entries land in the fleeting notes folder automatically.

Three core folders anchor the method. Fleeting notes act as an inbox: a stream of consciousness for thoughts, opinions, and anything found online or offline, with no links and no structure. Literature notes become the reference library for consumed material—books, articles, courses, lectures, and podcasts—organized into subfolders and tagged with broad categories (e.g., psychology, philosophy, reading, focus). These notes can include outlines (such as chapter-by-chapter structure for books) and dates to track when learning happened.

Permanent notes are where “magic happens,” but only after selection. The guidance is strict: keep permanent notes atomic—short enough that they don’t require scrolling—and avoid copy-paste. Instead, ideas should be rewritten in the note-taker’s own words to ensure understanding and to expose knowledge gaps. Each permanent note includes a brief explanation, a connections section that links to similar or even opposing ideas (to reduce confirmation bias), and a references section that stores sources. A quick test for clarity is whether someone else could understand the note without context.

In practice, the workflow is demonstrated using a book (Hyperfocus by Chris Bailey). The reader first records the book’s chapter outline, then creates separate permanent notes only for concepts worth reusing—such as “four types of tasks.” Notes are tagged, connected to related frameworks (for example, linking to the Eisenhower Matrix), and optionally annotated with page numbers for fast retrieval. Kindle highlights can be stored at the bottom as additional raw material, while the permanent notes remain the curated knowledge base.

The system also adapts beyond the classic three-folder model. The organizer keeps extra folders for content creation (video scripts and ideas), unsorted items, attachments (images and PDFs), clippings saved via an Obsidian Chrome plugin, daily/weekly/monthly reviews, planning, templates, and “rating” mini-essays. To avoid common beginner traps, the workflow emphasizes learning Markdown basics, resisting plugin overload, and using Obsidian primarily for note-taking rather than turning it into a calendar, habit tracker, or full task manager.

Finally, graph view is treated as a feature—not a gimmick. It helps visualize clusters of connected ideas, spot orphan notes, and use local graph views to focus on specific topics. The overall message is to start immediately, iterate based on what works, and let the knowledge network grow through linking and selection rather than passive consumption of tutorials.

Cornell Notes

The workflow builds a Zettelkasten system inside Obsidian as a pipeline: capture in Fleeting Notes, store sources in Literature Notes, and convert only high-value insights into short, atomic Permanent Notes. Fleeting Notes stay unstructured and link-free, acting as an inbox for raw thoughts and materials. Literature Notes organize consumed content (books, articles, podcasts, etc.) with tags, dates, and often outlines to preserve context. Permanent Notes must be rewritten in the note-taker’s own words, kept short enough to avoid scrolling, and enriched with a connections section (including opposing ideas) plus a references section. This structure turns reading into reusable knowledge and makes graph view useful for spotting clusters and orphan notes.

Why are fleeting notes intentionally unlinked and unstructured?

Fleeting notes function as an inbox for “everything that comes into my mind.” The guidance is to treat them as a capture stage: thoughts, opinions, and items found online or offline get dumped there without connections. The system assumes most of these entries will later be deleted or processed into permanent notes, so forcing structure early would slow down capture and clutter the Vault.

What makes a permanent note “atomic,” and why does that matter?

Atomic notes are short—ideally so short the reader doesn’t need to scroll. The goal is to keep each permanent note focused on a single idea that can be reused and linked. This also supports clarity: when notes are brief and precise, connections become easier to manage in Obsidian’s linking and graph view.

Why avoid copy-paste when creating permanent notes?

Copying highlighted text from books is discouraged because it can mask misunderstanding. The workflow recommends rewriting concepts in the note-taker’s own words, which acts like self-testing: if the idea can’t be explained clearly, gaps in understanding show up. The note should also be readable by someone else without needing the original book context.

How do connections and opposing ideas improve the quality of notes?

Permanent notes include a connections section that links to similar ideas and also to opposing ideas. The explicit reason is to avoid confirmation bias—if only matching viewpoints are linked, the knowledge base becomes one-sided. Linking to contrasting ideas improves the system’s accuracy and usefulness for later content creation.

How does the workflow handle references and retrieval?

Each permanent note includes a references section (“sources”) where related materials are stored—books, articles, and even connected works mentioned by other books. For retrieval, the workflow suggests adding page numbers next to notes (e.g., “page 60”) so the concept can be found quickly in the original source later.

What role do plugins and graph view play in this system?

Plugins are kept minimal to prevent distraction and customization fatigue. The workflow lists a small set (e.g., natural language dates, outliner, periodic notes, reading time, recent files, and a Chrome clippings plugin), but warns against turning Obsidian into a content calendar or habit tracker. Graph view is treated as a core tool: it reveals clusters of connected ideas, helps identify orphan notes, and supports local graph views for deep dives.

Review Questions

What criteria determine whether an idea moves from fleeting or literature notes into a permanent note?
How would you structure a permanent note so it stays atomic, understandable to others, and link-ready?
What are two ways graph view can help maintain a healthy knowledge base (e.g., spotting clusters or orphan notes)?

Key Points

1
Start with a Vault and decide on a backup strategy (cloud storage plus frequent backups, or Obsidian Sync if you want automatic syncing).
2
Use Fleeting Notes as an inbox: capture quickly, keep it unstructured, and avoid linking until ideas are selected.
3
Organize Literature Notes as a reference library with tags, dates, and outlines when helpful, but don’t force rigid structure if it becomes clutter.
4
Create Permanent Notes only for high-value concepts, keep them atomic (short, no scrolling), and rewrite in your own words instead of copy-pasting.
5
Add a connections section to link both supporting and opposing ideas to reduce confirmation bias.
6
Store sources in a dedicated references section and optionally record page numbers for fast retrieval.
7
Limit plugin use to essentials and rely on graph view to visualize clusters and find orphan notes.

Highlights

Permanent notes should be atomic and rewritten in your own words; copy-pasted highlights are treated as unreliable for understanding.

Fleeting notes are intentionally link-free—raw capture happens first, and selection happens later.

Connections aren’t just “related ideas”; linking opposing viewpoints is used to fight confirmation bias.

Graph view is positioned as a practical diagnostic tool for clusters and orphan notes, not a decorative feature.

Topics

Mentioned

Chris Bailey