PARA & Building a Second Brain

Tiago Forte's PARA (Projects / Areas / Resources / Archives) and BASB (CODE) — output-oriented PKM.

PARA is the organisational scheme; BASB is the methodology. Tool-agnostic — works in Notion, Obsidian, Logseq, Apple Notes, even a paper folder. Pair with pkm-overview-methodologies; contrast with pkm-zettelkasten; GTD overlap in prod-task-gtd-apps; see also prod-note-taking-consumer, prod-knowledge-management-readwise, selfhost-notes-wiki.

PARA in one paragraph

Projects — outcomes with deadlines. "Ship Q3 release," "plan Tokyo trip."
Areas — ongoing responsibilities. "Health," "Engineering team," "Finances."
Resources — topics of interest you may want later. "Espresso," "Rust."
Archives — inactive items from the other three.
★ Sort by actionability, not topic. A note about "Tokyo" lives in the Project (this trip), the Area (travel-as-life), or the Resource (general Japan info) depending on whether it has a deadline.

★ Capture — keep what resonates. Don't capture everything — capture what surprised you, what you might use, what triggers an emotion.
★ Organise — file into PARA by actionability.
★ Distil — Progressive Summarisation. Bold the surprising sentences; highlight the bolded; one-line summary at the top.
★ Express — produce something: post, talk, deliverable. The point of the system.
Output is the metric. A second brain that doesn't ship is a museum.

★ Obsidian — folder-as-PARA; community plugins for project dashboards (Tasks, Dataview). Deep dive: pkm-obsidian-deep.
★ Logseq — namespace-as-PARA (Projects/Q3 launch); journal-anchored. Deep dive: pkm-logseq-deep.
★ Joplin — folder-as-PARA; mobile-friendly. See pkm-joplin-standard-notes.
Notion — paid + free; PARA in databases is the prototypical Forte example, but lock-in is real — see prod-note-taking-consumer.
AppFlowy / AnyType / AFFiNE — Notion-shape OSS; PARA in databases — see pkm-anytype-appflowy-affine.
Trilium / TriliumNext — tree + relations; explicit PARA structure — see pkm-trilium-silverbullet.

Layer 1 — capture. The article, the highlight.
Layer 2 — bold the sentences that made you stop reading.
Layer 3 — highlight the boldest of the bolds.
Layer 4 — one-line summary at the top.
★ Don't do all four upfront. Distil only when re-reading, and only if the note keeps re-surfacing. Most captures stay at layer 1 forever — that's fine.

★ Knowledge worker, project-driven: PARA fits the shape of work. Projects come and go; Areas stay.
Researcher / academic: PARA on top of Zettelkasten — Projects = papers, Resources = literature notes — works, but feels constrained. Zettelkasten alone is more flexible.
Hobbyist / autodidact: PARA can feel over-structured. LYT / MOCs are looser — see pkm-knowledge-graph-mocs.
Pure capture / journaling: overkill — see prod-daily-journaling and pkm-daily-weekly-review.

★ PARA + Zettelkasten — PARA is the project shelf; Zettelkasten is the idea graph. Permanent notes live in Resources; their MOCs in Areas; current writing in Projects.
PARA + GTD — Projects becomes the GTD project list; Areas is your areas-of-focus. See prod-task-gtd-apps.
PARA + Daily Notes — daily note links into Projects. Logseq / Obsidian both ergonomic here.

Folders by topic, not actionability. "Marketing" sounds like a project but is an Area. The split matters.
Archives that aren't truly archived. Move-to-archive must be cheap; otherwise people leave dead projects in the active list.
Capture > Express. A second brain that only captures is the most common failure. The output cadence is the system.

Tiago Forte — Building a Second Brain (2022). The book.
Forte Labs — BASB cohort (paid; ~$1,500). Brand-name course; the community is decent but the methodology is fully covered in the book.
PARA Method (2023, Forte). Standalone short book on PARA.
See pkm-learning-resources.

Project-driven work: PARA + BASB is built for you.
You ship deliverables: the Express step is the value.
You're paralysed by Zettelkasten's open-endedness: PARA's deadlines are grounding.
You're an academic or pure idea-generator: Zettelkasten / Evergreen will fit better — see pkm-zettelkasten, pkm-evergreen-digital-garden.
Tool pick: Obsidian (markdown, FOSS-flavoured) or Logseq (FOSS); avoid Notion if portability matters.