Skip to content
Tutorials Center
My learning

Topics

Lesson 30 of 36 ยท Workflows and Systems

PARA and the Second Brain

Organize Notion with the PARA method: Projects, Areas, Resources and Archive. Learn the databases, relations and weekly habits that make a second brain work.

After a few months most Notion workspaces look the same: dozens of pages with no clear home. A system fixes this. One popular system is PARA, a way to sort everything you keep into four buckets so you always know where something belongs and what can be put away.

Notion cannot run on this site. This lesson describes how to set the system up in the real app, and uses labelled JavaScript stand-ins to practice the decisions behind it.

The four buckets

PARA at a glance

Projects Goals with an end date
Areas Ongoing responsibilities
Resources Topics you may use later
Archive Finished or paused

Sort by how actionable something is, not by topic.

1 / 2
  • Projects: a short-term outcome with a finish line: "Launch the newsletter", "Plan the trip".
  • Areas: a standard you maintain with no end: Health, Finances, Team management.
  • Resources: reference material by topic: Recipes, Design inspiration.
  • Archive: anything inactive from the other three.

The key rule: a page lives in the bucket that matches how actionable it is today. When a project ends, it moves to the Archive; a resource you start using for a goal links into a Project.

Building it in Notion

A robust setup uses databases, not nested pages, because databases let you filter and relate things.

  1. Create databases: Projects, Areas, Resources, Tasks, Notes.
  2. Add a Status property to Projects (Planning, Active, Paused, Done) and a Deadline date.
  3. Add relations: Tasks to Projects, Projects to Areas, Notes to Projects or Resources. (See the Relations and Formulas chapter of this track if you need a refresher.)
  4. Create a Home page with linked views: Active projects, Tasks due this week, Recently edited notes.
  5. Add a Type select to the Notes database if you prefer one shared table: Project note, Area note, Resource, Archived.

If you prefer one database for everything, add a single PARA select (Project, Area, Resource, Archive) and filter views by it. Fewer databases means less to maintain.

Stand-in: where does it belong?

A rule-of-thumb classifier in JavaScript. This is only a model of the decision, not a Notion feature.

JS Stand-in: PARA sorter

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The weekly review

A system decays without upkeep. Spend 20 minutes weekly:

  1. Empty the Inbox: every new note or task gets a bucket and a project.
  2. Review Active projects: is each one moving? Is a next action written?
  3. Move finished work to Archive (use a status, not deletion).
  4. Check Areas for neglected items.
  5. Pick the top three priorities for next week.

Stand-in: spotting stale projects

This stand-in lists active projects that have not been touched recently, which is exactly the view you would filter for in a review.

JS Stand-in: stale project finder

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Common pitfalls

  • Too many databases. Start with Projects, Tasks and Notes; add more only when you feel pain.
  • Capturing without processing. Notes that never leave the inbox are just a pile.
  • Over-designing. A plain system you use beats a beautiful one you abandon.
  • Mixing topic and action. "Marketing" is an Area or Resource; "Launch campaign" is a Project.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. Which PARA bucket fits "Maintain my finances" with no end date?

    An ongoing responsibility with no end date is an Area.
  2. 2. Why does PARA suggest databases instead of nested pages?

    Databases give you filters, relations and linked views, which keep the system flexible.
  3. 3. What happens to a finished project?

    Finished work is archived, not deleted, so it stays searchable.

Summary

  • PARA sorts work into Projects, Areas, Resources and Archive by actionability.
  • Build it with linked databases and a Home page of filtered views.
  • A weekly review keeps the system alive.
  • Start small and add structure only when needed.

Next: A Task Management System