summary

Tiago Forte - How a GTD Master Trainer Uses PARA

Thumbnail of the video “Tiago Forte - How a GTD Master Trainer Uses PARA”
Community upload. AI output has not been independently verified.

Short Summary

Main recommendation: Organize notes with the PARA system (Projects, Areas, Resources, Archive) but adapt it with an Inbox, a separate Action Support stack, a Someday Maybe stack, and tag-based organization for Resources, plus a Zettelkasten Slip Box for building linked insights. The speaker is a student of Tiago Forte's Building a Second Brain course presenting his own evolved implementation of PARA in a video message to Tiago Forte, which he has used for several months.

Key Points

  • The speaker's setup starts with an Inbox for incoming notes to process (roughly one week's worth at a time).
  • Project Support holds ongoing projects, each prefixed with a life area (e.g., a letter-style prefix), and completed projects move to Archive.
  • A separate Someday Maybe stack was added because out-of-sight notes tagged "someday maybe" were lost; a stack makes it easy to move projects in and out as priorities change.
  • Resources are handled in one catch-all "Notebook" organized by hashtag topic tags, not by separate notebooks per category, which the speaker found more flexible than classic PARA.
  • A Slip Box stack uses the Zettelkasten method (created by Niklas Luhmann) to build a network of numbered, linked notes from reading insights.

Details Worth Noting

  • Concrete instructions:
    • Create an Inbox stack and process incoming notes regularly, moving each note to the appropriate stack.
    • Create an Action Support stack for single notes tied to a specific action, rather than placing them inside projects.
    • Prefix each project name with its life area so projects sort by area.
    • When a project is finished, move it to the Archive stack.
    • Keep Someday Maybe projects in their own stack so they remain visible and can be swapped with active projects.
    • For Resources, use one notebook and apply hashtag topic tags (e.g., #management or #attention) instead of creating a notebook per topic.
    • Use Entity tags for people or authors (e.g., tagging all notes by a given author with that person's name), and document-type tags (e.g., "receipt" or "questions to ask") where useful.
    • Add insights from reading to the Slip Box, numbering each note to create a hierarchy and linking it to existing notes so future writing draws on prepared material.
  • The speaker notes the system has evolved from classic PARA and is intended to be used for a longer period before further changes.
  • Progressive Summarization is applied to Resource notes that are needed for research or reference.
  • The speaker considers this structure complete and invites the instructor to consider it as a case study.

Bottom Line

The core value of this setup is adapting PARA's rigid notebook-per-category structure into a flexible model: tag-based resources, a visible Someday Maybe stack, and a Zettelkasten layer for insights, so information stays accessible and reusable.