There is a pattern that plays out in every knowledge management system that lasts longer than six months. You start with good intentions. You capture diligently. You link notes to each other. You use tags, folders, a sophisticated structure. And then, at some point, you realize: you can't find anything.
Not because the notes aren't there. Because the system has outgrown your ability to navigate it. Because retrieval — finding what you need, when you need it — is a completely different problem than storage, and most systems are designed for the wrong one.
Why Folders Disappoint as Retrieval Systems
Folders are useful for boundaries: projects, areas, archives, client work, research dumps. They disappoint when you ask them to carry context by themselves. When you file something, you make a decision about where it lives based on what it is. When you retrieve it, you have to remember that decision — which can require the same cognitive load as remembering the thing itself.
This is why many reference folders go stale. You file something, you can't find it later, you file a copy somewhere else, now you have two copies, neither of which you trust, and eventually you Google it again.
Links work better because they preserve context. When you link Note A to Note B, you're encoding a relationship: these two things are connected. When you encounter one, the link points you to the other. That's closer to how memory works than a folder hierarchy.
The practical rule: Use folders for broad categories you access rarely. Use links aggressively for connections between ideas you're actively working with. Let the links build a web of context around your current work.
The Atomic Note Problem
Atomic notes — one idea per note, written in your own words — are widely recommended and widely misunderstood. The goal is good: if each note is about one thing, notes are easier to link and move. But atomic doesn't mean short, and it doesn't mean isolated.
An atomic note that says "Product velocity depends on team cognitive load — source: McKinsey article" is atomic in form but useless in practice. When you come back to it, you don't have enough context to use it. What does cognitive load mean here? Why does it matter?
The atomic note test: Can you understand this note in six months without the context you had when you wrote it? If not, add more. Write what you understood at the time. Not a summary of the source — your interpretation of it. Your future self needs your perspective, not a rephrased article.
The Retrieval Audit (Do This Once a Quarter)
Once a quarter, run this check:
- Pick three projects you worked on in the last six months. Without looking at your task system, try to find every note, decision, and reference related to each one.
- For each project: count how many relevant notes you found in under two minutes. Did you find things you'd forgotten?
- For notes you found: could you understand them without the original context? If not, annotate them now.
If you consistently can't find things, the problem is in Layers 1 and 2 — you have too many active notes, or the link structure isn't being maintained. The fix is not more folders. The fix is: close Layer 1 (move finished work to Layer 3) and build Layer 2 deliberately (for every active note, ask "what does this connect to?").
Storage is cheap. Retrieval is the hard problem. Stop optimizing for storage.
