Build a Second Brain in Under an Hour

We do not need a second brain that looks impressive. We need a place to put useful things so they do not vanish when a project gets busy.

PARA is a plain filing method. It has four buckets: Projects, Areas, Resources, and Archive. It works in Notion, Obsidian, Capacities, Logseq, or the note app we already use. The point is not to save everything. The point is to find the few things that help with work now.

Set the timer and make four homes

Take ten minutes and make four top level folders or pages. Projects are short term outcomes with an end. Areas are parts of life that need care but do not end. Resources are topics we may want later. Archive is where inactive things go.

• Projects: launch the new site, plan a holiday, hire an assistant.
• Areas: health, finances, team leadership, home.
• Resources: cooking, public speaking, product research.
• Archive: finished launches, past trips, old role notes.

Use the test that keeps filing easy

When a note arrives, ask: what am I likely to use this for next? Put it with the active project if it helps a current outcome. Put it in an area if it supports a responsibility. Put it in resources if it is only a useful topic. If it has no likely use, close it or delete it.

This is why PARA works better than a huge tag list for many people. The question is about action, not about finding the perfect subject. An article about sleep could sit in Health today and move to Archive later. That is fine.

Organize notes for the work in front of you, not for a future version of you with endless free time.

A starter template

For any active project

• Outcome: write one sentence describing done.
• Next step: write the smallest action you can take.
• Notes and links: add only material that helps the outcome.
• Decisions: record choices that you do not want to debate twice.
• Finish date: move the whole project to Archive when the work ends.

In Notion, this can be one project page with linked notes below it. In Obsidian, it can be a project folder and a single overview note. Capacities and Logseq can hold the same structure with objects or pages. Do not rebuild the system when you switch apps. Move the four buckets first.

Keep it from becoming another chore

Spend five minutes once a week looking at Projects. Archive finished work. Move stalled work back to Resources or Someday if it is no longer a commitment. Do not spend an hour cleaning every resource note. Search is good enough for most old material.

The hour setup is successful if we can answer two questions fast: what are we working on now, and where did we save that useful thing? Everything else is extra.

What to leave out

Do not create folders for every possible topic. Do not copy a large template before you have used it. PARA works because a current project gives a note a reason to exist. A note with no use can wait in Resources or disappear.

For one week, file only notes that help an active project or a real area of responsibility. When you finish that project, move its folder to Archive. This one move teaches the habit faster than a long cleanup session.

• Keep the next step small enough to test this week.
• Change one rule at a time, so we know what helped.
• Keep what makes the work easier and drop the rest.

Bottom line

Make the four buckets now and add one active project. Use the system for your next piece of work before changing a single setting.