IX Coach

Getting Things Done (GTD), Made Practical

The five steps, the next-action habit, and the science of offloading your mind

How does the Getting Things Done (GTD) method actually work?

David Allen’s GTD runs every commitment through five steps — capture, clarify, organize, reflect, and engage — so nothing lives in your head and you always know the next physical action. The core insight, that unfinished tasks held in memory create persistent mental load, is supported by cognitive research; GTD itself is a coherent practitioner system rather than a single tested protocol.

GTD is built on one premise: your mind is for having ideas, not holding them. By moving every open loop out of your head into a trusted external system and deciding the very next action, you free attention for the work in front of you. Below are the core practices, each with the mechanism that makes it work and an honest read on the evidence.

Practices

How these practices connect

Every practice in GTD manages the same limited resource: attention that gets consumed the moment a commitment is undefined or untrusted. Capture removes undefined commitments from memory, clarifying removes the ambiguity that stalls action, contexts remove the feasibility check at decision time, and the weekly review keeps all of it trustworthy enough that attention actually stays freed. Each practice is a different point where an open loop would otherwise silently tax working memory.

Do you have to follow the steps in order?

Mostly yes, because each step depends on the one before it. You cannot clarify a next action for something you have not captured, and organizing actions by context only works once each action has already been clarified into something concrete. The two-minute rule is applied during clarifying, not as a separate later step. The weekly review and engaging with your list are the two steps that run on a loop rather than once through.

Why do I still feel anxious even though I wrote everything down?

Writing something down only quiets the mind if you actually trust that list is current and complete, and that trust depends on continuing to review it. If items sit uncaptured in scattered places, or a captured list goes stale because the weekly review got skipped, the brain resumes holding those loops as backup because it cannot verify the external system is reliable. The relief is not from the act of writing, it is from the trust that the writing removed the need to remember.

What's the difference between the two-minute rule and just organizing by context?

The two-minute rule is a decision made once, during clarifying, about whether a specific action is even worth tracking at all. Organizing by context happens after that decision, for everything that was worth tracking, and sorts those remaining actions by where or with what they can be done. One decides in from a list, the other decides out of it entirely before a list is built.

Why do context lists work better than one big to-do list?

A single master list forces you to make two decisions every time you look at it: what can I even do right now, and what should I do next. The first question is pure overhead because your current situation, whether you have a phone, are near a computer, or are out running errands, already rules most items out. Sorting actions into context lists in advance answers that feasibility question at filing time, so at the moment of choosing you are only weighing the actually useful comparison.

What happens if I stop doing the weekly review?

The lists and contexts stop being trustworthy, and trust is the entire mechanism the rest of GTD depends on. Once you suspect a list is out of date, your mind starts re-holding those commitments as backup, which undoes the relief that capturing was supposed to provide. It also directly undermines engaging with your work fully present, since that state depends on believing you are not forgetting something a stale list would have caught.

Is GTD actually backed by research or is it just a productivity trend?

The support is mixed and mostly indirect rather than a single study validating the whole method. Making tasks concrete and specific has experimental support for improving follow-through, but GTD's particular way of sorting those tasks into projects and contexts is practitioner structure layered on top of that finding. The capture, review, and engagement mechanisms are argued from observation and from how attention appears to work, not from randomized trials of GTD itself, and the two-minute threshold is an arbitrary number rather than a tested one.

How do you choose between these?

If something is on your mind and undone, capture it first regardless of what else is happening, since an unwritten commitment is the thing actively costing you attention. If you are looking at a captured item and cannot start on it, the problem is almost always that it is still vague, so clarify it into a concrete next action before doing anything else. If a clarified action would take under two minutes, do it immediately rather than filing it. When you are choosing what to work on next from an already-clarified list, pull from the context list that matches where you are and what tools you have available. Run the weekly review on a fixed cadence regardless of how the week went, because it is precisely the busy weeks when skipping it feels tempting that the system most needs it to stay trustworthy.

What these approaches do not settle

The evidence underneath these practices is uneven: task specificity improving follow-through has experimental backing, but the weekly review, the two-minute cutoff, and the felt relief from capturing are argued from mechanism and observation rather than direct trials of GTD as a whole. Context-based sorting is also a convention rather than a universal law, since some people find organizing by priority or energy level more useful than organizing by location or tool. And all of it depends on a single condition that is easy to let slip: the freed attention only lasts as long as you genuinely trust the system, so a capture tool you stop reviewing or a two-minute rule that runs unchecked through focused work time can quietly undo the benefit each practice is meant to provide.

Practice this with IX Coach

Practice this with IX Coach

Frequently asked questions

How does the Getting Things Done (GTD) method actually work?

David Allen’s GTD runs every commitment through five steps — capture, clarify, organize, reflect, and engage — so nothing lives in your head and you always know the next physical action. The core insight, that unfinished tasks held in memory create persistent mental load, is supported by cognitive research; GTD itself is a coherent practitioner system rather than a single tested protocol.

How do you capture everything into a trusted inbox?

Unfinished tasks held only in memory generate intrusive reminders and background tension — the mind keeps re-surfacing them because it cannot tell whether they are handled. Writing each one into a single trusted capture tool lets the brain stop rehearsing it, freeing the attention those open loops were silently consuming.

How do you clarify each item into a concrete next action?

A vague entry like "taxes" stays on a list untouched because the brain has no executable instruction to run — it sees an undefined project and stalls. Forcing each item into a concrete next physical action ("download last year’s return") removes the in-the-moment decision cost that causes procrastination, so starting requires almost no deliberation.

What is The two-minute rule?

The overhead of capturing, organizing, and later re-engaging a tiny task can exceed the cost of just doing it. For very short actions, deferring is net-negative — it adds tracking load and a future context-switch. Doing them immediately keeps the system lean and prevents trivial items from accumulating into a demoralizing backlog.

Context in GTD: how do you sort actions by where you can do them?

You can only do what your current situation allows — errands need to be out, calls need a phone, certain tasks need a specific person present. Grouping actions by context means that in any given moment you see only the things you can actually do right now, removing the friction of scanning an undifferentiated master list and deciding what is even possible. The deeper reason this works is that a master list forces two decisions at once — "what can I do here?" and "what should I do next?" — and the first one is pure overhead you pay every time you look. Context lists pre-answer the feasibility question at filing time, when you are already thinking about the task, so that at the moment of choosing you are only doing the second, genuinely useful comparison. It also changes what a list is for: a context list is not a record of everything outstanding, it is a menu for a specific situation, which is why a good one is short enough to read without scrolling.

How do you run a weekly review?

A capture system only quiets the mind as long as the mind trusts it is current — the moment lists go stale, the brain resumes holding loops as backup. The weekly review re-establishes that trust by clearing inboxes, updating project lists, and confirming every commitment has a next action, so the system stays the reliable external memory the whole method depends on.

Engage: how do you choose work from a clear mind?

Once open loops are externalized and clarified, you no longer have to weigh every possible task each time you choose what to do — the deciding has mostly been done in advance. That lets you engage with a chosen action without the background anxiety that you are forgetting something, which is the state in which focused, present work becomes possible.

Do you have to follow the steps in order?

Mostly yes, because each step depends on the one before it. You cannot clarify a next action for something you have not captured, and organizing actions by context only works once each action has already been clarified into something concrete. The two-minute rule is applied during clarifying, not as a separate later step. The weekly review and engaging with your list are the two steps that run on a loop rather than once through.

Why do I still feel anxious even though I wrote everything down?

Writing something down only quiets the mind if you actually trust that list is current and complete, and that trust depends on continuing to review it. If items sit uncaptured in scattered places, or a captured list goes stale because the weekly review got skipped, the brain resumes holding those loops as backup because it cannot verify the external system is reliable. The relief is not from the act of writing, it is from the trust that the writing removed the need to remember.

What's the difference between the two-minute rule and just organizing by context?

The two-minute rule is a decision made once, during clarifying, about whether a specific action is even worth tracking at all. Organizing by context happens after that decision, for everything that was worth tracking, and sorts those remaining actions by where or with what they can be done. One decides in from a list, the other decides out of it entirely before a list is built.

Why do context lists work better than one big to-do list?

A single master list forces you to make two decisions every time you look at it: what can I even do right now, and what should I do next. The first question is pure overhead because your current situation, whether you have a phone, are near a computer, or are out running errands, already rules most items out. Sorting actions into context lists in advance answers that feasibility question at filing time, so at the moment of choosing you are only weighing the actually useful comparison.

What happens if I stop doing the weekly review?

The lists and contexts stop being trustworthy, and trust is the entire mechanism the rest of GTD depends on. Once you suspect a list is out of date, your mind starts re-holding those commitments as backup, which undoes the relief that capturing was supposed to provide. It also directly undermines engaging with your work fully present, since that state depends on believing you are not forgetting something a stale list would have caught.

Is GTD actually backed by research or is it just a productivity trend?

The support is mixed and mostly indirect rather than a single study validating the whole method. Making tasks concrete and specific has experimental support for improving follow-through, but GTD's particular way of sorting those tasks into projects and contexts is practitioner structure layered on top of that finding. The capture, review, and engagement mechanisms are argued from observation and from how attention appears to work, not from randomized trials of GTD itself, and the two-minute threshold is an arbitrary number rather than a tested one.

Research

Related concepts

Articles that cover this