Getting Things Done: What Holds Up and What Doesn't

David Allen's system has useful parts, but the evidence base is thinner than the popularity suggests.

Getting Things Done, published in 2001, is probably the most influential personal productivity book of the past quarter century. David Allen’s system has spawned an industry of apps, coaches, and consultations. The core framework, capture everything, clarify what each item means, organize by context, review regularly, and engage with confidence, has a certain engineering elegance to it [5]. The question is how much of it is supported by evidence and how much is supported by enthusiasm.

What the system is

GTD is a five-step workflow for managing tasks and projects [5]:

  1. Capture: collect every open loop (task, idea, commitment) into a trusted inbox.
  2. Clarify: process each item by deciding what it is and what the next physical action is.
  3. Organize: sort items into lists by context (at computer, at phone, errands) and project.
  4. Reflect: conduct a weekly review of all inboxes, projects, and next actions.
  5. Engage: choose what to work on based on context, time available, energy, and priority.

The system’s central claim is that the human mind is for having ideas, not holding them. By externalizing every commitment into a reliable external system, you free cognitive resources for the work itself rather than for remembering what work exists. Allen draws an analogy to RAM: open loops consume working memory, and the more of them you hold internally, the less capacity you have for the work in front of you. The solution is to move them to an external system you trust, so your brain can stop tracking them.

The appeal is intuitive, and the system has attracted a dedicated following. But the gap between a system that sounds right and a system that has been tested is worth examining.

What the research supports

The capture principle

The strongest scientific support for GTD comes from research on unfulfilled goals and cognitive load. Masicampo and Baumeister demonstrated across two experiments that making a specific plan for an unfulfilled goal eliminates the intrusive thoughts that goal generates, even before you execute the plan [2]. Participants who wrote down a concrete plan for an unfinished task showed no more cognitive interference from that task than participants who had already completed it. This directly supports Allen’s claim that capturing and clarifying tasks reduces mental overhead: the act of deciding what you will do and writing it down is sufficient to free the working memory that the unresolved commitment was consuming.

Heylighen and Vidal mapped GTD’s principles to established cognitive science and found that the system aligns well with research on external memory, attention management, and stress reduction [1]. The theoretical fit is strong: externalizing commitments to a reliable system should reduce the cognitive load of maintaining them internally. Their analysis identified specific cognitive mechanisms that each GTD step addresses, including the Zeigarnik effect (the tendency for incomplete tasks to occupy working memory), prospective memory failures (forgetting to do things you intended to do), and the anxiety that comes from a sense of uncontrolled obligations.

The two-minute rule

GTD’s two-minute rule (do it now if it takes less than two minutes) functions as a form of implementation intention: a specific if-then plan that removes the decision about when to act [4]. The research on implementation intentions consistently shows that they increase follow-through by eliminating the deliberation about when and how to begin. The two-minute rule converts a class of tasks from “things I need to decide when to do” into “things I do now,” and for trivially short tasks, this is a good rule of thumb. The overhead of capturing, clarifying, organizing, and reviewing a two-minute task exceeds the cost of simply completing it.

Next-action thinking

Defining the next physical action for each project or task is another form of implementation intention. Rather than keeping a vague item (“taxes”) on a list, GTD requires you to specify the concrete next step (“download W-2 from employer portal”). This specificity is well-supported by goal-pursuit research [4]. Gollwitzer’s review found that implementation intentions, specific plans of the form “when situation X arises, I will perform response Y,” roughly doubled the rate of goal achievement across a range of domains. GTD applies this principle systematically to every item in the system.

The practical effect is that the list becomes a list of concrete, actionable items rather than a list of vague reminders. “Call doctor” is more actionable than “health stuff.” “Draft the first three paragraphs of the proposal” is more actionable than “work on proposal.” The specificity reduces the decision cost at the moment of engagement, which is where many people stall.

What the research does not support

The full system

There are no randomized controlled trials comparing full GTD implementation against other productivity systems or a control condition. The evidence for GTD as a complete system is theoretical and anecdotal. Heylighen and Vidal’s analysis is a theoretical mapping, not an empirical test [1].

This does not mean the system doesn’t work. It means we do not know whether the full five-step implementation outperforms simpler alternatives that use the same core principles. A person who captures tasks, defines next actions, and reviews weekly may be doing 80 percent of the productive work of GTD at 20 percent of the system maintenance cost. The marginal value of the remaining components, context-based organization, elaborate project lists, the full weekly review process, is unknown.

Context-based organization

GTD’s context lists (sorting tasks by where you can do them: at computer, at phone, at office) were designed for a world where these contexts were distinct. In a world where most knowledge work happens on a single device, the context distinction has largely collapsed. A knowledge worker’s “at computer” list is, functionally, their entire list. There is no research suggesting that context-based organization outperforms simple priority-based organization, and the overhead of maintaining multiple context lists may exceed the benefit they provide.

Some GTD practitioners have adapted the context concept to refer to energy level or attention type rather than physical location: “deep focus” tasks versus “low energy” tasks. This adaptation has intuitive appeal but no more empirical support than the original.

The weekly review

The weekly review is where GTD’s ambition meets human reality. Allen describes it as the critical habit that makes the entire system work, and most GTD users describe it as the habit they most struggle to maintain. The review involves processing all inboxes to zero, reviewing all active projects, updating all next-action lists, and reviewing upcoming calendar items. It takes 30 to 90 minutes and requires the kind of sustained, non-urgent effort that is precisely the type of task most people postpone.

There is no research on the optimal frequency or format for a productivity review. What the time management literature does suggest is that simpler systems tend to have higher long-term adherence [3]. Claessens and colleagues found that time management behaviors were positively associated with performance and satisfaction, but the association was driven by goal-setting and planning rather than by any specific organizational system. The implication is that the habit of reviewing and planning matters; the specific format may not.

The failure mode of the weekly review is catastrophic to the system. When the review lapses, the lists become stale. When the lists are stale, they cease to be trustworthy. When they cease to be trustworthy, the user stops consulting them. And when the user stops consulting them, the system is functionally abandoned, even though the lists still exist. This cascading failure is the most common way GTD practitioners leave the system.

Practical considerations

The core insight of GTD, that externalizing commitments and defining next actions reduces cognitive load, is well-supported and worth adopting regardless of whether you implement the full system.

The two-minute rule is practical and effective. Use it.

The weekly review is where most people fail. If you adopt GTD, treat the review as the single most important habit to protect, because everything else depends on it. If you cannot maintain a weekly review, consider whether a simpler system would serve you better. A daily five-minute scan of your task list, while less thorough than a full GTD review, may be more sustainable and therefore more useful over time.

The full GTD system is most valuable for people managing many projects across multiple domains: a senior manager, a freelancer with many clients, an executive with complex responsibilities. For someone with a relatively simple task load, a basic to-do list with next-action thinking may provide most of the benefit at a fraction of the maintenance cost. The overhead of the full system is not trivial, and a system whose maintenance costs exceed its benefits is not productive, regardless of how well-designed its components are.

The best productivity system is the one you actually use. GTD’s theoretical foundation is sound, but a system that lives in a neglected app is worse than a sticky note you actually look at.

If difficulty concentrating is new, persistent, or significantly affecting your life, it’s worth speaking with a doctor. Changes in focus can sometimes reflect sleep problems, mood disorders, or health conditions that are worth addressing directly. This site covers technique, not diagnosis.

Frequently asked questions

Does GTD actually work?

Parts of it are well-supported by cognitive science: externalizing tasks reduces mental load, and processing decisions at capture time (rather than repeatedly) is efficient. The full system as a whole has very little direct research. Most evidence is from user surveys and self-report, not controlled studies.

What is the two-minute rule in GTD?

If a task takes less than two minutes, do it immediately rather than capturing it. The logic is that the overhead of tracking and scheduling a tiny task exceeds the cost of just completing it. This is one of the most practically useful parts of the system.

Why do people quit GTD?

The weekly review, where you process all inboxes and review all projects and next actions, is the most common failure point. It takes 30 to 90 minutes and requires discipline to maintain. When the review lapses, the system loses its reliability, and trust in the system collapses.

Is GTD worth learning?

The core principles (capture everything, clarify what each item means, decide the next action) are worth adopting even if you never implement the full system. The overhead of maintaining all the lists and contexts may not be justified unless your task load is genuinely complex.

Sources and further reading

  1. Heylighen & Vidal -- Getting things done: The science behind stress-free productivity

    Long Range Planning, 2008. Theoretical analysis mapping GTD to cognitive science.

  2. Masicampo & Baumeister -- Consider it done: Plan making can eliminate the cognitive effects of unfulfilled goals

    Journal of Personality and Social Psychology, 2011. Two experiments, N=103.

  3. Claessens et al. -- Do time management behaviors relate to performance? A meta-analysis

    Journal of Managerial Psychology, 2004. Meta-analysis of 32 studies.

  4. Gollwitzer -- Implementation intentions: Strong effects of simple plans

    American Psychologist, 1999. Review of implementation intention research.

  5. Allen -- Getting Things Done: The Art of Stress-Free Productivity

    Penguin, 2001 (revised 2015). The original book describing the GTD system.

Sources checked March 25, 2026. This is an editorial summary, not a systematic review or individual advice.

Get new articles by email

New articles from Desk Hours, sent to your inbox. Unsubscribe at any time.

Related articles