Getting Things Done (GTD): A Complete Implementation Guide

David Allen's Getting Things Done (GTD) is the most influential personal productivity system of the last quarter-century, and for good reason: it solves a real problem. The human brain, Allen argues, is for having ideas, not for holding them. Trying to remember everything you have to do consumes mental bandwidth and produces a constant low-grade anxiety that there is something you have forgotten. GTD solves this by moving every commitment out of your head and into a trusted external system, then processing that system to empty on a regular cadence. This is a complete implementation guide for people who want to actually run it, not just admire it.

The core principle: capture everything

The first rule of GTD is that nothing stays in your head. Every commitment, idea, obligation, and "someday maybe" gets captured into an inbox — physical or digital — the moment it occurs to you. The brain is a terrible filing system because it reminds you of things at the wrong time (3 AM) and forgets them at the wrong time (in the meeting where it mattered). The capture habit is the foundation; without it, the rest of the system has nothing to work on.

Most people need one or two capture points, not seven. A single note app on your phone plus a physical inbox on your desk covers 95% of life. The trap is having too many inboxes — email, Slack, three note apps, a paper notebook, sticky notes — because each one becomes a place things get lost. Consolidate.

The five steps of GTD

Allen's workflow has five steps, and they are sequential. Most people who think they "do GTT" actually do only the first two and wonder why the system feels heavy.

1. Capture

Collect everything that has your attention into inboxes. Do not sort, do not decide — just collect. The goal is an empty head and a full inbox.

2. Clarify

Process the inbox to zero. For each item, ask: is this actionable? If no, it is trash, a reference item (file it), or a "someday/maybe" item (park it). If yes, what is the next physical action? If the task takes less than two minutes, do it now. If it has multiple steps, it is a project; define the next action and the desired outcome. This step is where most people stall, because it requires a decision for every item.

3. Organize

Put each clarified item in the right place. The canonical GTD lists are:

• Projects — any outcome requiring more than one step.
• Next Actions — the single next physical thing to do, organized by context (@home, @computer, @calls).
• Waiting For — things delegated to others, with the date you delegated them.
• Someday/Maybe — things you want to keep alive but are not committing to now.
• Reference — information with no action but you may need later.
• Calendar — only time-specific commitments and hard landscape. Never put a to-do on the calendar; that dilutes its reliability.

4. Reflect

Review the system on two cadences. A weekly review is the heart of GTD — without it, the lists rot and trust in the system collapses. The weekly review is when you process every inbox to zero, review every project for its next action, update the Waiting For list, scan Someday/Maybe, and look at your calendar for the coming weeks. Most GTD failures are weekly-review failures. A daily review, lighter, is a glance at the calendar and the Next Actions list for the day.

5. Engage

Do the work, choosing from your trusted lists rather than from panic. The choice of what to do at any moment considers four things: context (where are you, what tools do you have), time available, energy available, and priority. This is where GTD hands off to other methods — once you have a trusted list, you can apply prioritization or time blocking to decide which item to do when.

The two-minute rule

If an action takes less than two minutes, do it the moment you clarify it, rather than tracking it. The rule is not about efficiency — doing 30 two-minute tasks one at a time takes the same time as batching them. It is about trust: a system full of trivial tracked items feels heavy and stops being used. The two-minute rule keeps the lists meaningful, so when you look at them, you see only things that genuinely needed tracking.

The weekly review, in detail

This is the single most important habit in GTD, and the one most people skip. Block 60 to 90 minutes, weekly, at the same time. Friday afternoon works well for many people. The sequence:

1. Process every inbox to zero — email, physical, capture app, voicemail.
2. Review each active project: does it still have a defined next action? If not, define one.
3. Scan the Waiting For list: are any items overdue? Send a follow-up if so.
4. Review past and future calendar for stray commitments and capture anything that occurs to you.
5. Review Someday/Maybe: promote anything you now want to activate; delete anything stale.
6. Get your head empty: what is on your mind that is not in the system? Capture it.

The weekly review is what makes the system trustworthy. When you trust it, you stop trying to remember things, which frees the mental bandwidth that makes the actual work better. Use a recurring calendar block and a reminder to protect it.

Common implementation mistakes

• Using the inbox as a to-do list. The inbox is for capture; it must be processed to zero regularly. If it grows unbounded, it becomes a graveyard.
• Vague next actions. "Think about the proposal" is not a next action; "draft the three objections section" is. If you cannot picture doing it, it is not a next action.
• Skipping the weekly review. Within three weeks, the system drifts and trust collapses. Protect the review like a meeting with your most important client.
• Too many lists. Five well-maintained lists beat twenty abandoned ones. Start small and add lists only when you feel a real pain point.
• Putting to-dos on the calendar. The calendar is for time-specific commitments only. If you put "write report" on Tuesday, and you do not do it Tuesday, the calendar becomes a source of guilt rather than a source of truth.

The bottom line

GTD is not about doing more; it is about thinking less about doing. The payoff is the mental space that opens when you stop trying to remember everything. The system is simple to describe and hard to maintain, and the people who get the most from it are the ones who treat the weekly review as non-negotiable. Start with capture and the two-minute rule, add the lists, and protect the review. Within a month, the constant background anxiety of "what am I forgetting" will fade, and you will have the bandwidth to do the actual work better.