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.