Note-Taking Systems
Zettelkasten Method
Three note types form a processing pipeline:
| Note type |
What it is |
Where it lives |
Lifespan |
| Fleeting |
Raw capture — thoughts, highlights, quick ideas |
Inbox |
Days |
| Literature |
Processed from a single source, in your own words |
Reference |
Permanent |
| Permanent (Zettel) |
Single idea, linked to related ideas, evergreen |
Main slip box |
Permanent |
Permanent Note Principles (atomic notes)
- One idea per note — split if a note covers more than one concept
- Write in your own words — paraphrasing builds understanding
- Link explicitly — every note links to at least one related note
- Title is a full sentence or claim: "Spaced repetition beats massed practice for long-term retention"
- Notes should make sense without context (standalone)
Zettelkasten Workflow
- Capture fleeting notes throughout the day (phone, paper, app)
- Process fleeting notes daily/every 2 days → literature or permanent notes
- Write permanent notes — formulate the idea, find links
- Link to existing notes — this is where insight emerges
- Review periodically — notes surface connections over time
PARA Method
Four categories for organizing all digital information:
| Category |
What belongs |
Time horizon |
Examples |
| Projects |
Active work with deadline/outcome |
Weeks-months |
"Launch feature X", "Write article on Y" |
| Areas |
Ongoing responsibilities, no deadline |
Indefinite |
"Health", "Finance", "Engineering" |
| Resources |
Reference material for future use |
Indefinite |
"CSS patterns", "Tax info", "Book notes" |
| Archives |
Completed or inactive from above |
Permanent |
Finished projects, past references |
PARA Rules
- Every piece of information belongs in exactly one location
- Projects drive organization — resources exist to support projects
- Move items to Archives when no longer active (don't delete)
- Review quarterly: promote resources → projects, archive completed projects
Progressive Summarization
Four layers of highlighting to distill information over time:
| Layer |
What you do |
When |
| 0 |
Save the source note |
When captured |
| 1 |
Bold the most important passages (10-20%) |
When reading/processing |
| 2 |
Highlight the most important bolded passages (10-20% of layer 1) |
When revisiting |
| 3 |
Write a short executive summary at the top |
When actively using |
Layer 4: Express — turn the note into your own output (article, presentation, decision).
Key rule: Only add a layer when you revisit the note for a real reason. Don't pre-summarize.
Capture Workflow
What to capture
- Ideas that surprise you or challenge your assumptions
- Connections between unrelated concepts
- Questions you want to explore
- Counterarguments to things you believe
- Anything you want to be able to find again
- Not: everything — selectivity is a skill
Capture tools by context
| Context |
Tool |
| Mobile / walking |
Voice memo, Apple Notes, quick capture app |
| Desktop |
Dedicated inbox in PKM tool or browser extension |
| Reading (physical book) |
Pen + paper → transfer during weekly review |
| Reading (digital) |
Readwise, Kindle highlights, browser clipper |
| Meeting |
Dedicated meeting note template |
Inbox Zero for Notes
- Process capture inbox at least twice a week
- Each item: delete / file as-is / develop into permanent note
- Nothing stays in inbox > 1 week
Tool Comparison
| Tool |
Best for |
Strengths |
Weaknesses |
| Obsidian |
Zettelkasten, local-first, power users |
Linking, plugins, local markdown files |
Setup complexity |
| Roam Research |
Bidirectional linking, daily notes |
Block references, networked thought |
Cost, proprietary |
| Notion |
Teams, PARA, databases |
Flexible, collaborative |
Slow, poor linking |
| Apple Notes |
Quick capture, iOS integration |
Fast, reliable, search |
No linking, basic |
| Logseq |
Open-source Roam alternative |
Free, local, outline-based |
Smaller ecosystem |
Atomic Note Template
# [Claim or concept in full sentence]
[2-5 sentences explaining the idea in your own words]
## Evidence / Examples
- [Supporting example or data point]
- [Counter-example if relevant]
## Why this matters
[Practical implication or why you captured this]
## Links
- [[Related note 1]] — [how it relates]
- [[Related note 2]] — [how it relates]
## Source
[Author, Book/Article, Date, Page/URL]
Review and Maintenance
Daily (5 min)
- Process fleeting notes from yesterday
- Write 1 permanent note minimum
Weekly (during weekly review)
- Process literature notes backlog
- Check notes related to active projects
Monthly
- Browse randomly through 10-20 notes
- Update outdated notes
- Merge duplicates
Signals that your system needs attention
- You can't find notes you know you took
- Notes exist but never get used
- Capture is high but processing is zero
- Too many orphaned notes with no links
1---2name: note-taking3description: When to activate: note taking, Zettelkasten, PARA method, knowledge management, PKM, evergreen notes, second brain, Obsidian, Roam, Notion4---56# Note-Taking Systems78## Zettelkasten Method910Three note types form a processing pipeline:1112| Note type | What it is | Where it lives | Lifespan |13|-----------|-----------|---------------|---------|14| Fleeting | Raw capture — thoughts, highlights, quick ideas | Inbox | Days |15| Literature | Processed from a single source, in your own words | Reference | Permanent |16| Permanent (Zettel) | Single idea, linked to related ideas, evergreen | Main slip box | Permanent |1718### Permanent Note Principles (atomic notes)19- One idea per note — split if a note covers more than one concept20- Write in your own words — paraphrasing builds understanding21- Link explicitly — every note links to at least one related note22- Title is a full sentence or claim: "Spaced repetition beats massed practice for long-term retention"23- Notes should make sense without context (standalone)2425### Zettelkasten Workflow261. **Capture** fleeting notes throughout the day (phone, paper, app)272. **Process** fleeting notes daily/every 2 days → literature or permanent notes283. **Write** permanent notes — formulate the idea, find links294. **Link** to existing notes — this is where insight emerges305. **Review** periodically — notes surface connections over time3132## PARA Method3334Four categories for organizing all digital information:3536| Category | What belongs | Time horizon | Examples |37|----------|-------------|-------------|---------|38| **P**rojects | Active work with deadline/outcome | Weeks-months | "Launch feature X", "Write article on Y" |39| **A**reas | Ongoing responsibilities, no deadline | Indefinite | "Health", "Finance", "Engineering" |40| **R**esources | Reference material for future use | Indefinite | "CSS patterns", "Tax info", "Book notes" |41| **A**rchives | Completed or inactive from above | Permanent | Finished projects, past references |4243### PARA Rules44- Every piece of information belongs in exactly one location45- Projects drive organization — resources exist to support projects46- Move items to Archives when no longer active (don't delete)47- Review quarterly: promote resources → projects, archive completed projects4849## Progressive Summarization5051Four layers of highlighting to distill information over time:5253| Layer | What you do | When |54|-------|-------------|------|55| 0 | Save the source note | When captured |56| 1 | Bold the most important passages (10-20%) | When reading/processing |57| 2 | Highlight the most important bolded passages (10-20% of layer 1) | When revisiting |58| 3 | Write a short executive summary at the top | When actively using |5960Layer 4: Express — turn the note into your own output (article, presentation, decision).6162**Key rule**: Only add a layer when you revisit the note for a real reason. Don't pre-summarize.6364## Capture Workflow6566### What to capture67- Ideas that surprise you or challenge your assumptions68- Connections between unrelated concepts69- Questions you want to explore70- Counterarguments to things you believe71- Anything you want to be able to find again72- **Not**: everything — selectivity is a skill7374### Capture tools by context75| Context | Tool |76|---------|------|77| Mobile / walking | Voice memo, Apple Notes, quick capture app |78| Desktop | Dedicated inbox in PKM tool or browser extension |79| Reading (physical book) | Pen + paper → transfer during weekly review |80| Reading (digital) | Readwise, Kindle highlights, browser clipper |81| Meeting | Dedicated meeting note template |8283### Inbox Zero for Notes84- Process capture inbox at least twice a week85- Each item: delete / file as-is / develop into permanent note86- Nothing stays in inbox > 1 week8788## Tool Comparison8990| Tool | Best for | Strengths | Weaknesses |91|------|---------|-----------|------------|92| Obsidian | Zettelkasten, local-first, power users | Linking, plugins, local markdown files | Setup complexity |93| Roam Research | Bidirectional linking, daily notes | Block references, networked thought | Cost, proprietary |94| Notion | Teams, PARA, databases | Flexible, collaborative | Slow, poor linking |95| Apple Notes | Quick capture, iOS integration | Fast, reliable, search | No linking, basic |96| Logseq | Open-source Roam alternative | Free, local, outline-based | Smaller ecosystem |9798## Atomic Note Template99100```markdown101# [Claim or concept in full sentence]102103[2-5 sentences explaining the idea in your own words]104105## Evidence / Examples106- [Supporting example or data point]107- [Counter-example if relevant]108109## Why this matters110[Practical implication or why you captured this]111112## Links113- [[Related note 1]] — [how it relates]114- [[Related note 2]] — [how it relates]115116## Source117[Author, Book/Article, Date, Page/URL]118```119120## Review and Maintenance121122### Daily (5 min)123- Process fleeting notes from yesterday124- Write 1 permanent note minimum125126### Weekly (during weekly review)127- Process literature notes backlog128- Check notes related to active projects129130### Monthly131- Browse randomly through 10-20 notes132- Update outdated notes133- Merge duplicates134135### Signals that your system needs attention136- You can't find notes you know you took137- Notes exist but never get used138- Capture is high but processing is zero139- Too many orphaned notes with no links
Mattakushi432