Skip to content

Chapter 2 of 7

Organizing Knowledge with PARA and Note Types

PARA is an organization framework built around four buckets: Projects, Areas, Resources, and Archives. Projects are short-term efforts with a clear outcome and deadline, such as launching a landing page or preparing an interview loop. Areas are ongoing responsibilities you must maintain over time, such as health, finances, management, or learning. Resources hold reference material and topic-based knowledge that may be useful in the future. Archives keep inactive material from projects, areas, or resources so it stays searchable without cluttering active work. Periodically, after a major life or work shift, a PARA migration moves existing notes between these buckets to reflect what is actually current.

Within PARA, three classic note types do most of the work. A reference note stores facts, definitions, or source material that supports future work. A project note tracks thinking, decisions, and resources tied to a specific active outcome. A source note captures key ideas from a book, article, podcast, or video while preserving attribution, so you can locate the original later. None of these are useful without context, because even an accurate idea is unusable on revisiting if the circumstances that made it matter are not recorded. For this reason, capturing and processing are kept separate: capture stays fast while a later moment is reserved for organization. Source material should be attributed clearly to prevent confusion, support credibility, and make it easy to revisit the original; a source map—a note listing the primary sources, authors, and references behind a topic—can be especially useful when several atomic notes draw from overlapping material. A summary note that condenses a single source into its key claims and personal takeaways serves a related purpose but stays distinct from atomic notes.

A few conventions make retrieval far more reliable. Notes should be written in your own words, because rewriting improves understanding and makes notes more useful on re-reading. Evergreen notes are atomic—capturing one idea per note—so they can be linked, refined, and reused without confusion. Effective note titles are specific and descriptive enough that you can predict the note's value before opening it. Tags often matter less than people expect: too many become messy quickly, so strong titles, links, and search usually outperform elaborate tag schemes. Linking notes helps ideas reinforce each other and exposes patterns, and templates reduce friction for recurring note types like meeting notes, reading notes, and project briefs.

All chapters
  1. 1Foundations of Personal Knowledge Management
  2. 2Organizing Knowledge with PARA and Note Types
  3. 3The CODE Method and Progressive Summarization
  4. 4The Zettelkasten Tradition
  5. 5Getting Things Done and Task Management
  6. 6Modern Note Networks and Maps of Content
  7. 7Workflows, Reviews, and Long-Term Knowledge Health

Drill it

Reading is not remembering. These come from the Knowledge Management deck:

Q

What is personal knowledge management (PKM)?

Personal knowledge management is the practice of capturing, organizing, and reusing information so it becomes easier to think, create, and make decisions.

Q

Why is capture important in a PKM system?

Capture prevents useful ideas from vanishing and reduces the mental load of trying to remember everything in real time.

Q

What makes a good capture habit?

A good capture habit is fast, low-friction, and consistent across devices so ideas can be saved before they disappear.

Q

What is the difference between collecting and curating?Collecting saves information broadly

curating filters, labels, and keeps only what is likely to be useful later.