A Notion second brain is a small set of linked databases, a Notes inbox, Projects, Areas and a Resources view, organized with the PARA method so every note lives next to something you're actually working on. You can set it up on Notion's Free plan in an afternoon, and the structure below keeps it from turning into a digital junk drawer.
PARA's definitions are from Tiago Forte's own page (updated April 2026); Notion's view types and pricing are from Notion's help and pricing pages. The example and the time estimates are mine, and where I give an opinion I say so.
What is PARA, and why use it?
PARA sorts everything into Projects, Areas, Resources and Archives. Forte defines them this way: projects are short-term efforts with a goal, areas are ongoing responsibilities, resources are topics you're interested in, and archives hold anything inactive from the other three.
| Category | Definition (Forte) | Example |
|---|---|---|
| Projects | Short-term efforts with a goal | Finish Spanish language course |
| Areas | Ongoing responsibilities | Health, finances, writing |
| Resources | Topics of interest | Habit formation, photography |
| Archives | Inactive items from the other three | Completed or paused projects |
The point of PARA is to organize by actionability rather than by school-style subject. Forte argues that listing areas as if they were projects ("Hiring", "Marketing") hides how much work you've actually committed to, because areas never end. Break each one into projects with an outcome, such as "hire a designer by March", and your list turns over. That's his claim; I've found it holds for me, but it's an opinion about productivity rather than a measured result.
How should I structure the Notion databases?
Use three databases: Notes, Projects and Areas, with relations between them. Resources and Archives can be views or a status rather than separate databases.
| Database | Key properties | Notes |
|---|---|---|
| Notes | Title, Type (idea, quote, reference, meeting), Project (relation), Area (relation), Source URL, Status (Inbox, Filed) | Everything lands here first |
| Projects | Name, Status (Active, On hold, Done), Target date, Area (relation), Notes (relation) | Each has a finish line |
| Areas | Name, Standard (what "good" means), Review day | Never "done" |
Create linked views on your home page: Active Projects (a board grouped by Status), Inbox (Notes filtered to Status is Inbox), and Resources (Notes where Project is empty and Area is empty, sorted by Type). Notion's help center says you can link a view of another database into the current one, which is how you show a project's notes inside the project. Archiving is then just setting Status to Done or On hold, with an "Archive" view filtering those out of daily sight.
What does a worked example look like?
Take a freelance writer with the Area "Writing business" and three live projects. This is a made-up setup to show the shape:
| Area | Project (with finish line) | Example notes |
|---|---|---|
| Writing business | Publish 10,000-word guide by 15 December | Interview quotes, outline, source links |
| Writing business | Send 20 pitches in November | Editor contacts, pitch drafts |
| Health | Run a 10 km in spring | Training plan, shoe research |
A quote saved from an interview goes to Notes with the guide project selected. A random article about trail shoes goes in with the running project. A note with no home stays in the Inbox until the weekly review, when you either file it, link it, or delete it. If a note serves no project and no area, my opinion is it belongs in Resources only if you'd realistically search for it again.
What is the weekly review?
Ten to twenty minutes, once a week. Steps I use (opinion):
- Process the Inbox to zero by assigning a project or area, or deleting.
- Check each Active project for a next action and a date.
- Move finished or stalled projects to Done or On hold.
- Skim one area and ask whether it needs a new project.
Forte's book Building a Second Brain frames the wider workflow as Capture, Organize, Distill and Express. The Express step is where the notes pay off, whether as an article, a presentation or a book. If that's your goal, Interactive eBook Builder can turn the structure you already have into one: its Seed Prompt sets up the eBook's overall structure, Agent A Spec Builder writes the Chapter Plan, and the Packs Database's Research Pack holds sources for each chapter, so the project note and the chapter share the same material. For a book-specific Notion build see the Notion book writing template.
How do I turn a project's notes into a book?
Group the project's notes by idea, then give each group a chapter. A made-up 10-chapter guide might map like this:
| Note type | Where it goes in the book |
|---|---|
| Interview quotes | Examples inside chapters |
| Reference notes with source URLs | Fact-checked claims and a sources list |
| Ideas | Chapter hooks and takeaways |
| Meeting notes | Often nothing; leave them out |
Paste the grouped notes into your Chapter Plan rather than asking AI to invent content. Because Interactive eBook Builder has no subscription and allows unlimited eBooks, you can finish one project's guide and then re-run the Seed Prompt for the next without paying again, which suits a second brain that keeps producing new projects.
Which mistakes sink second brains?
Collecting without using. The usual failures, in my experience rather than from a study: capturing everything and processing nothing, building a database per topic so notes scatter, keeping areas with no project so nothing finishes, and spending the first week designing icons. Keep one Notes database, add relations, and delay any cosmetic work until the weekly review has run four times. If you have an attention-related reason to want fewer decisions, a Notion template for ADHD covers lower-friction layouts, and worksheets and checklists in Notion shows how to attach checklists to a project. When AI summarizes your notes, check its claims against the originals; stopping AI from making up facts explains how.
What does it cost?
Nothing, for one person. Notion's pricing page lists databases with custom properties and subtasks on Free, and says a solo Free workspace can add unlimited pages and blocks. File uploads on Free are limited to 5 MB, which matters if you save PDFs; Plus ($10 per member per month) allows 5 GB. Students and educators get Plus with a one-member limit free using a school email. Check the page for current pricing.
| Need | Free | Plus |
|---|---|---|
| Databases and custom properties | Yes | Yes |
| File upload size | Up to 5 MB | Up to 5 GB |
| Page history | 7 days | 30 days |
Once the capture system is working, a small habit database can sit beside it; the Notion habit tracker template walks through one.
Before you hit send
- Does every project have a finish line?
- Do all notes pass through one Inbox?
- Is the weekly review scheduled?
- Are areas broken into projects?
- Is anything in the system you won't search for again?
The takeaway: three databases, relations, and a weekly review make a second brain; the template matters less than the habit of filing notes next to the work they serve.