Populate your SECOND BRAIN | GUIDE to Atomic Notes in Logseq (or Roam)
Based on Tomi Nuottamo's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Permanent notes should be atomic: one note should contain one idea so links can connect precisely.
Briefing
Evergreen “permanent notes” are the engine of a second brain: each note should hold one atomic idea, then link to other notes so new insights emerge through connections. The workflow’s hardest step isn’t capturing information—it’s converting scattered material into stable, searchable notes that can later be recombined into outlines, arguments, and updates. The practical takeaway is simple: treat permanent notes like single concepts on a table, and let the network of links do the thinking.
A major early decision is how to title notes. Generic “how-to” titles tend to clutter search results because they all share the same phrasing. Instead, titles should describe the idea directly—removing “how to” and focusing on the concept the note represents. For example, “how to motivate yourself when you’re not feeling motivated” becomes “finding motivation when not feeling motivated.” Clear titles also make later outlining easier, because the note’s subject reads like a usable heading.
Atomic notes also shape what goes into each note. The guidance favors keeping permanent notes short and focused, even if that means splitting content. While some people prefer packing everything relevant into one place, the atomic approach forces the note to capture the essence of a single idea. When multiple ideas sit in one note, it becomes harder to create meaningful connections—because links attach to a bundle rather than a specific concept.
Once a library of permanent notes exists, the next move is maintenance through retrieval. Search through existing notes that match what’s being worked on now, especially because many earlier insights will be forgotten. Those “long-lost” notes can provide three kinds of value: fresh support for current reading or writing, conflicting perspectives that sharpen thinking, or supplementary thoughts that extend what’s already been written. The recommended action is either to create a new note that connects the old idea to the new context, or to morph the old note so it stays accurate.
Logseq offers multiple ways to find and connect notes. Graph view supports visual exploration, while search can isolate connected notes into a focused view. More advanced querying is possible through Logseq queries, but the guidance suggests that beginners can rely on spotlight search and graph view first, then graduate to query-based workflows later.
Finally, not everything deserves permanent status. “Fleeting notes” include web clips, journal entries, seminar notes, and video notes collected during the day. Keeping them outside the second brain helps avoid clutter and reduces friction—capturing notes in whatever tool is easiest at the moment. The system works best when fleeting notes are sifted later, with only a fraction promoted to permanent notes. The goal is to keep the fleeting inbox near zero for momentum and a sense of progress, while building a network of permanent notes whose connections become increasingly rewarding over time.
Cornell Notes
Permanent notes are the backbone of a second brain and should be “atomic”: one note equals one idea. Titles work best when they describe the concept directly (e.g., “finding motivation when not feeling motivated”) rather than generic “how-to” phrasing that makes search harder. Atomic notes stay short and focused so links connect to specific ideas, making it easier to generate new connections and insights. When working on something new, retrieve relevant permanent notes, then either create a new linking note or morph the old one to reflect new context. Fleeting notes (web clips, journal entries, seminar and video notes) should stay out of the permanent system until they’re sifted, keeping the second brain uncluttered and the capture process low-friction.
What does “atomic” mean for permanent notes, and why does it matter for connections?
How should note titles be structured to improve search and outlining?
What’s the recommended way to use older permanent notes when tackling new work?
Which Logseq features help beginners find connected notes, and when should queries be learned?
Why keep “fleeting notes” separate from permanent notes?
Review Questions
- How would you rewrite a “how-to” note title to make it more searchable and useful as an outline heading?
- What problems arise when multiple ideas are stored in a single permanent note under an atomic-note approach?
- When you find a relevant but outdated permanent note during retrieval, what are the two recommended actions?
Key Points
- 1
Permanent notes should be atomic: one note should contain one idea so links can connect precisely.
- 2
Use concept-descriptive titles instead of generic “how-to” phrasing to reduce search clutter and improve outlining.
- 3
Keep permanent notes short and focused; splitting or refining notes makes it easier to build meaningful connections.
- 4
Retrieve and reuse older permanent notes when working on new material, then either create a linking note or morph the old note to match new context.
- 5
In Logseq, graph view and spotlight search are practical starting points for finding connected notes; advanced queries can come later.
- 6
Store fleeting notes outside the permanent system to avoid clutter and keep capture low-friction across tools.
- 7
Promote only a fraction of fleeting notes to permanent notes and aim to keep the fleeting inbox near zero for sustained momentum.