mem1.wiki

Methods

Method

PARA

Tiago Forte's organising scheme for personal knowledge — Projects, Areas, Resources, Archive. Pragmatic file-cabinet shape for execution-oriented PKM. The right scaffolding for Notion-style team workspaces; the wrong shape for thinking.

Source
https://fortelabs.com/blog/para
Taxonomy
methods.pkm
Origin
Tiago Forte (2017)
Primary source
https://fortelabs.com/blog/para
Domain
pkm
Maturity
mainstream
Primary artifacts
Projects (active outcomes with deadlines), Areas (ongoing responsibilities), Resources (reference material), Archive (inactive items)

Core idea

Organise all personal information by actionability, not topic. Four top-level buckets:

  1. Projects — has a deadline and a defined outcome.
  2. Areas — ongoing responsibility, no end state (health, finances, a team you run).
  3. Resources — topics of interest you might draw on later (no current commitment).
  4. Archive — anything inactive from the other three.

The same item moves between buckets as its status changes. Categorisation by topic is explicitly de-emphasised; you’ll find your stuff by context, not by ontology.

Why it works

PARA fits how working professionals actually use information: most of it is in service of something they’re trying to ship, not something they’re trying to learn. Anchoring on actionability cuts the ceremony of “where does this belong?” almost to zero.

Where it works

Where it fails

Sources

How PARA compares

AI-generated editorial comparisons against nearest peers (glm-4.6). Cached at build time; regenerate via node scripts/build-comparisons.mjs.

vs ZettelkastenAI · cached

PARA and Zettelkasten trade immediate execution for long-term insight. PARA wins for shipping work; it is a pragmatic file-cabinet designed to clear your desk. It anchors information to "Projects" with deadlines, making it perfect for consultancies or founders who need to access active resources without ceremony. However, this utility focus blinds it to the unexpected: if an idea doesn't serve an active goal, PARA treats it as passive clutter, leaving no space for concepts that are simply interesting.

Zettelkasten, by contrast, is built for thinking, not doing. It encourages "atomic" notes that link densely over time, fostering a bottom-up structure where surprising connections emerge. This method excels for researchers or writers building a complex theory over years, but it fails as a productivity system. The flywheel requires months of unrewarded effort to yield results, and because it relies on personal associations, it collapses in multi-team environments. Use Zettelkasten to explore a problem, but switch to PARA when you are ready to execute the solution.

Related

Tools

  • AnytypeObject-oriented, local-first, end-to-end encrypted PKM with P2P sync via the Any-Sync protocol. Architecturally the most ambitious tool in this list; the UX still trails Notion and Obsidian.
  • CapacitiesObject-based PKM that splits the difference between Notion's databases and Roam's daily-notes. Cleanest object model in the consumer PKM space; cloud-only is the main reason to skip it.
  • NotionBlock-and-database hybrid that became the default team wiki. Strong for structured project bases, weak as a personal thinking tool — too many features compete for attention.
  • ObsidianLocal-first markdown editor with bidirectional links and a deep plugin ecosystem. Best-in-class as a personal thinking surface; weakest for real-time team collaboration.

Methods

  • ZettelkastenLuhmann's slip-box method — atomic notes, dense linking, no rigid hierarchy. Foundational influence on every modern bidirectional-link PKM tool. Easy to romanticise, hard to actually run.

Anti-patterns

  • The read-only wiki nobody updatesThe Confluence / Notion / wiki space that everyone references and nobody edits. Drifts from reality, nobody trusts it, but it stays up because removing it feels worse than ignoring it. The default end state of most team knowledge bases.