Getting Things Done (GTD): A Plain Guide and an Honest Critique

Getting Things Done, usually shortened to GTD, is a productivity method from David Allen's 2001 book of the same name. The core idea fits in one sentence: your head is for having ideas, not for holding them. So you move every commitment, however small, out of your brain and into an external system you trust, and then you work from that system instead of from memory.

It is probably the most influential productivity method ever written down. It has sold millions of copies, spawned an industry of apps and courses, and shaped tools like Todoist, OmniFocus and Things so deeply that their vocabulary is Allen's vocabulary. In our experience, it is also the method with the widest gap between the people who praise it and the people who still practice it.

That gap is not an accident. GTD rarely fails on day one. It fails quietly, six weeks in, at one specific recurring chore that the enthusiastic blog posts tend to skim past. We will get to that chore. First, the plain-English version of the method, because most summaries make it sound more complicated than it is.

The five steps, in plain English

GTD is a loop with five steps: capture, clarify, organize, reflect, engage. Here is what each one actually asks of you.

Capture

Write down everything that has your attention. Not just work tasks: the dentist appointment you keep almost booking, the email you owe your aunt, the vague sense that the car is making a new noise. Everything goes into an inbox, which can be a notebook, an app, a voice memo, or a tray on your desk. The rule is that nothing is allowed to live only in your head.

This is the part of GTD that almost everyone loves, because the relief is immediate and physical. Unfinished business hums in the background of your attention until it is recorded somewhere, and a genuinely complete capture silences a surprising amount of that hum. People finish their first big capture session and describe it like putting down luggage they forgot they were carrying.

Clarify

Then you process the inbox, item by item, asking one question: is this actionable? If not, it gets deleted, filed as reference, or parked on a someday/maybe list. If it is actionable, you decide the very next physical action. Not "sort out insurance" but "call the broker and ask for the renewal quote." Allen is strict about this, and he is right to be: vague items repel you, concrete ones do not.

This is also where the famous two-minute rule lives. If the next action would take less than two minutes, you do it immediately, because filing and tracking it would cost more than just finishing it.

Organize

Actions get sorted onto lists by context, meaning the place or tool they require. Classic GTD uses lists like @phone, @computer, @errands and @home. Anything that needs more than one step becomes a project, and every project must always have a next action attached. Appointments and hard deadlines go on the calendar, and only those. Things you are waiting on from other people go on a waiting-for list.

Reflect

Once a week, you sit down and review the whole system: empty every inbox, reread every project, check every list, prune what is dead, add what is missing. Allen calls this the weekly review, and he is blunt about its importance. It is the step that keeps the system trustworthy. Hold that thought, because we are coming back to it.

Engage

Finally, you do the work, choosing what to do in the moment based on four filters: your context, your available time, your available energy, and priority. Notice that priority comes last, and notice what the whole arrangement assumes. GTD trusts you to make good in-the-moment choices, as long as your lists are complete and current.

Who GTD is genuinely great for

We want to be fair here, because the critique that follows is not "GTD is bad."

GTD is superb for people whose central problem is volume: too many inputs, too many commitments, too many open loops colliding in one overworked head. Managers, founders, anyone running a job and a household and an aging parent's paperwork at the same time. If your mind spins at 2 a.m. reciting things you must not forget, a complete capture into a trusted system is about as close to medicinal as a productivity method gets.

It is also great for people who already have a stable rhythm of self-administration, the sort of person who reconciles their bank account every month without drama. GTD does not create that rhythm. It rewards it, magnificently.

And parts of it are simply true for everyone. Capture everything: yes. Define the next physical action: yes. The two-minute rule: yes, with the caveat that it can quietly become a way to spend the whole day doing two-minute things. If you take nothing else from Allen, take those three.

Where Getting Things Done (GTD) quietly breaks down

Here is the honest critique, and it is mechanical rather than a matter of taste.

GTD contains no scheduler and no prioritizer. Its answer to "but when do I actually do these things, and which one matters most?" is: keep the lists complete, then trust your in-the-moment judgment. The whole method therefore rests on one load-bearing component, the weekly review. Lists that are not reviewed stop being complete. Lists that are not complete stop being trusted. Lists that are not trusted stop being used. Allen says this himself, repeatedly. The weekly review is not a nice-to-have. It is the engine.

Now look at what the weekly review actually is. It is one to two hours of pure administration: emptying inboxes, rereading every project, deleting dead actions, updating someday/maybe. It produces nothing visible. It has no deadline, and nobody is waiting for it. It is, in other words, precisely the species of recurring, low-stimulation, high-executive-function chore that a busy brain postpones and an ADHD brain is practically wired to avoid. The one component GTD cannot survive without is the component its most hopeful adopters are least equipped to sustain.

And the failure is silent. Skip one review and nothing happens. Skip three and your lists are subtly wrong: finished things still listed, new commitments missing, projects with no next action. There is no crash and no error message. There is just a Tuesday when you realize you have not opened the app in two weeks and you are running on memory and adrenaline again, while a guilt-inducing monument to week two sits in your dock. We wrote about this pattern more broadly in why to-do lists don't work for ADHD: the failure point of list systems is almost never the list. It is the upkeep.

Two smaller structural gaps deserve a mention. GTD says very little about time. Contexts tell you where you could do something, not when anything will actually happen, which is rough on anyone with time blindness. And at ground level it says almost nothing about importance: a complete next-action list treats "reply to the newsletter" and "prepare the interview that could change your year" as equal neighbors. Allen answers this with higher "horizons of focus," but in practice almost nobody reviews their horizons, for exactly the same reason they skip the weekly review.

Running a lighter GTD

None of this means you should throw the method out. It means you should shrink it until the maintenance fits inside the attention you actually have. Here is the version we would suggest.

Keep capture, absolutely, but cut down to one inbox. Five capture points means five things to empty. Voice is the lowest-friction capture there is: saying a thought out loud the moment it appears beats finding the right app and the right field, and it works while you are walking, driving or making coffee.

Cut contexts to two or three. The @phone, @computer, @errands taxonomy was designed in 2001, when those were genuinely different physical places. On a laptop, everything is @computer. A split like deep work, shallow work and errands does the same job with a tenth of the sorting.

Replace the two-hour weekly review with a fifteen-minute one, attached to an anchor that already exists in your week, like Friday's last coffee or Sunday's laundry cycle. Empty the inbox, glance at active projects, pick the three things that matter most next week. That is the whole review. An imperfect review that happens beats a canonical one that does not.

Then add the two things GTD deliberately leaves out. For importance, borrow a simple filter: we wrote a full guide to the Eisenhower matrix, which pairs unusually well with GTD lists precisely because it answers the question GTD refuses to. For time, put your three chosen things on the calendar instead of trusting your in-the-moment self to pick them over whatever is loudest.

Finally, let software carry the rote parts. This is the one place automation genuinely helps a GTD-ish system: resurfacing items that have gone stale, rescheduling what slipped, prompting the mini-review so it does not depend on you remembering the meta-task. Automation cannot do your weekly thinking for you, and tools that promise otherwise are selling something else. But it can make sure the thinking gets triggered, and for most people the trigger was the actual point of failure. If you are weighing GTD against other systems entirely, we compared eight productivity methods honestly, including where each one tends to die.

What this will not fix

A lighter GTD still will not decide what matters to you. No capture system knows your goals unless something upstream is holding them. It will not fix task initiation either: a perfectly clarified next action can still sit untouched for days, and if that is your pattern, the problem was never your lists. And nothing in this article is treatment. If ADHD is part of your picture, a method plus a tool sits alongside diagnosis, therapy, coaching or medication, never in place of them.

Where we fit in

We are Skedul, and we build in this space, so read the previous sections knowing that. Skedul is a voice-first AI planner organized around goals rather than tasks: you talk to it, it breaks your goals into milestones and daily actions, schedules them around your real energy, and rebuilds the plan when the day falls apart. Our philosophy is accountability and consistency rather than automation, which makes us a complement to GTD's thinking, not a replacement for yours.

If you suspect your own system is rotting somewhere specific, the free productivity assessment takes about three minutes, needs no account, and tells you which of six common failure patterns is most likely yours.

Quick answers

What does GTD stand for, and what is it in one sentence? GTD is Getting Things Done, David Allen's method for moving every commitment out of your head and into a trusted external system, organized as five steps: capture, clarify, organize, reflect, engage.

What is the two-minute rule in GTD? While processing your inbox, if an action would take less than two minutes, you do it immediately instead of filing it, because tracking it would cost more than finishing it. It is the most portable piece of GTD, though it can turn into a full day of two-minute tasks if you let it run your schedule.

Is GTD good for ADHD? The capture habit is genuinely helpful, because it externalizes working memory. The full system is risky, because it depends on a weekly review that is exactly the kind of recurring executive-function chore ADHD makes hard to sustain. A reduced version, with one inbox, two or three contexts and automated review prompts, survives much longer.

How long should a GTD weekly review take? Allen's canonical review runs one to two hours. If that is not happening, a fifteen-minute version that empties the inbox, scans projects and picks next week's priorities preserves most of the value. A short review you actually do beats a complete one you keep postponing.