AI & Automation for Knowledge
Learn the evergreen notes method from Andy Matuschak. Build a note-taking practice where every note gains value over time through revision and linking.
Most notes are write-once, read-never.
You write a note. You never look at it again. It becomes digital clutter.
Evergreen notes are different.
They're designed to be revisited, refined, and connected. They become more valuable over time.
Like compound interest for knowledge.
This guide explains the evergreen note method from Andy Matuschak, how to write them, and how they compound in value.
An evergreen note has four properties:
You return to the note periodically. You read it. You might refine it.
Raw notes: "Compound interest is exponential growth."
Evergreen note on first pass: "Compound interest is exponential growth of principal + accumulated interest. Example: $1,000 at 10% grows to $2,593 after 10 years."
Evergreen note after encountering new information: "Compound interest is exponential growth where returns generate returns. Key insight: early compounding matters most — $1 invested at 10% for 20 years > $20 invested at 10% for 1 year."
You can link this note to other notes. It exists in a graph of related ideas, not in isolation.
When you write an evergreen note, you ask: "What other notes does this connect to?"
And you add those links.
When you read an old note and see connections to new ideas, you add new links.
Over time, your note becomes a hub in a network of related concepts.
You can read the note without context and understand it.
Bad: "See compound interest note."
Good: "Compound interest occurs when returns generate returns. $1 at 10% compounds to $2.59 after 10 years — the $1.59 gain comes from interest on interest."
A reader should understand your note without reading 5 other notes first.
The note is about an idea, not about a book or article.
Bad: "From 'Thinking, Fast and Slow' by Kahneman — anchoring bias makes people rely on first information."
Good: "Anchoring bias: people's estimates are influenced by an initial reference point (anchor), even if the anchor is arbitrary. Example: asking 'Is the population of Australia > 30 million?' primes higher estimates than asking 'Is the population < 5 million?' — Related to: [[Cognitive Biases]], [[Heuristics]]."
The note is about the idea (anchoring bias), not about Kahneman's book. You might have encountered this idea from multiple sources — the evergreen note captures the idea itself, linked to related concepts.
Raw highlight:
"The most important investment is time."
Why it's not evergreen: No interpretation. No connection. Just a quote.
Evergreen version:
Fleeting note: "Maybe quarterly reviews waste time?"
Why it's not evergreen: It's a question, not an idea. It might be abandoned.
Evergreen version:
Literature note: Summary of an article you read.
"From TechCrunch article 'The Rise of AI': AI is getting better, companies are adopting it, future is uncertain."
Why it's not fully evergreen: It's source-attached and generic.
Evergreen version (built from the literature note):
Don't start with "I read article X."
Start with "I've learned an idea."
Example: After reading 3 different articles on habits, you have an understanding of habit loops. That's your starting point.
The title should express the idea clearly.
Bad:
Good:
Pretend you'll read this note in 6 months and won't remember the original article.
Include:
Example:
# Habit Stacking: Attaching New Behaviors to Existing Ones
## Definition
Habit stacking is attaching a new routine to an existing one.
Formula: "After [existing habit], I will [new habit]."
## Why It Works
Existing habits are already automatic.
They require no willpower.
By attaching a new behavior, you leverage existing momentum.
## Example
- Existing habit: "After I pour my morning coffee, I will..."
- New habit: "...do 10 pushups"
- Result: No new trigger needed. You just added to an existing routine.
## Why It Matters
Most failed habits fail because they require new willpower every time.
Stacking piggybacks on existing habits.
Lower friction = higher success.
## Related
- [[Willpower Depletion]]
- [[Keystone Habits]]
- [[Behavioral Design]]
As you write, ask: "What else does this connect to?"
Add links (or create placeholder links if the note doesn't exist yet):
Or create a "Related" section at the end.
Later, when you encounter:
You return to the note and refine it.
Original version: "Habit stacking is attaching new habits to existing ones."
Refined version (after learning more): "Habit stacking works best when the existing habit is already rock-solid. If the existing habit is itself weak, the new habit won't stick because the anchor habit isn't reliable."
You've made the note better.
Individually, evergreen notes are just well-written ideas.
But collectively, they compound.
You have 5 evergreen notes on decision-making:
Each note is valuable alone.
You add 10 more notes: [[Opportunity Cost]], [[Regret Theory]], [[Expected Value]], etc.
Now when you read a 15-note collection, you see patterns.
You realize many notes connect to a deeper idea: "People make bad decisions because they don't quantify tradeoffs."
You have 30 notes on decision-making and related topics.
A dense network emerges.
When you search "How should I make a career change?", your system shows:
You've accidentally built a decision-making system.
You have 100 evergreen notes across topics.
Now when you face a problem, your system helps you think.
You're not just retrieving information. You're thinking with your notes.
Month 1 — Initial capture:
# Pareto Principle: 80/20 Rule
80% of results come from 20% of effort.
Month 3 — Refined after encountering new examples:
# Pareto Principle: The Vital Few vs. The Trivial Many
The Pareto Principle (80/20): Roughly 80% of outputs come from 20% of inputs.
Examples:
- 80% of software bugs come from 20% of the codebase
- 80% of your happiness comes from 20% of your relationships
- 80% of business revenue comes from 20% of customers
Why it matters:
Prioritization is asymmetric. Some efforts matter far more than others.
The question isn't "What should I do?" but "Which 20% will create 80% of value?"
Related: [[Opportunity Cost]], [[Prioritization Frameworks]], [[Pareto Optimal Allocation]]
Month 9 — Refined with deeper understanding:
# Pareto Principle: The Vital Few vs. The Trivial Many
## Definition
The Pareto Principle observes that roughly 80% of results come from 20% of inputs.
## Why It's Not Magical
The ratio isn't always exactly 80/20. It's often 90/10 or 70/30.
The principle is that *distributions are non-uniform*, not that the ratio is fixed.
## Real Examples
- Code: 80% of bugs come from 20% of code → focus code review there
- Business: 80% of revenue from 20% of customers → prioritize those customers
- Health: 80% of health improvements from 20% of behaviors → sleep, exercise, diet
## The Thinking Tool
When facing a problem, ask: "What's the vital 20%?"
This flips prioritization from "Do everything" to "Focus on what matters most."
## Related
- [[Opportunity Cost]] — choosing 20% means not doing 80%
- [[Prioritization Under Constraints]]
- [[Power Law Distributions]] — why this pattern exists mathematically
- [[Pareto Optimal Resource Allocation]]
## Distinction
Related to but different from:
- [[80/20 Time Rules]] — allocating time to learning/thinking
- [[Kaizen]] — continuous improvement (not just big 20%)
- [[Minimum Viable Product]] — building core 20% first
The note started as a one-liner. Now it's a thinking tool that connects to a rich network of ideas.
And it's better than the original because you've refined it, added examples, and linked it.
You encounter an idea. You immediately write it as an evergreen note.
Problem: You don't fully understand it yet. Your note is shallow.
Fix: Let ideas marinate. Wait a few days or weeks. When you revisit the idea, you'll write a better note.
You try to capture an entire topic in one evergreen note.
Problem: The note becomes unfocused and hard to update.
Fix: Keep notes small and idea-focused. One clear idea per note.
You write evergreen notes but never link them.
Problem: They remain isolated. No compounding happens.
Fix: Every note should have 2–3 links to related notes.
You revisit an old note and rewrite it completely.
Problem: If you had linked to the old version, those links become confusing.
Fix: Refine the core idea, but keep the structure recognizable. Add, don't replace.
You write notes and never look back.
Problem: They don't improve. No compounding.
Fix: Weekly: scan your recent notes. Monthly: pick a random old note, read it, consider if it needs refinement.
Pick 5 ideas you've learned recently (from reading, experience, thinking).
Write a one-sentence title and 100–200 word explanation for each.
Don't overthink it. Rough is fine.
Read your 5 notes. For each, ask: "What other notes does this relate to?"
Add links (or create placeholder links).
Pick one note. Read it. Ask:
Refine it.
Continue writing new evergreen notes. Regularly revisit old ones. Watch your network grow.
Evergreen notes are ideas that improve over time.
They're:
Write them with:
The value compounds. Over time, your notes become a thinking tool that's more valuable than any book.
For more on building knowledge systems, see Personal Knowledge Management. For note-taking methodology, check Zettelkasten Method Guide.
Write clearly. Link intentionally. Refine regularly.
Build notes that compound.
More WebSnips articles that pair well with this topic.
Master the Zettelkasten method for building a powerful digital knowledge graph. Learn atomic notes, linking, and the slip-box workflow with modern tools.
Compare AI and manual note-taking across learning, meetings, and research contexts. Find the right balance for your knowledge workflow.
Design a daily notes practice that feeds your PKM system. Covers fleeting notes, daily review rituals, and how to turn daily logs into permanent knowledge.