In 2001, David Allen published a book that changed how an entire generation of knowledge workers thought about productivity. Getting Things Done — GTD for short — introduced a comprehensive framework for capturing, clarifying, and organizing every commitment, project, and task in your life. It became one of the best-selling business books of all time. Allen's consulting practice grew into a global training business. Entire software ecosystems were built to support the GTD workflow.
And yet, the vast majority of people who try GTD abandon it within months. Not because the ideas are bad — many of them are genuinely excellent — but because the system as a whole demands more than most people can sustainably give it. This is not a failure of discipline. It is a failure of fit. GTD was designed for a specific type of person operating in a specific type of work environment, and it was mistakenly marketed as a universal solution.
This article examines what GTD got right, where it breaks down, and what research on decision-making and cognitive load tells us about why constrained, minimal systems often outperform comprehensive ones for most people.
What GTD Actually Is
GTD is built around five core stages: capture everything that has your attention, clarify what each item means and what to do about it, organize the results into appropriate lists and categories, reflect through regular reviews, and engage with your tasks from a place of clarity rather than anxiety.
The canonical GTD setup involves multiple lists organized by context — "@computer," "@phone," "@home," "@errands," "@waiting" — alongside a project list, a someday/maybe list, a reference filing system, a calendar for hard landscape items (things that must happen on a specific date), and a weekly review ritual that holds the entire system together.
The philosophical promise is that if you capture everything that has your attention into a trusted external system and maintain that system rigorously, your mind can relax. Allen calls this the "mind like water" state: calm, clear, and ready to respond appropriately to whatever arrives. It is an appealing vision, and for people who achieve it, it genuinely works.
GTD's Genuine Contributions
Before examining the failure modes, it is worth acknowledging what GTD got genuinely right. These ideas have become so widely adopted that we now treat them as obvious, but they were clarifying innovations when Allen introduced them.
Ubiquitous capture. The idea that you should have a reliable way to capture anything that has your attention — wherever you are, whatever you're doing — was genuinely novel in 2001. Before smartphones, Allen recommended carrying a notepad everywhere. The insight that open loops in your mind create background anxiety, and that externalizing them provides relief, is supported by subsequent psychological research on the Zeigarnik effect and cognitive load.
Next actions over vague projects. Allen's insistence that every project must have a defined "next action" — a specific, physical, visible task — is one of the most practical ideas in productivity literature. "Plan vacation" is not a next action. "Open browser and search for flights to Lisbon" is. The distinction forces you to think through what a project actually requires rather than leaving it as an intimidating abstraction.
The two-minute rule. If something takes less than two minutes to do, do it now rather than organizing it into a system. This simple heuristic prevents the common trap of spending more time managing a task than it would take to complete it.
Where GTD Breaks Down
Despite its contributions, GTD has consistent, predictable failure points that affect the majority of practitioners. These are not edge cases. They are structural problems with the system itself.
1. The Weekly Review Is the First Thing to Go
The weekly review is not an optional component of GTD. It is the keystone. Without it, context lists go stale, projects lose their next actions, the someday/maybe list becomes a permanent holding pen, and the entire system slowly loses the trustworthiness that is its core value proposition. Allen describes it as "the master key to GTD."
And yet, surveys of GTD practitioners consistently show the weekly review is the first practice abandoned, typically within a few weeks of starting the system. The review takes 30 minutes to two hours when done properly. It requires processing every inbox, reviewing every project list, updating every context list, and thinking carefully about upcoming commitments. For people with busy lives, that block of time rarely materializes, and when it doesn't, the system begins to decay immediately.
A productivity system with a critical dependency on a two-hour weekly ritual is not a system that works when life gets busy — precisely the conditions under which you most need a reliable system.
2. Context Lists Become Outdated and Irrelevant
GTD's context-based organization made intuitive sense in 2001. Your "@computer" list contained tasks that required a computer. Your "@phone" list contained calls to make. Your "@home" list was for things you could only do at home. The geographic and technological separation of work and home created natural contexts that shaped what was possible at any given moment.
3. Capture Everything Means an Infinite Backlog
4. System Maintenance Becomes a Second Job
5. GTD Assumes All Tasks Are Equal
The GTD Personality Type
Research on Decision Fatigue and Option Overload
The Anti-GTD: Constrained Systems and the Daily Reset
Not a Criticism of GTD Practitioners
Choosing the Right System for You
- Do you enjoy organizing and systematizing for its own sake, or do you want to spend as little time managing tasks as possible?
- Do you manage a large number of simultaneous projects with complex interdependencies, or do your days involve a smaller set of focused priorities?
- Can you reliably protect a 30–90 minute weekly review, or does your schedule resist that kind of recurring commitment?
- When you've tried GTD before, did you abandon it? If so, how quickly?
- Do you find comprehensive lists energizing or overwhelming?