Get AI summaries of any video or article — Sign up free
How to make building your SECOND BRAIN easier | Create a HABIT with these simple steps thumbnail

How to make building your SECOND BRAIN easier | Create a HABIT with these simple steps

Tomi Nuottamo·
5 min read

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.

TL;DR

Avoid the collector’s fallacy by building a routine that converts highlights and clips into permanent notes, not just saves them.

Briefing

Building a second brain fails most often when captured notes pile up without being processed. The core fix is to create a repeatable habit for “tending” the knowledge system—turning fleeting highlights, clips, and literature notes into permanent notes—so the system produces usable knowledge instead of a growing archive.

A major trap is the collector’s fallacy: collecting web clips, highlights, and book notes can feel productive while doing little to transform information into insight. The workflow needs a consistent step that forces processing—moving from raw capture to permanent notes—otherwise the system becomes clutter rather than cognition. The goal is to make that tending routine feel manageable from day one, not something that only works after motivation returns.

To reduce friction, the approach emphasizes simplifying the process and automating what can be automated. One setup uses Readwise integrations with Snippt and Notion databases: Readwise exports highlights, saved tweets, articles, and notes into a single Notion table. That table is converted into a Kanban-style board, then items are dragged into a “doing” column for active processing. After processing, items move to “done,” which helps the user resume work quickly and keeps captured material separated from the knowledge-management workspace.

If the process must stay inside the knowledge tool itself, hashtags can provide lightweight structure. Notes can be tagged with statuses such as #doing or #to do, then queried to populate a journal view or a dedicated task list page. A simple “key” page listing the tags used in the workflow keeps the system from turning into a maze of rules.

Habit formation is handled through a practical routine design: stack the tending habit onto an existing daily trigger (for example, after brushing teeth, go to the desk and tend the knowledge garden). The routine should start with the easiest task available—such as reviewing fleeting notes or converting book highlights into notes—so the first steps are low-effort and help the mind enter focus. A time expectation is also offered: it typically takes about five to ten minutes to get into a focused mode, so starting small can make the session feel less like a chore.

Finally, the “short knowledge cycle” limits how long research is allowed to consume attention. Instead of collecting large quantities of material and postponing synthesis, the method sets a cap on research time and then spends the same sitting creating literature notes and permanent notes from what was gathered. That tight loop prevents highlight stacks from becoming overwhelming and keeps insights flowing.

Overall, the system is less about building a perfect toolchain and more about building a repeatable processing habit—using automation, simple tagging, and time-boxed cycles to ensure captured information turns into durable knowledge.

Cornell Notes

A second brain becomes useful when captured material is consistently processed into permanent notes. The biggest failure mode is the collector’s fallacy—saving highlights and clips without turning them into knowledge. To make tending routine easier, the workflow reduces friction with automation (Readwise → Notion table → Kanban board) or with simple status tags like #doing and #to do. Habit formation is built by stacking the task onto an existing daily trigger and starting with the easiest step (review fleeting notes or convert highlights). A “short knowledge cycle” time-boxes research and then immediately creates literature and permanent notes, preventing overwhelming highlight piles.

What is the collector’s fallacy, and why does it break a second brain?

The collector’s fallacy is collecting notes, web clips, and highlights without processing them into permanent notes or insights. It can feel productive because capture is fast, but it doesn’t contribute meaningfully to knowledge. The system needs a habit that forces the conversion step—turning fleeting items (highlights, literature notes, book highlights) into permanent notes—so the archive becomes usable knowledge.

How does the Readwise + Notion Kanban approach make processing easier?

Captured highlights, saved tweets, articles, and notes are exported into a single Notion table via Readwise integrations (with Snippt mentioned in the setup). That table is converted into a Kanban-style board. Items are dragged into a “doing” column when they’re ready to process, then moved to “done” once processed. This keeps everything synced in one place while separating raw capture from the actual knowledge-management work.

What’s an alternative to Kanban if the workflow must stay inside the knowledge tool?

Hashtags can act as lightweight status labels. Notes can be tagged with something like #doing for items currently being worked on. Queries for hashtag #doing or hashtag #to do can populate a journal view, and a separate task list page can be created from those queries. A simple key page listing the tags used in the workflow helps prevent clutter.

How should the habit be scheduled to avoid relying on motivation?

The routine is created by stacking it onto an existing daily habit and choosing a specific time and place. Example: after brushing teeth, go to the desk and tend the knowledge garden. Starting with the easiest task—reviewing fleeting notes or converting book highlights—helps the session begin quickly and reduces the sense of chore-like effort.

What is the “short knowledge cycle,” and how does it prevent overwhelm?

The short knowledge cycle sets a limit on how long research is allowed to run, then uses the same sitting to create literature notes and permanent notes from the researched material. Instead of collecting large quantities of research and trying to synthesize later, the method processes ideas immediately, so highlight stacks don’t grow into an overwhelming backlog.

Review Questions

  1. What specific step turns fleeting notes and highlights into knowledge, and why is that step essential?
  2. How do automation (Readwise → Notion → Kanban) and hashtag tagging (#doing, #to do) each reduce friction in processing?
  3. What does the short knowledge cycle time-box, and what two types of notes are created from the research during the same session?

Key Points

  1. 1

    Avoid the collector’s fallacy by building a routine that converts highlights and clips into permanent notes, not just saves them.

  2. 2

    Reduce friction by simplifying the tending workflow and automating the capture-to-triage steps where possible.

  3. 3

    Use a Kanban-style process (e.g., Notion “doing” and “done” columns) to make it easy to resume processing and track progress.

  4. 4

    If Kanban isn’t used, use status hashtags like #doing and #to do, then query them to generate task lists or journal views.

  5. 5

    Stack the tending habit onto an existing daily trigger (time and place) to make consistency more likely than motivation.

  6. 6

    Start with the easiest processing task first to enter focus quickly; plan for roughly five to ten minutes to get into a focused mode.

  7. 7

    Time-box research with a short knowledge cycle so literature notes and permanent notes are created in the same sitting, preventing highlight overload.

Highlights

Collector’s fallacy is the trap of saving highlights and clips without processing them into permanent notes—feeling busy while producing little knowledge.
A Readwise-to-Notion Kanban workflow turns captured items into a clear “doing” queue, then moves them to “done” after processing.
Hashtags like #doing and #to do can replace complex systems by powering simple queries for what’s next.
Habit stacking (e.g., after brushing teeth) plus starting with the easiest task helps the routine stick.
The short knowledge cycle limits research time and forces immediate synthesis into literature notes and permanent notes, keeping backlog manageable.

Topics

Mentioned