Evergreen Notes Summary
Summary of Andy Matuschak’s notes on evergreen note-writing, knowledge work, and tools for thought.
Source: his public notes and essay How to write good prompts.
What evergreen notes are
Notes written and organized to evolve, contribute, and accumulate over time, across projects. Most people take only transient notes — jotting things down in the moment, never revisiting them. Evergreen notes are the opposite: living documents you return to, refine, and build on.
The goal isn’t “better note-taking” — it’s better thinking. The notes are a byproduct of developing insight.
Core principles
Atomic. Each note captures one idea. Not a summary of a book, not a collection of thoughts on a topic. One concept, one note. This makes notes composable — you can combine them in new ways, link them into new structures. Like separation of concerns in software: a module should be “about” one thing so it’s reusable. But don’t fragment too much — you’ll get a cohesion problem.
Concept-oriented. Organize around concepts, not sources. Don’t title a note “Chapter 3 of Book X.” Title it with the idea. When multiple sources inform the same concept, they converge on the same note. This makes it easy to find past thinking when a concept comes up again — you don’t need to remember which book or project dealt with it.
Densely linked. The value of a note grows with its connections. Each note should link to related notes, creating a web of ideas you can navigate associatively. Over time, you accumulate notes which you can combine in increasingly complex ways to produce novel insights.
Associative over hierarchical. Don’t build neat folder trees. Build graphs. A note about “enabling environments” might connect to notes about apprenticeships, video games, and research labs — relationships no folder structure could capture.
Write for yourself. Disregard audience. These notes are thinking tools, not publications. Write in whatever way helps you think.
Naming and titling notes
Titles are APIs
When a note is well-titled, the title becomes an abstraction — a handle for the entire idea. You can reference the note by title alone in other contexts and the meaning carries through. As your thinking matures, you can write notes whose titles abstract over increasingly large subtrees of ideas.
This is also a litmus test: if you can’t summarize a note in a sharp title, your thinking is muddy — either the note is about multiple things (break it up) or you don’t understand it well enough yet.
Use complete phrases, not topic words
Don’t title a note “Stock” or “Deep work.” Make a claim:
- “Evergreen notes should be atomic”
- “Educational objectives often subvert themselves”
- “Effective deep work depends on both time and intensity”
These are declarative or imperative phrases that force you to actually have a point. Questions also work — “To what extent is exceptional ability heritable?” — but the goal is to eventually refactor them into declarative notes (drop the question mark).
Exceptions:
- Core terms that other notes orbit around get noun-phrase titles: “Enacted experience”, “Enabling environment”, “Executable strategy”
- Outline notes that sequence other notes into an argument: “§Note-writing systems”
Matuschak often starts writing without knowing the title. The title emerges from the text. When it clicks into a sharp claim, that’s a sign the thinking is landing.
Prefer positive framing
Don’t write “X is bad” or “Y doesn’t work.” Express the underlying theory positively:
- Not “Passive environments can’t offer good metacognitive support” → “Metacognitive supports require dynamic, participatory environments”
- Not “Don’t read on your phone” → “Use phones to collect and triage, not to read”
Negative notes are dead ends. Positive notes express the requirement or property, making them easier to build on systematically and connect to other ideas.
Concept handles
A good name for a concept (a “concept handle,” from Christopher Alexander) makes it possible to use that concept in thinking. Without a handle, the concept is slippery, hard to reference, hard to combine. Good note titles create concept handles — note-writing isn’t just recording ideas, it’s making ideas usable by giving them names you can think with.
Linking
Tags are weak. Tags say “these things are related” but not how. They produce jumbled, unordered lists. Prefer explicit links with context.
Prefer fine-grained associations. Link to specific notes, not broad topics. A link should connect two specific ideas.
Prefer labeled associations. When linking, add a few words of context about why these notes relate. The context serves as a cue when navigating later — it helps you retrace your former thought processes.
Prefer explicit associations to inferred ones. Don’t rely on co-location or shared tags to imply relationships. Make the connection explicit.
Backlinks define nodes implicitly. You can define a concept extensionally — by linking to it from many places — before it has any content of its own. The backlinks are the definition, at least initially.
How to write them
Start from what you read. Writing about what you read forces sharper understanding. Don’t highlight — write. The act of reformulating ideas in your own words reveals what you actually understand and where the gaps are. This is “knowledge transforming” — you don’t just record what you know, you discover what you think.
Use a writing inbox. Keep a place for transient, incomplete notes — scraps, hunches, half-formed thoughts. Regularly process this inbox: refine scraps into evergreen notes, discard what doesn’t hold up, link what connects.
Create speculative outlines. When developing a concept, sketch outlines that sequence your existing notes into an argument or narrative. The outline isn’t the goal — it’s a tool for seeing what’s missing and what doesn’t fit. You can sort notes by pairwise comparison (“which comes first?”) rather than trying to impose structure top-down.
Let notes accrete. Evergreen notes grow through compounding. Each time you encounter an idea that connects to an existing note, you can refine or extend it. Over months and years, notes become richer, more nuanced, more connected. This is the “compound interest” of knowledge work.
Evergreen notes are a safe place to develop wild ideas. Because you’re writing for yourself, you can explore ideas that aren’t yet defensible or fully formed. The note can mature over time.
Matuschak’s daily practice
He starts each day with a note titled with the date (e.g. “2020-03-12”). It captures ephemera throughout the day: reflections, scratch work, etc. It’s an intentional dumping ground — a release valve so there’s always “a place to put that thing.” Processing this into evergreen notes happens separately.
He describes his note taxonomy as:
- Evergreen notes — precise, narrow, declarative claims
- Outline notes — sequences of links that build an argument (prefixed with §)
- Bridge notes — dedicated notes explaining the relationship between two ideas
- Literature notes — titled after a single work, primarily as linkages to other notes and backlink targets
- Daily working logs — ephemeral, date-titled
Types of knowledge and how to capture them
(From the prompt-writing guide — principles generalize beyond flashcards.)
Factual knowledge (closed lists, definitions). Break down into atomic pieces. For a list of ingredients, each item gets its own note/prompt. Don’t try to compress multiple facts into one unit. Write more atomic notes than feels natural — the cost per note is lower than you think.
Procedural knowledge. Extract the keywords that carry the critical details. What are the important verbs, conditions, heuristics? A recipe’s procedure boils down to a few key transitions and their triggers. Capture why behind steps, not just what. “Why” prompts help avoid rote learning and build deeper understanding. When writing reveals a gap in your understanding (“why does low heat produce cleaner flavor?” — I don’t know), that’s valuable — note it.
Conceptual knowledge. Use multiple lenses:
- Attributes and tendencies — what makes X, X? What’s always/sometimes/never true?
- Similarities and differences — what distinguishes X from adjacent concepts?
- Parts and wholes — examples, sub-concepts, broader categories
- Causes and effects — what does X do? When is it used?
- Significance and implications — why does X matter? What does it suggest for action?
You won’t use every lens for every concept. They’re a toolkit for identifying what seems most important.
Open lists. Some knowledge is inherently open-ended (ways to use stock, applications of a technique). Don’t try to capture these as closed lists. Instead:
- Write notes about individual instances, linking each back to the concept
- Write notes about patterns you notice across instances
- Keep a fuzzy “name some examples” note that grows over time
Open lists are like tags in a mental filing cabinet — you’re associating instances with a concept, not memorizing a fixed set.
On knowledge work
Most knowledge work lacks deliberate practice. Unlike music or athletics, knowledge workers rarely have structured ways to improve their core skills. Evergreen note-writing can serve this role — it’s a concrete, repeatable practice that develops the skill of thinking well.
Writing forces sharper understanding. The process of writing changes and adds to the knowledge the writer had when starting. You don’t just record what you know — you discover what you think.
Insight through making. Building something (a note, an outline, a system) reveals things that pure contemplation misses. The interaction between your ideas and the constraints of the medium produces insights.
Effective deep work depends on both time and intensity. Getting to the desk and blocking distractions is table stakes. One hour of genuinely sharp, vivid attention produces more than five hours of dull focus. The hard part isn’t clearing your schedule — it’s maintaining real intensity.
Taxonomies of note types help. Matuschak distinguishes between different types of notes (evergreen, outline, bridge, literature, daily) not for bureaucratic reasons but because each type has a different function in thinking. Knowing what type you’re writing helps you write it well.
Memory and mastery
Conceptual mastery is enabled by mastery of details. People who claim they want “broad conceptual understanding” without memorizing fundamentals are fooling themselves. You can’t compose a sonnet in French if you only know 200 words. Memory of basics is often the binding constraint on higher-level understanding.
Chunking is what expertise is. Chess masters perceive 25,000-100,000 patterns, not individual pieces. Expertise in any domain involves learning to perceive and reason about increasingly complex “chunks.” Note-writing can accelerate chunk acquisition by forcing you to articulate and connect the pieces.
Memory is not the goal — action is. A common failure: people can recall answers when tested but can’t retrieve them when they actually need them, or don’t even recognize opportunities to use what they’ve learned. The goal is fluent facility for effective action, not performance on a quiz.
Enabling environments
Matuschak thinks extensively about what makes environments that help people grow and do better work.
Focus on doing, not learning. The best environments enable people to do meaningful work, not to practice abstract skills. Growth happens as a byproduct of pursuing intrinsically meaningful purposes. Y Combinator founders are trying to build a company, not to learn entrepreneurship — the learning is a side effect.
Powerful environments arise from real projects. Apollo, Pixar, research labs, cathedrals — the enabling environment was a byproduct of pursuing a deeply meaningful goal, not designed in isolation. You can’t make “tools for thought” in the abstract. You have to make a tool for thinking about something in particular.
Focus on expert use. Tools designed for experts can also serve novices; tools designed for novices rarely help experts. Mathematica enables high schoolers to visualize experiments AND helps professional scientists — because it was designed for the scientists. SimCity is fun but its representations can’t evolve to real urban planning. Design for the frontier; novice paths can grow from there.
Serious contexts of use matter. You can’t build good tools for a domain you don’t practice seriously. Scrappy prototypes are fine, but critical insights only emerge from real use. Tool-makers usually lack connection to a serious context of use — and that’s why most “tools for thought” are plausible-seeming toys.
Enacted experiences
An enacted experience is one where participants feel they’ve brought it about — but which is actually the largely-specified expression of an author’s intentions.
Games are the paradigmatic example. Players press the buttons, feel they’re creating each moment, but the designer has arranged things so players typically create exactly the intended experience. This is different from film (where the author created the moment) and from software (where users feel agency but the experiences aren’t controlled by the designer).
Why this matters: enacted experiences create intense personal connection to authored targets. In Journey, you took every step — so the character’s transcendence is felt far more deeply than watching a movie. This is also why Y Combinator works: the dinners, milestones, and Demo Day feel like things founders brought about, even though the structure was carefully designed.
Potential as mass medium. Apprenticeships create enacted experiences but don’t scale. Games scale but mostly convey aesthetic experiences, not knowledge. The open question: can you create an enacted experience that does the “job” of a book — communicating ideas, values, and practices — but with the personal connection of a game or apprenticeship?