Knowledge Concepts
What is evergreen notes? A clear explanation of Andy Matuschak's concept, how to write notes that compound in value over time, and how to build a knowledge system that works.
Evergreen notes are notes written to be permanent and perpetually useful — stated clearly and completely enough to stand alone, linked to related notes, and revised over time as your thinking develops — as opposed to transient notes (meeting notes, daily logs) that are only useful for a brief period after they're written.
The concept was articulated by Andy Matuschak, a researcher and software designer whose published notes at notes.andymatuschak.org have become an influential model for the practice.
Andy Matuschak is a researcher focused on tools for thought and the founder of Quantum Country (a spaced repetition reading platform). His thinking about evergreen notes builds on Niklas Luhmann's Zettelkasten but extends it with explicit properties that make notes more useful and better suited to long-term knowledge development.
Matuschak's key insight: most notes fail at their intended purpose not because people don't take notes, but because the notes are written in a format that's only useful once. Meeting notes capture the meeting. Literature notes capture the book. But neither is designed to persist and develop. Evergreen notes are written to be visited and revised repeatedly — like a living document, but at the granular level of a single idea.
Matuschak publishes his evergreen notes publicly (a practice called "working with the garage door open"), and the collection at notes.andymatuschak.org demonstrates the method at scale. Reading through his linked notes illustrates what a well-developed evergreen note system actually looks like.
Matuschak identifies several properties that distinguish evergreen notes from ordinary notes:
Concept-oriented, not source-oriented. Evergreen notes are organized around ideas, not around the sources they came from. "Loss aversion makes people prefer status quo options" is an evergreen note. "Notes from Kahneman Chapter 3" is a literature note. The evergreen note can receive links from many different sources over time; the literature note is frozen at the time you read the book.
Atomic. One idea per note. Not "everything I know about behavioral economics" — that's a category. Not "a few interesting thoughts from today's reading" — those are fleeting notes. One clear, complete statement of a single idea.
Connected. Each evergreen note links to related notes. The connections aren't decorative — they're the mechanism through which knowledge compounds. An isolated note, no matter how well-written, is less useful than a connected one.
Written for future self and others. Evergreen notes are written clearly enough that they make sense without context. Not "as discussed above" or "see the Smith paper" — the note contains the idea, explained.
Revised over time. As your understanding develops, you update the note. This distinguishes evergreen notes from a static archive: the note grows with you.
| Note type | Purpose | Lifespan | Format |
|---|---|---|---|
| Fleeting notes | Quick capture | Hours to days | Rough, contextual |
| Literature notes | Processing a source | Until processed | Source-specific |
| Project notes | Active work context | Duration of project | Action-oriented |
| Evergreen notes | Permanent knowledge | Years to indefinite | Atomic, concept-oriented, linked |
Fleeting and literature notes are inputs that get processed into evergreen notes. Project notes are temporary scaffolding. Evergreen notes are the permanent knowledge base that compounds over time.
A science journalist writing about neuroscience:
Fleeting note (Monday): "Article about sleep consolidation — something about REM and memory. Save for later."
Literature note (Thursday): After reading the full study: "Walker (Why We Sleep, 2017): During REM sleep, the hippocampus replays recent experiences and transfers them to the neocortex for long-term storage. Sleep deprivation disrupts this transfer."
Evergreen note: "Sleep is required for memory consolidation, not just memory formation" — written as a statement, linked to notes on memory, performance optimization, cognitive psychology. Includes one key mechanism (hippocampal replay during REM) and a practical implication.
Six months later: Writing an article on productivity. Searches her notes. Finds this evergreen note. Reads the statement. Immediately useful — she doesn't need to reprocess the book or the fleeting note. The idea is available.
Two years later: She updates the note with a new finding that nuances the claim — REM sleep matters most for procedural memories; declarative memories also consolidate during NREM. The note evolves.
The compounding value of evergreen notes comes from two sources:
Density of connections. Each new note doesn't just add to the archive — it connects to existing notes, creating new paths between ideas. A note on loss aversion connects to notes on pricing strategy, subscription behavior, and negotiation. The next time you're writing about pricing, navigating from one note leads to three others you'd have needed to reconstruct from scratch.
Cumulative development. Each time you revisit and update a note, you're adding years of reading and thinking to a single place. A note on "effective CTA design" that you've visited and updated 20 times over four years embeds insights from 20 different reading contexts. That's not something you can replicate in a single writing session.
This is why evergreen notes are particularly valuable for knowledge workers who develop expertise over years: the system captures not just what you've learned but how your understanding has developed.
Step 1: Start from a strong source. Evergreen notes are extracted from sources worth the extraction effort. Literature notes, key findings, important principles, concepts you want to internalize.
Step 2: Find the single concept. Ask: what is the one clear idea I want to preserve from this? If you can't state it in one sentence, it might be multiple notes.
Step 3: Write the idea as a complete, standalone statement. The note title should be a complete sentence that states the idea. "Loss aversion makes people prefer avoiding losses over acquiring equivalent gains" is a title. "Loss aversion" is not — it's a category.
Step 4: Write the body in full sentences. Include the mechanism, not just the claim. Include one concrete example. Write as if explaining to an intelligent reader who has no context from your other notes.
Step 5: Link aggressively. What other notes does this connect to? Add those links. If a note exists that contradicts this one, link to it. Both notes become richer.
Step 6: Revisit and update. Evergreen notes are never truly "done." When you encounter new evidence, a better example, or a nuance that changes the claim, update the note. Date your updates if the evolution matters.
WebSnips sits upstream of the evergreen notes workflow — in the capture and connection layer:
For writers who develop expertise through web research and want to write from a compound knowledge base, WebSnips provides the source library and Creator Studio handles the initial synthesis — you then extract the evergreen notes that capture the durable insights.
Do I need Obsidian or Roam to take evergreen notes?
No — you need any tool that supports linking between notes and that you'll maintain over years. Obsidian, Roam Research, and Logseq are popular because [[wikilinks]] make linking easy, but even a folder of markdown files with explicit links works. Notion is usable but the linking is more friction.
How many evergreen notes should I expect to have? Andy Matuschak has thousands of public notes. Niklas Luhmann had 90,000. At typical note-writing rates, a serious practitioner might write 2–5 evergreen notes per day of focused work. After a year, a few hundred. After five years, a thousand or more. Volume is less important than quality and connection density.
What's the difference between evergreen notes and a personal wiki? A personal wiki is organized hierarchically by topic (Home → Technology → Note-Taking → Tools). Evergreen notes are organized by concept, linked directly — the structure emerges from connections rather than being imposed by a hierarchy. A wiki looks like an encyclopedia; an evergreen note system looks more like a graph.
Can I convert existing notes to evergreen notes? Yes, retrospectively. Review your existing notes and ask: is this a fleeting/temporary note or a potentially permanent idea? For the permanent ones, rewrite the title as a complete concept statement and add links to related notes. You don't need to process everything at once — you can convert notes opportunistically when you return to them for a purpose.
Evergreen notes are the building blocks of a knowledge system that compounds over time — atomic, concept-oriented, connected notes that are written to be permanent and revised as understanding develops, rather than discarded after a single use.
The shift from temporary notes to evergreen notes is a shift from capturing information to developing knowledge. Information captured in a vacuum decays; ideas developed in connection with other ideas grow.
Start with one: find the single most important idea in an article you just read. Write it as a complete sentence. Link it to two things you already know. That's your first evergreen note.
More WebSnips articles that pair well with this topic.
What is citation management? A clear explanation for researchers and academics — how citation managers work, the best tools, and how to avoid the most common mistakes.
What is tacit knowledge? A clear explanation for team leads and ops people — what tacit knowledge is, why it's the hardest knowledge to transfer, and practical methods to make it explicit.
What is a commonplace book? A clear explanation of the centuries-old knowledge collection practice, famous examples, and how to build a modern digital version for writers and researchers.