David Allen spent two decades as a management consultant watching capable people drown in commitments before writing the book that named the problem. Getting Things Done is not a motivational text and makes no attempt to be one. It is a specification for a personal workflow — closer to an operations manual than to self-help — and its influence on every productivity app built since is difficult to overstate.
The core argument
Allen’s diagnosis is psychological rather than logistical. Stress does not come from having too much to do; it comes from unkept agreements with yourself. Every unresolved commitment you are storing mentally, from a major project to remembering to buy batteries, occupies attention at the same level of urgency, because the mind is bad at holding things and worse at prioritising them. His prescription follows directly: your mind is for having ideas, not for holding them. Move all of it into an external system, and the anxiety of half-remembered obligation drains away.
The system has one non-obvious demand. It is not enough to write things down — a list of vague nouns like “Mum” or “insurance” produces more dread, not less. Each item must be processed until you have decided the desired outcome and the very next physical, visible action required to move it. That translation step, from ambiguous commitment to concrete action, is the actual engine of the method, and the part most people skip.
The system also has to be genuinely trusted. Allen is insistent that a partially maintained system is worse than none, because the mind reverts to holding everything itself once it detects the list is unreliable. This is why the weekly review is not optional housekeeping but the load-bearing habit of the whole method.
Key ideas
- The five steps. Capture everything, clarify what each thing means and what it demands, organise the results into the right lists, reflect through regular review, and engage by choosing what to do now.
- The next action. Always define the next physical step, not the project. “Plan holiday” stalls; “call Sam to check his August dates” does not.
- The two-minute rule. If clarifying reveals an action that takes under two minutes, do it immediately — tracking it costs more than doing it.
- Projects versus actions. Anything requiring more than one action is a project and needs its own list, with at least one live next action attached at all times.
- Contexts. Group actions by what they require — phone, computer, errands, a particular person — so you can work from whichever list your current situation permits.
- The weekly review. A recurring session to empty inboxes, update lists, and check every project has a next action. Allen treats this as the difference between a system and a graveyard.
- Horizons of focus. Six altitudes from current actions up through projects, areas of responsibility, goals, vision, and life purpose — a corrective to the charge that GTD is all tactics and no direction.
Who it’s for
Ideal for anyone whose work arrives from many directions at once and who has outgrown a single to-do list. Be realistic about the cost: the initial capture can take a full weekend, and the system decays fast without the weekly review, which is where most adopters quietly fail. The book itself is a chore in places — dry consultant prose, corporate anecdotes, considerable repetition, and a workflow diagram more elaborate than it needs to be. It also shows its age. Written before smartphones, its context lists assume a world where “at the computer” was a meaningful constraint, and the revised edition updates the examples without rethinking that premise. None of that undermines the core insight, which has held up better than almost anything else in the genre: capture everything, decide the next action, review regularly.