Getting Things Done, the productivity system David Allen first published in 2001 and revised in 2015, has outlasted dozens of competing methodologies because it solves a real problem rather than selling an aesthetic. The premise: the human brain is bad at remembering, prioritizing, and tracking open commitments, and the mental tax of trying to do those things in your head leads to anxiety, missed work, and the feeling that nothing is ever fully under control. GTD’s answer is to move all commitments out of the head and into a trusted external system, then process that system on a regular cadence. This guide covers the five steps in plain language, the weekly review that makes the whole thing work, and the most common reasons people abandon the system after a few months.
The core insight
The brain is a terrible filing cabinet. It does not surface tasks when they are relevant. It surfaces them at 2 AM when they are not actionable. It also produces a constant low-grade anxiety about everything that might be open, which Allen calls “open loops”. The more open loops the brain is tracking, the less capacity remains for actual thinking and creative work.
GTD’s job is to close those loops by externalizing every commitment. Once the brain trusts that the system has captured everything, it stops running the background-anxiety process. That trust is the whole point of the system, and the trust is earned only by maintenance.
The five steps
Step 1: Capture. Get every open commitment out of the head and into an inbox. Email inboxes, paper inboxes on the desk, a notes app, a voice memo, a notebook page. The capture step does not require deciding what to do with anything. It just requires noting that the thing exists. The mental rule is simple: if something is occupying mental bandwidth, capture it.
Step 2: Clarify. For each captured item, ask: what is this, and what is the next physical action? If there is no next action (it is reference material, or someday/maybe, or just an idea), file it. If the next action takes less than two minutes, do it now. If it requires multiple steps, it is a project; capture the project and identify the next action that moves it forward. The clarify step is what most casual GTD users skip, which is why their systems collapse.
Step 3: Organize. Put each clarified item where it belongs. Calendar for date-specific items. Next-actions list for everything to be done as soon as possible. Project list for multi-step outcomes. Reference for material to be looked up later. Waiting-for list for things blocked on someone else. Someday/maybe for things that might happen but are not committed. The organization is the filing cabinet that the brain trusts.
Step 4: Reflect. Review the system regularly. Daily review (5 to 10 minutes) for the calendar and next-actions list. Weekly review (60 to 90 minutes) for the entire system. The reflect step is the keystone. Skip it for two weeks and the system stops working.
Step 5: Engage. Actually do the work, with confidence that the system is showing the right thing. The engagement step pulls from the next-actions list filtered by context, time available, and energy level. The system does the thinking about what to do; the human does the doing.
The two-minute rule
Embedded in the clarify step is the two-minute rule: if processing a captured item reveals that the next action takes less than two minutes, do it immediately instead of organizing it for later. The overhead of capturing, filing, and re-finding a two-minute task is usually larger than the task itself.
In practice, the rule clears the small obligations that would otherwise pile up: confirming an appointment, sending a one-line reply, filing a paper, adding a name to a list. Without the rule, these accumulate and the next-actions list bloats with trivial items that obscure the real work.
The catch is that two minutes is easy to misjudge. An email that looks like a two-minute reply turns into a fifteen-minute thread. The rule is a heuristic, not a guarantee, and applying it requires honest estimation.
Contexts
GTD organizes next-actions by context: @computer, @phone, @office, @errands, @home, @waiting-for. The point is that the right action depends on where the user is and what tools are available. Standing in a grocery store, the @errands list is the relevant view. Sitting at a desk, the @computer list is the relevant view.
In 2026, contexts have become less rigid because most knowledge work happens on a single device that goes everywhere. Many GTD users now organize by area (work, personal, health, learning) rather than physical context. The principle holds: filter the list to what is doable in the current situation.
The weekly review
The weekly review is the single most important habit in GTD, and it is the one users skip first. The full version takes 60 to 90 minutes and covers:
- Process all inboxes (email, paper, notes app, voicemails) to zero.
- Review the calendar for the past week (anything to capture from completed events) and the next two weeks (anything to prepare for).
- Review the projects list. Confirm each project has a next action, mark completed projects done, add new ones.
- Review the next-actions list. Remove completed items, re-context anything that has changed, defer anything that no longer fits the week.
- Review the waiting-for list. Follow up on anything stale.
- Review the someday/maybe list. Activate anything that has become a current project, archive anything that has gone cold.
- Look at the next week and decide on priorities.
Doing this on Friday afternoon or Sunday evening means the next week starts with a clean slate and full trust in the system. Skipping it means starting each week half-blind.
A structured weekly review protocol is worth setting up once and following religiously.
Picking tools
GTD is tool-agnostic. The original book describes a paper-and-folders implementation that still works. Modern digital options include:
- Todoist. Strong context filtering, recurring tasks, cross-platform sync. The most popular GTD-friendly app.
- Things 3. Apple-only, beautifully designed, fits GTD almost natively.
- OmniFocus. The most GTD-purist app, Apple-only, deep customization, steep learning curve.
- TickTick. Cross-platform, lower cost, includes calendar and Pomodoro features.
- Notion or Obsidian with templates. Maximum flexibility but requires setup and maintenance.
Picking the right tool matters less than committing to a tool and using it for at least three months. Switching apps every six weeks is itself a sign that the system is not working, and the actual problem is rarely the tool. Decide between a calendar and a task app early to avoid duplicating work.
Why GTD fails most users
Common failure modes:
- Capture without process. Items accumulate in the inbox because the clarify step is skipped. The inbox grows to thousands of items. The system feels overwhelming. The user quits.
- Skipping the weekly review. The single most common failure. Without weekly maintenance, contexts go stale, projects accumulate, and trust collapses.
- Over-engineering the setup. Spending three weekends in Notion building the perfect GTD template, then never using it. The system is the daily habit, not the dashboard.
- Treating every captured item as urgent. GTD does not say everything must be done; it says everything must be captured and decided. Many captured items belong in someday/maybe or get deleted on review.
The honest framing
GTD is not a productivity religion. It is a discipline for closing open loops so the brain has more room to think. The five steps and the weekly review have survived twenty years because they address a problem that did not go away when the tools changed. Read the summary, pick a tool, run the system for ninety days with weekly reviews, and the value (or the lack of fit) becomes obvious. Most users who give it a real ninety days keep it for the rest of their careers.
See our /methodology page for how we evaluate productivity systems and tools.
Frequently asked questions
Is GTD still relevant in 2026 with modern apps and AI assistants?+
Yes, more than ever. AI assistants like ChatGPT, Claude, and Google Gemini handle the execution of individual tasks faster, but they do not solve the upstream problem GTD addresses: deciding what to work on and capturing every commitment somewhere outside the brain. The five-step workflow (capture, clarify, organize, reflect, engage) works identically whether the task list lives in a paper notebook or in Todoist with AI auto-prioritization. The underlying principle is older than any specific tool.
Do I need to read the whole book to use GTD?+
No, but reading the book makes the system work better. The 2015 revised edition of Getting Things Done is about 350 pages and most of it is examples and context. The actionable system can be summarized in 30 minutes, and that summary is enough to start. The book matters because it covers edge cases (what to do with someday/maybe items, how to handle reference material, how to recover when the system breaks down) that summaries skip. For users who try GTD lite and fall off after two months, reading the book often gets them back on track.
What is the two-minute rule and does it actually work?+
The two-minute rule says: if a task takes less than two minutes, do it immediately instead of capturing it for later. It works because the overhead of writing down, organizing, and scheduling a two-minute task often exceeds the task itself. Reply to a quick email, file a paper, send a confirmation, mark a calendar invite. The rule cuts the noise in the task system and clears small obligations before they accumulate. The catch is that two minutes is easy to misjudge; many users find that a 'two-minute' email expands into a fifteen-minute thread.
Is GTD compatible with deep work and time-blocking?+
Yes, it is complementary. GTD is the front-end (capture, decide, organize commitments) and time-blocking or deep work is the back-end (when and how the work actually happens). A GTD next-actions list can feed directly into a time-blocked calendar: the morning deep-work block pulls from the priority project list, and the afternoon shallow-work block pulls from the @computer or @errands contexts. Cal Newport, who popularized deep work, has explicitly described his own system as a hybrid of GTD capture with time-blocked execution.
Why do people abandon GTD after a few months?+
Because the weekly review is the keystone habit, and most people skip it. GTD without a weekly review collapses within 6 to 8 weeks because the inbox accumulates, the contexts go stale, and the projects list stops reflecting reality. Users then experience the system as broken, when actually only the maintenance step was missing. David Allen himself has said in interviews that if forced to choose one part of GTD to keep, he would keep the weekly review. The other steps support it; without it, they decay.
