Getting Things Done

01Introduction

Getting Things Done asks you to hand your whole mind to a list. The support for that is testimony, not trials.

02Core Idea

The central idea in David Allen's book is simple: your head is a bad place to keep things. A web developer who has practised the method for years, Jeremy Daly, sums it up in his review of the revised edition from twenty fifteen. Daly says the method builds what he calls an "external brain." That means a trusted system that holds everything you would otherwise keep worrying about.

The argument rests on a metaphor. Daly compares the brain to the RAM in a computer. It can hold only so much at once, and it is bad at priority. Remembering to buy milk takes as much effort as remembering a key point for a client presentation. Anything you are holding in your head but have not dealt with, Daly calls an open loop. In this account, open loops use up the attention you need for higher-level thinking. It's worth being clear about what kind of claim that is. It is an analogy, and a plausible one. In the reviews on file, it is not tied to any memory research.

The method itself works like a pipeline. You capture everything. You clarify what each item is. You organize it into lists, including a someday-maybe list and a reference file. You reflect, through daily and weekly reviews. Then you engage, meaning you actually do the work. On how often to review, Daly quotes the book directly. Allen's guidance is to review "often enough to feel like you don't have to think about them."

For bigger projects, Allen adds what he calls the natural planning model. You define the purpose, picture the outcome, brainstorm, organize, and then choose next actions. Allen notes that most meetings run this backwards, opening with someone asking who has a good idea. That is a sharp observation about workplaces. But it is an observation, not a finding.

03The Evidence

Here is what the evidence for this review contains: three sources. One is a long review by a self-described fan. One is a blog essay by a critic who used the system for years. The last is a forum thread from twenty twelve. None of them cites a study. None reports a measurement of stress, output, or time saved. Everything that follows is practitioner testimony, and it should be weighed as testimony.

The fan is Jeremy Daly. He first read the book in late two thousand seven, while running a web development firm that badly needed operational clarity. Daly writes that the method is "very practical and works well if you can commit to it." He also says it takes time and energy. That condition matters, because committing to it is doing most of the work in that sentence. Daly goes further and says the system can release creativity at a level you may never have thought possible. That is the strongest claim on file, and it rests on one reader's experience.

Allen's own framing points somewhere interesting. As Daly reports it, Allen says the method needs no new skills. It only puts the skills you already have to better use. Daly adds that much of it is common sense. That is honest, and it changes what proof would look like. A system built from common sense does not need a lab to be plausible. It would need one to show it beats the next system.

The critic matters on the evidence side too. Cal Newport adopted the system as a Dartmouth undergraduate in two thousand three and later broke with it. Even so, Newport calls GTD "devastatingly effective" for organizing shallow work, and adds that many will attest to it. So "many will attest" is the standard of evidence here, from friends and critics alike.

The forum thread shows how people use the system day to day. One commenter answers critics who say contexts are out of date. Having a phone in the boardroom, the commenter argues, does not mean you should be making calls there. Another commenter recalls a follower of an older put-everything-in-the-calendar method. That follower booked a solid hour with himself just to schedule calls with other people. These are useful warnings, but they are anecdotes about how people use systems. They do not test whether this system works.

One for the comments: have you ever kept a full capture system going past the first month? If you did, what made it stick? And if you stopped, what broke first?

04The Critiques

The most developed critique comes from Cal Newport. His complaint is specific. After a few years on the system, by which time he was at MIT for graduate school, he was good at full capture and regular review. But the system was not making him better at anything. Newport writes: "David Allen's universalism is seductive, but ultimately flawed." His point is that processing tasks efficiently cannot, on its own, produce work of lasting value. His phrase for it is cranking widgets.

The comments under Newport's essay did not all agree with him. One reader argues that the natural planning model is itself a method for deep thought. Another says the real engine of the system is what Allen calls areas of focus. Without a focused purpose, that reader says, GTD can feel like staffing a never-ending conveyor belt. The same reader still says nothing else has worked as well. So the argument is not about whether GTD organizes tasks. It is about whether organizing tasks is the same as doing good work.

The forum raises a harder practical question. One poster asks what happens to your top-priority tasks when you learn your sister has cancer. The whole scale changes. The poster later admits the example is extreme. Still, it points to a real gap. A system that files everything evenly says little about what to do when the priorities themselves shift. To be fair, Allen does describe higher-level reviews above the daily work, meant for exactly that kind of reckoning. Whether they hold up under that pressure is not something the file can tell us.

Then there is the overhead. One forum user says they would spend more time each day changing task statuses to waiting, delegated or actionable than they would save by tracking them. That user also makes a distinction worth keeping. The GTD in Allen's book is not the same as the GTD built into productivity apps. Some criticism of Allen is really criticism of the software that borrowed his labels.

To be fair to the book, its defenders in the thread make a precise point. GTD does not require contexts. Contexts are a tool you can use if you need them. And the book does not ban putting work on your calendar. It only advises keeping the calendar for things that really are tied to a time or a date. Several of the critiques are aimed at a stricter system than the one Allen actually wrote.

05Who It's For

Jeremy Daly's situation is the clearest match in the file: someone running a business, buried in obligations, with no operational clarity. Cal Newport as an undergraduate fits as well. He says Allen's ideas resonated when his obligations started to overwhelm him. The book is built for a reader whose problem is volume.

If your problem is not too many tasks but the wrong ones, Newport's experience is the warning. He mastered the system and found it did not make his work better. And if what you want is measured evidence, stress levels and output tracked rather than reported, this book does not offer it.

06Verdict

Clarity of method and practical tooling score high. The evidence scores lowest, because there is none beyond testimony. The apps that copied the method, and the book's fit outside task-heavy jobs, both score low.

Our verdict: Getting Things Done is well built as a workflow and thinly supported as a claim. Its fans and its critics agree it handles a flood of shallow work. None of them measures what it does for stress or output. And its sharpest critic found that mastering it did not make his work better. It is strong on the inbox and unproven on the outcome. A reader whose real problem is choosing what matters will find the lists tidy and that question left open.

Getting Things Done asked you to hand your mind to a list. The list holds up. The evidence that it frees your mind is still testimony.

That is the evidence check on Getting Things Done. If you found this scrutiny useful, like the video, and subscribe to Gem Harvester for more reviews that separate the story from the study.