Build a Note System That Matches How You Think
For knowledge workers and note-takers · Based on Lenaghan Friction-First Productivity System Builder
// TL;DR
Knowledge workers accumulate notes, references, and tasks across tools and often spend more time tuning tags than using them. The friction-first method redirects that energy: instead of re-tagging endlessly or chasing the next second-brain method, you treat every 'Where do I file this note?' pause as a signal. You map your real mental model, make the smallest change that fits it, and validate with natural retrieval. Use it when your note system feels like maintenance work rather than a thinking tool.
Why does my note system feel like endless maintenance?
Because you're working on your system instead of working on the things in it. Re-tagging notes, restructuring your vault, and migrating between apps all feel productive, but they produce no actual thinking or output. Knowledge workers are especially prone to this because note tools are infinitely tweakable and every second-brain influencer offers a new taxonomy. The maintenance impulse is a symptom: your structure doesn't yet match how your brain retrieves ideas, so you keep fiddling instead of fixing the real mismatch.
How do I find the friction points in my notes?
Recall the last several times you paused while saving a note, searching for one, or deciding which folder or tag it belonged to. Write each one down specifically—'I couldn't decide if this went under Research or Projects,' or 'I couldn't find the meeting notes from last week.' Even vague frustration counts as a starting point. These pauses are diagnostic data, not evidence you're bad at organizing. Each one points to exactly where your taxonomy diverges from your thinking.
How do I map my real mental model?
For each friction point, ask where you expected that note to live. If you kept looking under a topic name but the system filed it by date, you think topically and your system is time-based—a classic mismatch. If you looked by project but the system used broad areas, you think project-first. The consistent gap between expectation and reality names your mental model. Once you can name it, you know which direction to reshape your structure.
What's the right way to fix a note-system mismatch?
Make the smallest change that closes the gap, not a full vault rebuild. If you think topically but your notes are date-organized, introduce topic folders or a topic tag as the primary axis and demote dates to metadata. If your tags overlap and cause hesitation, merge the redundant ones. Then keep a visual working model—a mind map or plain outline of your folders, tags, and note groups—so you can test rearrangements in the diagram before committing them to your vault.
How do I know a change resolved the friction?
Run the natural retrieval test. Over the next several notes you save or search for in that area, notice whether you reach the right place instinctively or still stall. Natural retrieval—no pausing, no reasoning—is the only signal that your structure now matches your mental model. If you still hesitate, the fix was partial; adjust once more and retest. If it's effortless, that part of your system is done and you stop touching it.
How do I stop chasing every new second-brain method?
Commit to the no-overhaul rule. Every new note-taking video or PKM framework will tempt you to restructure everything. Don't. Extract only the single element that addresses a friction point you're actively experiencing, and ignore the rest of the method. Over weeks and months, these small extractions and adjustments—gradual personalization—converge on a system that's genuinely yours. The endpoint isn't a perfect vault; it's a vault you stop thinking about so you can think with it instead.
Next step: Write down the three note-related hesitations you've hit most this week. Name the mental model each one reveals, then make one small structural change and let natural retrieval tell you whether it worked.
// FREQUENTLY ASKED QUESTIONS
Should I organize notes by topic, project, or date?
Organize by whichever axis your brain reaches for when searching. Test this by recalling recent note-search hesitations and asking where you expected the note to live. If you keep looking by topic but your system files by date, make topic the primary axis. Let your friction points, not a popular method, decide the structure.
How do I fix an overloaded, overlapping tag system?
Identify the specific moments you hesitate over which tag to apply—that overlap is the friction point. Merge the redundant tags into one, making the smallest change possible, then run the natural retrieval test. If tagging now feels instinctive, you're done. Resist the urge to redesign the entire taxonomy at once.
Is friction-first better than adopting a second-brain method like Zettelkasten?
For most knowledge workers, yes—because any published method was designed for its creator's brain, not yours. You can borrow a single useful element from Zettelkasten or any PKM system to solve a real friction point, but adopting the whole method wholesale usually reintroduces the mismatch that made you unhappy in the first place.