Getting Things Done: a complete guide

What is Getting Things Done?

Getting Things Done, usually shortened to GTD, is a personal productivity system developed by consultant David Allen and published in a book of the same name in 2001. The central argument is simple: your brain is terrible at remembering things and shouldn't have to. Every task, idea, commitment, and piece of information you're holding in your head is consuming cognitive resources that could be used for actual thinking. The solution is to get everything out of your head and into a trusted external system, then engage with that system in a structured way.

GTD peaked in mainstream popularity around 2007 according to search trends, but it has endured in a way most productivity frameworks haven't. The core insight about cognitive load and external systems has aged well, and the five-step workflow remains one of the most coherent frameworks for personal task management ever published.

Allen updated the book in 2015 to reflect the digital age, and while some specifics have dated (context lists made more sense when you couldn't carry the internet in your pocket), the underlying principles remain sound.

The five steps

GTD organises everything into a five-step workflow: Capture, Clarify, Organise, Reflect, and Engage.

1. Capture

The first step is to get everything out of your head. Ideas, tasks, commitments, things you've noticed need doing, things people have asked you to do, things you've told yourself you'll get to eventually. All of it goes into an inbox, which in GTD is simply any collection point that feeds into the system.

Allen's original vision included physical in-trays on your desk alongside digital capture. In practice most people now capture primarily digitally, using a notes app, a voice recorder, or a web clipper for things found while browsing.

The capture habit is the foundation of everything else. If you don't trust that you've captured everything, you'll keep maintaining mental backup systems, which is exactly the cognitive overhead GTD is designed to eliminate. Capture needs to be consistent and frictionless. If it's too much effort, things don't get captured, and things that don't get captured stay in your head as open loops.

2. Clarify

Once things are in your inbox, you process them. For each item, you work through a series of decisions:

Is it actionable? If not, you have three options: throw it away if it's useless, file it in a reference system if it might be useful later, or put it on a someday/maybe list if it's a vague future idea you don't want to lose but aren't ready to commit to.

If it is actionable: what's the next physical action? This is one of Allen's most useful ideas. Not "sort out the project," but "email Sarah to ask for the budget figures." The more concrete and physical the next action, the lower the activation energy required to actually do it.

Will it take less than two minutes? If yes, do it immediately. The overhead of recording, organising, and later retrieving a two-minute task costs more than just doing it. This is Allen's two-minute rule, and it's one of the most practically useful ideas in the whole system.

Should someone else do it? If yes, delegate it. Record what you've delegated and to whom so you can follow up.

If none of the above: it goes on your Next Actions list or your Calendar, depending on whether it's time-dependent.

3. Organise

GTD's organisational structure has several components:

Next Actions: your working task list. These are concrete, physical next steps that you can do as soon as you have the time, energy, and resources.

Projects: any outcome that requires more than one action step. Allen's definition of "project" is broader than most people's instinct. Writing a report is a project. Planning a dinner is a project. Anything requiring multiple steps belongs here, and every project should have at least one next action associated with it in the Next Actions list.

Waiting For: things you've delegated or are waiting on from someone else. If you've asked a colleague for a document, that goes here so you don't forget to follow up.

Calendar: time-specific actions (things that must happen on a particular day) and day-specific information (things you want to be reminded of on a particular date, even if they don't have to happen at a specific time).

Someday/Maybe: things you might want to do someday but aren't committing to now. Review this list periodically to see if anything has become relevant.

Reference: information you want to keep but that doesn't require action. This is where GTD connects to filing and search. Allen recommended a simple A-Z filing system for reference material. Most people now rely on search to find reference material rather than maintaining an elaborate filing structure.

Context lists (optional): Allen also recommended organising your Next Actions by context, @computer, @phone, @errands, @home, @office. The idea was that when you're at your computer you only want to see tasks that require a computer, not ones you can only do while running errands. This made a lot of sense in 2001 when many tasks actually required you to be in a specific place with specific tools. It's less relevant now that most people can do most things from anywhere, and many GTD users skip context lists or use a much simpler version.

4. Reflect

The review step is what keeps the system alive. Allen calls the weekly review the "critical success factor" of GTD. At least once a week you go through every list, clear out what's done, update what's changed, and make sure every active project has a next action.

The weekly review is also where Allen's "horizons of focus" come in. His framework has six altitudes: runway (current actions), 10,000 feet (current projects), 20,000 feet (areas of responsibility), 30,000 feet (one to two year goals), 40,000 feet (three to five year vision), and 50,000 feet (life purpose). Most weekly reviews only reach the first two or three levels. The higher altitudes are for longer-form reflection, monthly or annually.

The weekly review is also where GTD most commonly breaks down. It requires 60 to 90 minutes of focused administrative work, which competes directly with every other demand on your time. Miss it once and guilt accumulates. Miss it twice and the whole system starts to decay, because the lists stop reflecting reality and you stop trusting them.

5. Engage

This is the step where you actually do things, which is most of your day. When you're ready to work, you choose what to do next based on four criteria: context (what can you do where you are?), time available (how long do you have?), energy level (what are you capable of right now?), and priority (given the above, what matters most?).

The voltage model from ADHD research maps nicely onto Allen's energy criterion: high-voltage tasks need to be done when you have the most energy, which for most people means early in the day.

What GTD gets right

The open loops insight. The idea that every uncaptured commitment occupies cognitive resources is supported by neuroscience (the Zeigarnik effect) and Baumeister's research showing that making a plan to complete a task, not completing it, is enough to release the mental burden. This is probably the most valuable single idea in the book.

Next physical actions. Forcing yourself to define the next concrete step removes a surprisingly large amount of procrastination. Vague tasks are easy to avoid. "Email Sarah" is something you can do right now.

The two-minute rule. Simple, practical, and effective. If it takes less than two minutes, do it immediately rather than adding the overhead of recording and later retrieving it.

The project definition. Allen's insistence that anything requiring more than one action is a "project" catches a lot of tasks that people miscategorise as simple to-dos and then wonder why they never seem to finish them.

Separating capture from processing. Getting things out of your head first, then deciding what to do with them later, reduces the cognitive overhead of each individual capture. You don't have to decide anything when you capture, which makes capturing easier.

Where GTD falls short

The setup cost is high. Allen recommends an initial "mind sweep" to capture every open loop in your life, which can take hours. Setting up the full system, including reference files, context lists, and project lists, takes serious time and effort. Many people start GTD, hit the setup process, and abandon it before they've experienced any of the benefits.

The weekly review is hard to sustain. As discussed, the review is load-bearing but demanding. Without it the system rots, and keeping it current requires the kind of sustained organisational effort that many people struggle to maintain.

Context lists have aged poorly. The idea of filtering tasks by @computer or @phone made sense when being at your computer was a genuine constraint. In an era of smartphones and remote work, most people can do most tasks from anywhere. Context lists add complexity without proportional benefit for the majority of users.

GTD doesn't help with deep work. Cal Newport, who has written extensively about focus and digital distraction, has noted that GTD is excellent at clearing the decks but doesn't address how to actually do creative, cognitively demanding work. It optimises for throughput across many small tasks; it has less to say about blocking time for thinking.

It can become busywork. The system is at risk of becoming an end in itself. Maintaining your lists, processing your inbox, doing your weekly review, all of this can consume significant time without producing any actual output. The goal is to get important things done, not to maintain an impeccable system.

Lighter versions of GTD

Given the setup cost and maintenance burden, many people use a simplified version of GTD that keeps the most valuable ideas and drops the rest. Common simplifications:

Drop the context lists unless they're actually useful for your specific situation.

Replace the elaborate filing system with a simple search-based approach. Dump everything into one place and use semantic search to find it rather than maintaining an A-Z folder structure.

Do a shorter, lighter weekly review (15 to 20 minutes) rather than the full 60 to 90 minute version. Focus on projects and next actions; leave the higher-horizon reflection for monthly or quarterly.

Use the capture, clarify, and two-minute rule as your daily practice, and let the more elaborate structures be optional.

For a more structured approach to this, see our guide to GTD Lite.

GTD and other systems

PARA method: PARA organises your reference material and projects by actionability, which complements GTD's workflow naturally. Many people use GTD for the process (capture, clarify, review) and PARA for the filing (where does this information live?).

Building a Second Brain: Tiago Forte's system is partly inspired by GTD but focuses more on knowledge management and creative output. Where GTD is task-centric, BASB is information-centric. The two can work together.

Pomodoro Technique: GTD tells you what to do next. Pomodoro helps you actually start it and stay focused. The two are natural companions.

Time blocking: One criticism of GTD is that it leaves scheduling to the last minute, relying on your energy and context in the moment to decide what to work on. Time blocking adds structure to when you'll do things, which some people find helpful and others find overly rigid.

Zettelkasten: GTD's reference system is about storing information for future retrieval. Zettelkasten goes further, building a network of linked notes that generates new ideas. For knowledge workers and researchers, Zettelkasten handles the territory that GTD's reference system was never designed for.

Getting started

The quickest way to get real benefit from GTD without committing to the full system:

Start capturing everything into a single inbox. One place, consistently used. Stop trying to hold things in your head.

Process your inbox daily. For each item: is it actionable? If yes, what's the next concrete step? If it takes less than two minutes, do it now. If not, add it to your task list.

Keep a project list. Anything that requires more than one action is a project. Every project should have a visible next action so it doesn't stall.

Do a light weekly review. Clear out completed items, check your project list, make sure everything that's active has a next step defined.

Add the more elaborate structures (context lists, someday/maybe, higher horizons) later, if you find you need them.

The system doesn't need to be implemented all at once. The capture habit alone, consistently applied, will make a noticeable difference.

Frequently asked questions

Is GTD still relevant?

Yes, for the core ideas. The insight about open loops, the importance of external capture, the two-minute rule, the distinction between projects and next actions, these have aged well and are supported by research that didn't exist when Allen wrote the book. Some specifics, particularly context lists and the elaborate physical filing system, are less relevant in 2025, but the framework adapts.

How long does it take to set up GTD?

The full setup, including an initial mind sweep and processing everything, can take a full day or weekend. Most people don't need to do it that thoroughly. A more practical approach is to start with your current tasks and commitments, implement the capture and clarify habits from day one, and build out the rest of the system gradually.

What's the best app for GTD?

Allen's system is tool-agnostic and works with pen and paper, though most people use a combination of a task manager (for actions and projects) and a notes or file system (for reference material). The best app is the one you'll actually use consistently. Avoid spending too much time evaluating tools, since that's a common form of productive procrastination.

What's the difference between GTD and PARA?

GTD is a workflow: how you capture, clarify, organise, review, and do. PARA is an organisational structure: where you put information based on its actionability. GTD tells you what to do with something. PARA tells you where to file it. Many people use both together.

Do I have to do the weekly review?

In theory, no. In practice, the system degrades without it, because lists go stale, completed projects don't get archived, and things fall through the cracks. If the full weekly review is too demanding, a lighter 15-minute version that just checks your project list and next actions is far better than nothing.

Is GTD good for creative work?

GTD is strong on task management and weak on creative work. It will help you clear the administrative overhead that competes with creative time, which is valuable. But it doesn't address how to structure deep work, protect creative time from interruption, or manage the non-linear nature of creative projects. For that, pair GTD with time blocking or Newport's deep work principles.

Can I use GTD if I have ADHD?

The core ideas of GTD (capture everything, external systems, clear next actions) are particularly valuable for ADHD brains. The challenge is the setup cost and weekly review maintenance, which both require sustained executive function. A simplified version of GTD, or pairing it with a tool that handles organisation automatically, tends to work better than implementing the full system.

Getting Things Done was created by David Allen and published by Penguin Books. This guide is based on the revised 2015 edition.