Zettelkasten Implementation in Obsidian

Overview

The Zettelkasten method in Obsidian is a bottom-up, digital slip-box system for lifelong knowledge management that replaces top-down folders with networked, atomic notes.

Core Principles

Atomic Notes

Each note contains exactly one idea or concept:

• Easy to rearrange and link
• Maximum reusability
• Clear, focused content

Test: Can you summarize the note in one sentence? If not, it’s too long.

Unique Identification

Notes use either:

• Zettelkasten ID: YYYYMMDDHHMM (e.g., 202602011430)
• Descriptive titles for human readability

Wiki-Linking

The core of the method is connecting notes:

• Use double-bracket wiki-links to create connections
• Web of ideas rather than rigid hierarchy
• Links create emergent structure

Three-Tier Note Workflow

Step 1: Fleeting Notes (Capture)

• Quick, zero-friction recording
• Goes in 00_Inbox folder
• No formatting required
• Mobile app or daily note capture

Step 2: Literature Notes (Process)

• Summarize external content (books, videos, articles)
• Use your own words (no copy-paste)
• Goes in 10_Literature folder
• Can use Readwise/Zotero plugins for automation

Step 3: Permanent Notes (Distill)

• Extract single insights in your own words
• Goes in 20_Permanent folder
• One Note, One Idea Rule: Split if multiple concepts
• Building blocks for future work

Vault Architecture

Minimal folder structure (4 folders):

vault/
├── 00_Inbox/        # Fleeting Notes
├── 10_Literature/   # Source summaries
├── 20_Permanent/    # Atomic insights
└── 90_Assets/       # Images, attachments

Connection Engine

Creating Links

Every Permanent Note should ask: “What does this remind me of?”

1. Search vault for related concepts
2. Link to at least two other notes
3. Use backlinks to find context

Backlink Check

Enable Backlinks pane:

• Shows which notes reference current note
• Check “Unlinked Mentions” for implicit connections
• Convert mentions to explicit links

Graph View

Weekly review of Graph View:

• Dense clusters = expertise areas
• Isolated nodes = needs integration or research
• Orphans should be connected or archived

Maintenance & Scaling

Weekly Inbox Zero

Every week:

• Process all fleeting notes
• Delete or promote to Literature/Permanent
• Clear inbox completely

Maps of Content (MOCs)

When topic reaches 15-20 notes:

• Create index note
• Link all related notes in logical order
• Provides narrative structure

Success Metrics

Metric	Target
Atomic	Summarizable in one sentence
Linked	Minimum 2 links per note
Own words	Not copied from source
Inbox	Cleared weekly

Obsidian Features for Zettelkasten

Feature	Use Case
Graph View	Visualize connections
Backlinks	Find referencing notes
Templates	Consistent note structure
Tags	Cross-cutting categorization
Search	Find connections
Community Plugins	Readwise, Zotero, Dataview

Related

• PARA-Zettelkasten Hybrid - Combined methodology
• TDD Workflow - Similar iterative approach
• Tech Stack - Obsidian configuration