Concepts & methods

GTD: what Getting Things Done solves, and where it breaks

David Allen's method gave a generation trusted capture and the weekly review. An honest reference entry: what the five steps actually fix, the two places the system stalls, and what it never promised to do.

Aleem O'BalogunBy Aleem O'Balogun|Updated |5 min read

The short answer

GTD (Getting Things Done) is David Allen's method for getting every commitment out of your head into a trusted external system, then deciding next actions through a regular review. It genuinely solves the open-loop problem: things stop being remembered anxiously and start being tracked. What it does not do is put those actions into time.

What it is, and who made it

Getting Things Done is the method David Allen published in 2001 (revised 2015), built on one observation: your head is for having ideas, not holding them. Everything that has your attention, from a client deliverable to a dripping tap, is an open loop, and unclosed loops leak attention whether or not you are working on them. The method's answer is five steps: capture everything into trusted places, clarify what each thing actually is and what the next physical action would be, organise the results into lists by context, reflect on the whole system regularly, and engage with the action you chose. The canonical source is Allen's book and gettingthingsdone.com.

Two of its inventions became infrastructure for everything that came after: the capture habit (write it down the moment it lands, sort later) and the weekly review, the standing appointment where you empty the inbox, look at every list, and re-decide what matters. Almost every serious system since, digital or paper, is running some descendant of those two moves.

What it actually solves

GTD's genuine cure is the anxiety of the untracked. When every commitment lives in a system you actually trust, the 3am rehearsal of everything you might be forgetting quiets down, because forgetting is no longer how things fail. The next-action discipline fixes a second real problem: most stuck tasks are stuck because they are secretly projects (“sort the car insurance”), and naming the next physical action (“find the renewal date”) un-sticks them.

It is also honestly scoped. Allen never claimed the method decides your priorities for you; it promises a complete inventory and a clear head, so that choosing is at least made from the full picture.

Where it breaks

The first break is time. GTD produces immaculate lists of next actions with almost nothing to say about when anything happens; the calendar is reserved for genuine appointments, and everything else lives in lists you consult in the moment. In a life where the real constraint is a full week rather than an unclear next step, a perfect list meets a packed calendar and loses. This is the gap the whole time-blocking tradition exists to fill.

The second break is the review itself. The weekly review is the system's heartbeat, and it is the part most practitioners quietly stop doing, at which point the lists silt up and trust collapses. A method whose single point of failure is its least pleasant ritual has a durability problem, and Allen himself calls the review the critical success factor. The third, smaller break: GTD was born in executive work, and its vocabulary (projects, contexts, agendas) fits a briefcase more naturally than a family, a training plan, or a Sunday.

How it maps to the notice loop

On the notice loop's six verbs, GTD is strongest at the ends: capture is its masterpiece, and the weekly review is a genuine review-and-learn ritual that most later systems copied. The middle verbs are thinner. Noticing is manual and periodic: nothing surfaces the renewal or the birthday until you happen upon it in a list. Shaping barely exists: the method hands you a complete inventory and leaves the week's actual design to you. Run GTD alone and you get a trustworthy warehouse with no delivery schedule; run its capture and review verbs inside a weekly shape, and the warehouse finally ships.

Sources

Primary sources for the method as described; the assessment of where it breaks is editorial, argued in the text.

  • David Allen, Getting Things Done: The Art of Stress-Free Productivity (2001; revised edition 2015), and gettingthingsdone.com. The five steps, the open-loop framing, and the weekly review as critical success factor.
← All guides