Notion Office Hours: Building a Second Brain 🧠

Notion Office Hours frames “building a second brain” as a practical system for turning scattered information into usable output—by organizing knowledge around projects, areas, resources, and an archive (PARA). The core idea is that a reliable external system should store, organize, and progressively refine information so it can later be transformed into decisions, plans, and finished work. In this setup, projects hold active outcomes, areas cover ongoing responsibilities, resources collect reference material for future action, and archives become a low-stakes dumping ground for old material.

A major takeaway is how strongly the workflow depends on databases and relationships rather than page-by-page note-taking. Maria Aldri describes using PARA since 2015 and building a Notion workspace that keeps everything “one click away” through linked databases. Her projects are managed through a master ideas database that feeds into specific project views using filters (e.g., filtering by status such as “not done,” “in progress,” or “someday”). Requirements for each project are tracked via a related tasks/requirements structure, with rollups calculating completion percentages. She also maintains separate project groupings like active projects and “someday projects,” plus a long-term goals area.

Resources are treated as a pipeline, not a storage bin. She saves web material via the Web Clipper into an inbox, then curates on a schedule—assigning statuses such as whether content is reviewed, needs “Binet summarization” (progressive summarization), or is ready to be used. Each resource gets a quick description and is tagged by themes and linked to relevant projects. For her work—YouTube videos, blog posts, social media, and coaching—resources are only kept if they’re likely to be useful later, and they’re surfaced through filters or relational links when a project needs inspiration. She also emphasizes that the system should match how a person actually works; even two productivity consultants can end up with very different Notion structures.

The session also tackles execution: a “Start Here” workflow pushes the user toward what to do next, combining daily habits with weekly, monthly, and quarterly planning. Maria’s approach uses role-based planning (technical execution, managerial planning, and long-range envisioning) to reduce decision fatigue. She tracks progress through formula-driven fields like a “deadline status” that calculates days until completion and uses rollups to compute completion based on related tasks.

Beyond second-brain storage, the discussion clarifies that “getting things done” and “building a second brain” overlap but aren’t identical. PARA is more about knowledge capture, organization, and summarization; action comes from connecting that knowledge to projects and tasks. The conversation closes with practical guidance for beginners: start small, build one project at a time, and avoid copying complex templates without adapting them to personal workflow. The most consistent message is that Notion’s flexibility can feel overwhelming, but a structured PARA foundation—plus recurring review habits—turns that flexibility into a system that supports both messy thinking and concrete output.