Getting Things Done (GTD)

Overview

Getting Things Done (GTD) is a personal productivity method introduced by David Allen in his 2001 book of the same name. Its central premise is that the mind is better suited to thinking than to remembering. When open loops—unfinished tasks, vague commitments, half-formed ideas—are held in memory, they consume attention and create low-grade stress. GTD addresses this by moving every commitment into a trusted external system, then processing that system on a regular schedule. The method is organized around five practices: capture, clarify, organize, reflect, and engage. Capture means collecting anything that has your attention into an inbox. Clarify means deciding what each item is and what action it requires. Organize means placing the result in the right list. Reflect means reviewing those lists regularly, especially in a weekly review. Engage means choosing what to do next based on context, time, energy, and priority. GTD is deliberately tool-agnostic: paper notebooks, text files, task managers, or a combination can all work. What matters is that the system is complete, current, and trusted, so you can stop holding items in your head and start acting on them deliberately.

How it works

GTD works by separating the act of capturing from the act of deciding. Every incoming item—email, voicemail, meeting note, stray thought—goes into an inbox rather than directly onto a to-do list. Later, you process the inbox item by item. For each item you ask: what is it, and is it actionable? If it is not actionable, it is either trash, something to file as reference, or something to place on a someday/maybe list. If it is actionable, you decide the very next physical action. If that action takes under two minutes, you do it immediately. If it belongs to a larger outcome, it goes onto a project list, and its next action goes onto a next-actions list. Actions are grouped by context—such as calls, errands, computer, or at-home—so you can match tasks to your current situation. Items you are waiting on from others go onto a waiting-for list, and items with a fixed date go onto a calendar. The weekly review ties the system together: you empty inboxes, update project lists, and confirm that every active commitment has a defined next action.

Step-by-step

1. Set up your collection points. Choose one physical inbox (a tray or notebook) and one digital inbox (an email folder or capture app). Keep the number small so nothing is missed.

2. Capture everything. For one or two days, write down every task, commitment, idea, and loose end that has your attention. Do not organize yet; just collect.

3. Process the inbox. Take items one at a time. If an item is not actionable, discard it, file it as reference, or move it to a someday/maybe list. If it is actionable, define the next physical action.

4. Apply the two-minute rule. If the next action takes two minutes or less, do it now. Otherwise, record it.

5. Organize the results. Put single actions on context lists, multi-step outcomes on a projects list, delegated items on a waiting-for list, and date-specific items on the calendar.

6. Schedule the weekly review. Block 60 to 90 minutes at the same time each week. Use it to empty inboxes, review projects, and update lists.

7. Engage. During the day, consult your context lists and calendar, and pick the action that fits your available time, energy, and priority.

When to use it

GTD is most useful when the volume and variety of your commitments exceed what you can comfortably hold in memory. Typical situations include managing multiple projects with different stakeholders, handling a high flow of email and messages, running a small business or freelance practice, or coordinating work and personal responsibilities at once. It also suits people who feel that tasks slip through the cracks or who re-read the same email several times without deciding what to do about it. GTD is less necessary if your work is highly linear, with few incoming requests and a stable routine. It can also be overkill for a single short project, where a simple checklist is faster to build and maintain. The method assumes you are willing to spend a few hours setting up lists and contexts, and roughly an hour a week maintaining them. If that maintenance feels heavier than the value it returns, a lighter capture-and-review habit may be a better fit.

Common pitfalls

The most common failure is capturing incompletely. If some commitments stay only in your head, the system cannot be trusted, and you will keep mentally rehearsing them. A second pitfall is confusing projects with actions. A projects list should contain outcomes such as "finalize quarterly report," while next-actions lists contain concrete steps such as "email finance for figures." Mixing the two makes lists feel overwhelming and hard to act on. A third pitfall is skipping the weekly review. Without it, lists go stale, inboxes refill, and trust in the system erodes. A fourth is over-engineering: building elaborate contexts, tags, and sub-projects before the basic habit exists. Start with a few lists and add structure only when a real need appears. A fifth is treating the calendar as a to-do list. The calendar should hold only items tied to a specific date or time; everything else belongs on a context list. Finally, some people process inboxes constantly instead of in scheduled batches, which fragments attention without improving control.

Combining with other methods

GTD pairs well with several complementary approaches. With time blocking, you use GTD to decide what needs doing, then place those actions into specific calendar blocks; GTD supplies the inventory, time blocking supplies the schedule. With the Eisenhower matrix, you can sort next actions by urgency and importance when your lists are long and you need a quick prioritization pass. With Kanban, a projects list can be visualized as columns such as backlog, next action, waiting, and done, which helps teams see status at a glance. With Pomodoro, you select one next action from a context list and work it in focused intervals. With OKRs or similar goal-setting frameworks, the weekly review becomes a natural checkpoint to confirm that projects still support larger objectives. The key is to keep one trusted system of record. If you adopt a second method, decide which tool holds the master lists, and let the other method shape how you choose or schedule work rather than where it is stored.

Frequently asked questions

How long does it take to set up GTD? Most people can build a working system in a few hours: one capture session, one inbox processing pass, and a first weekly review. The habit of capturing consistently takes longer, often two to four weeks, before it feels automatic.

Do I need special software? No. GTD is tool-agnostic. A notebook and a calendar can support the full method. Digital task managers add search, reminders, and sync, but they are optional. Choose the tool you will actually open every day.

What if I fall behind on the weekly review? Do a shortened version rather than skipping it. Empty the inboxes, scan the projects list, and confirm that each active project has a next action. A 30-minute review restores enough trust to keep the system usable until you can do a full one.