A second brain is a personal knowledge system: one trusted place where ideas, notes, and lessons go so your actual brain can focus on thinking instead of remembering. The concept comes from Tiago Forte's Building a Second Brain method, built on two frameworks — CODE (Capture, Organize, Distill, Express) and PARA (Projects, Areas, Resources, Archives). Notion is one of the best homes for it, because databases let you store everything once and view it many ways. Notion AI then takes over the tedious parts: summarizing, categorizing, drafting, and answering questions across your notes. Here is the full workflow, step by step.
What you actually need
You can build the entire system on Notion's free plan. Databases, pages, backlinks, templates, the web clipper, and database relations are all included free. What costs money is the AI layer: Notion AI is bundled with the Business plan ($20 per member per month on annual billing), while Free and Plus plans only get a limited trial of AI features. If you stay on the free plan, you can still build everything below and paste AI summaries in from Claude or ChatGPT — you just do it manually. The paid AI is about removing that friction, not about unlocking the system itself.
Start with one Notion workspace page called "Second Brain". Everything in this guide lives under it, so the system is portable: you can duplicate the page or share it with a team later.
Step 1: Build your capture inbox
CODE's first step is Capture — get ideas out of your head fast, before they evaporate. Create a simple database called "Inbox" with just three properties: Title, Created time, and Status (select: New, Filed, Actioned).
Friction is the enemy here. On your phone, put the Notion app on your home screen and use the Quick Capture button. On desktop, install the Save to Notion browser extension so any article, thread, or page you read can be sent to the Inbox in two clicks. Voice memos work too: record on your phone, transcribe later, drop the transcript in.
The rule that keeps an inbox from becoming a graveyard: capture is a holding area, not a destination. Every item that enters the Inbox must either be filed into the PARA system, turned into an action, or deleted. Nothing lives in the Inbox permanently.
Step 2: Set up your PARA databases
PARA sorts every note by actionability. Projects are active efforts with a goal and deadline (launching a website, planning a trip). Areas are ongoing responsibilities with no end date (health, finances, career). Resources are reference topics you want to learn or revisit (AI tools, recipes, negotiation tactics). Archives hold finished or inactive items from the other three.
In Notion, create three databases (Archives can just be a filtered view of the others):
Notes database. The heart of the system. Properties: Title, PARA (select: Project, Area, Resource, Archive), Status (select: Seedling, Evergreen, Archived), Tags (multi-select), Created, and Summary (text). A "Seedling" is a fresh capture you have not processed yet; an "Evergreen" note is one you have distilled and would reference again.
Projects database. Properties: Name, Area (relation to an Areas database if you make one), Deadline (date), Status (select: Active, Waiting, Done), and Notes (relation to the Notes database). Relating notes to projects is what makes retrieval instant later — open a project and see every note attached to it.
Ideas / Reading list database. Properties: Title, Source (URL or text), Type (select: Article, Book, Video, Podcast, Tweet), Why I saved it (text), and Processed (checkbox). The "Why I saved it" field is the single most valuable habit in this system — one sentence of context ("stat for the Q3 pitch") makes a saved link ten times more useful a year later.
Do not over-engineer. A few essential fields beat a dozen columns you never fill. You can always add properties later once the habit is established.
Step 3: Distill with Notion AI
CODE's third step is Distill — squeezing raw captures into concentrated value. This is where Notion AI earns its keep. For any long captured note, open it, press the AI button (space bar in an empty block, or type /ai), and ask it to summarize in two to three sentences. Paste that at the top of the note in a callout block. Forte calls these "atomic summaries", and they are what let you reuse a note in thirty seconds instead of re-reading five pages.
Three AI workflows worth building:
AI autofill in databases. Add an "AI summary" property to your Notes database and use Notion AI's autofill to generate summaries for entire database views at once. A hundred raw captures becomes a hundred scannable one-liners, so your weekly review (step 5) takes minutes instead of hours.
Action-item extraction. For meeting notes, select the page and ask Notion AI to extract action items with owners and deadlines. Feed those directly into your Projects database instead of retyping them.
Draft generation. When Express (the final CODE step) means turning notes into output, start from your distilled notes: ask Notion AI to draft the outline for the article, report, or post from the notes tagged for that project. The draft will be rough — always edit — but the blank-page problem disappears.
Notion AI is not the best writer or reasoner compared to Claude or ChatGPT; its advantage is context. It reads your whole workspace, so it summarizes your notes, not generic internet text.
Step 4: Connect and retrieve with Q&A
A library is static; a second brain is a network. Linking is the mechanical part: whenever a note relates to another, type @ and link it, or use the [[ ]] syntax. Then build a "Map of Content" — a master note for each big topic (e.g. "Content Marketing Playbook") that links to every related note. These hubs become your starting point whenever you need to produce something on that topic.
Retrieval is the AI part. Notion's AI Q&A lets you ask questions across your entire workspace in plain language: "What did I learn about email subject lines?" or "Find all notes about the client who complained about pricing." Instead of remembering which project a note was filed under, you ask for it. For teams on the Business plan, Enterprise Search extends this to connected tools, and Notion Agent can perform multi-step work — draft a briefing from your research notes, then update the relevant project pages.
This is the step that turns a note archive into something you actually query. Most systems fail because people capture and file but never retrieve. If asking a question of your notes is easier than Googling, you will use the system.
Step 5: Run the weekly review
A second brain rots without maintenance. Block 30 minutes once a week and run this checklist:
1. Open the Inbox. For each item: file it into PARA, convert it to an action, or delete it. Empty the inbox completely.
2. Scan the Notes database for Seedlings and either distill them (add the atomic summary) or delete them.
3. Review Active projects: update statuses, move finished ones to Archives.
4. Ask Notion AI Q&A one question about your week ("What did I capture about pricing this week?") to surface forgotten material.
Treat the review as non-negotiable as a dentist appointment for the first month. After that the habit usually holds on its own because the system starts paying you back — every review makes retrieval better.
Common mistakes to avoid
Organizing before you have anything to organize. Start with 3–5 active projects, not a taxonomy of your whole life. Capture first, structure emerges.
Hoarding without distilling. A note you never summarize is a note you will never find useful. If you cannot be bothered to write one sentence about why you saved something, delete it.
Too many tools. Run the whole system in Notion. Splitting notes across Notion, Apple Notes, Google Docs, and a bookmark manager means retrieval never works — keep one home.
Perfectionism. A messy system you use beats a beautiful one you abandon. Design for easy restarts, not perfection.