Getting Things Done (GTD) and Personal Knowledge Management address different but deeply complementary problems. GTD manages the flow of actions and commitments; PKM manages the accumulation and synthesis of knowledge. Most productive knowledge workers eventually build systems that integrate both, whether they realize it or not.
GTD Overview
David Allen published "Getting Things Done" in 2001, and it became the most influential personal productivity framework of the twenty-first century. The system rests on a core insight: your mind is for having ideas, not holding them. Any commitment, task, or "open loop" that lives only in your head consumes cognitive resources through what Allen calls "psychic RAM." The remedy is a trusted external system that captures everything and processes it into actionable next steps.
GTD operates through five stages:
Capture everything that has your attention into an inbox. The inbox can be physical, digital, or both. The only rule is that nothing stays in your head.
Clarify each item by asking: "Is this actionable?" If yes, determine the next physical action. If the action takes less than two minutes, do it immediately. If it requires multiple steps, it becomes a project.
Organize clarified items into appropriate lists: next actions (by context), projects, waiting-for, someday/maybe, and reference material.
Reflect through regular reviews. The Weekly Review is the cornerstone ritual: review all projects, update next actions, process loose items, and get current. Without the review habit, the system degrades.
Engage by choosing actions based on context, time available, energy, and priority. The system is designed so that when you sit down to work, you are choosing from pre-processed options rather than deciding what to do from scratch.
Mind Like Water and the Trusted System
Allen's metaphor of "mind like water" describes the state achieved when every open loop has been captured and organized. Like water responding to a stone, you react proportionally to events because nothing is competing for background cognitive attention. This state depends entirely on trust: you must trust that your system contains everything, or your mind will continue its anxious background scanning.
The concept of a "trusted system" is Allen's most important contribution to productivity thinking. A system that captures 90% of your commitments is not 90% as good as one that captures 100%. It is essentially worthless, because your mind cannot relax its vigilance unless it trusts the system completely.
Where GTD Ends and PKM Begins
GTD's reference filing system is deliberately simple: if it is not actionable but might be useful later, file it where you can find it. Allen offers no framework for developing ideas, connecting concepts, or building knowledge over time. Reference material in GTD is static. You file it and retrieve it; you do not grow it.
This is exactly where PKM takes over. PKM handles the knowledge layer: ideas, insights, concepts, questions, and their interconnections. A Zettelkasten note is not a reference file; it is a thinking artifact that participates in an evolving network of ideas. GTD asks "what do I need to do?" PKM asks "what do I know, and what does it mean?"
The Action Layer and the Knowledge Layer
Many practitioners converge on a two-layer architecture:
The action layer (GTD or a GTD-inspired system) manages tasks, projects, deadlines, contexts, and commitments. It is oriented toward execution and completion. Items flow through it and eventually leave.
The knowledge layer (PKM) manages notes, ideas, sources, and their connections. It is oriented toward understanding and emergence. Items flow into it and accumulate over time, becoming more valuable as the network grows.
The two layers interact at specific touch points. A meeting note might produce both action items (GTD) and knowledge notes (PKM). A research session might clarify a project's next actions while also generating permanent notes. The capture habit serves both systems simultaneously.
BASB vs GTD
Tiago Forte's Building a Second Brain (BASB) is often positioned as a successor to GTD, but it is more accurately a bridge between GTD and PKM. Forte's PARA system (Projects, Areas, Resources, Archives) maps closely to GTD's organizational categories, but adds the concept of progressive summarization and the "intermediate packet", which are knowledge management practices.
Where GTD is action-first and treats knowledge as reference, BASB is project-first and treats knowledge as raw material for creative output. BASB inherits GTD's capture discipline but extends it into a system where captured material is progressively refined and eventually deployed in projects.
The difference is philosophical. GTD optimizes for stress-free productivity through complete capture and processing. BASB optimizes for creative output through knowledge reuse. Neither alone covers the full spectrum of knowledge work.
Integration Patterns
Practitioners commonly integrate GTD and PKM in several ways:
Shared inbox, divergent processing. Everything enters one inbox. During processing, actionable items go to the task manager (GTD), and knowledge items go to the PKM system (Zettelkasten, BASB, etc.).
Daily notes as bridge. A daily note serves as both a GTD capture surface and a PKM processing log. Tasks, ideas, and observations coexist in the daily note and are later routed to their respective systems.
Weekly review as integration point. The GTD Weekly Review is expanded to include PKM maintenance: reviewing recent notes, connecting ideas, identifying knowledge gaps alongside task gaps.
Context links between layers. Tasks reference relevant knowledge notes; knowledge notes reference the projects they support. The two layers remain separate but navigable.
Key Points
- GTD manages action (what to do); PKM manages knowledge (what to know and think)
- The "trusted system" concept from GTD is equally essential for PKM: a system you do not trust, you will not use
- BASB bridges GTD and PKM but fully replaces neither
- Most productive knowledge workers operate a two-layer system whether they name it or not
- The capture habit and the weekly review are shared rituals that serve both layers
Open Questions
- Can AI agents unify the action and knowledge layers into a single coherent system?
- Does the two-layer architecture create unnecessary friction, or is the separation essential?
- How should recurring knowledge tasks (review, connect, prune) be represented in a GTD system?
References
- David Allen, "Getting Things Done: The Art of Stress-Free Productivity" (2001, revised 2015)
- Tiago Forte, "Building a Second Brain" (2022)
- Soenke Ahrens, "How to Take Smart Notes" (2017)
- David Allen, "Making It All Work" (2008)