Methodology
Getting Things Done: the definitive guide
Last updated:
David Allen published Getting Things Done in 2001. Twenty-five years later, GTD remains the most widely adopted personal productivity methodology in the world. Not because it's trendy — because it works. This guide covers the complete system: the five steps, the processing flowchart, the lists you need, and the habit that holds it all together.
The core idea
GTD is built on one observation: your brain is terrible at remembering things, but very good at having ideas about things. When you try to use your mind as a storage system — holding meetings, deadlines, errands, promises, and half-formed plans — it creates a low-level anxiety that Allen calls “open loops.” Each open loop takes up cognitive space, even when you're not actively thinking about it.
The fix is mechanical, not motivational. Get everything out of your head and into a trusted external system. Define what “done” looks like for each commitment. Decide the very next physical action. Review the whole system regularly.
When the system is complete and current, your mind stops tracking. Allen calls this “mind like water” — the state where you can respond appropriately to whatever comes up because you're not mentally juggling fifty other things. It's not about doing more. It's about the clarity to choose what to do with confidence.
“Your mind is for having ideas, not holding them.” — David Allen
The five steps of GTD
GTD is a workflow with five distinct stages. Every piece of “stuff” in your life moves through these stages, in order.
1. Capture
Collect every open loop — every task, idea, commitment, question, or nagging thought — into an inbox. This can be a physical tray, a notes app, a voice memo, an email folder, or a task manager inbox. The medium doesn't matter. What matters is that you capture everything and that you trust yourself to process it later.
The goal is zero residue. If something is on your mind, it goes into the inbox. Don't organize, don't prioritize, don't evaluate. Just capture. You'll sort it in the next step.
Common inboxes: physical tray on your desk, email inbox, task manager inbox, notes app, voice memos during commute, a pocket notebook.
2. Clarify (Process)
Take each item in your inbox, one at a time, starting from the top, and ask: “Is this actionable?”
If the answer is no, the item goes to one of three places:
Trash. Delete it. It's not relevant.
Reference. File it. It's useful information but requires no action. Recipes, serial numbers, meeting notes, articles.
Someday/Maybe. Park it. It's something you might want to do eventually but not now. Learn Italian, build a deck, write a book. These get reviewed periodically to see if they've become actionable.
If the answer is yes, you need to define two things:
What's the desired outcome? If it takes more than one action to finish, it's a project. “Plan holiday” is a project. “Book flights to Lisbon” is an action.
What's the very next physical action? Not “work on presentation” — that's vague. “Open slide deck and write the three key points for slide 4” — that's a next action. It's concrete, visible, and doable.
Then apply the decision tree:
Under 2 minutes? Do it now. The overhead of tracking it exceeds the effort of doing it.
Someone else's job? Delegate it and put it on your Waiting For list with the date you delegated.
Not actionable yet? Set a defer date — the date it becomes actionable — and let it hibernate until then.
Actionable now? Put it on your Next Actions list, filed by context.
3. Organize
Every clarified item goes into one of several lists. These lists are the backbone of your trusted system:
Next Actions. Single, concrete actions you can do right now. Organized by context — @computer, @phone, @errands, @office — so when you're at a certain place or have a certain tool, you see only what you can actually do there.
Projects. Any desired outcome that takes more than one action. Every project must have at least one next action at all times. A project without a next action is a stalled project — and stalled projects are where GTD systems break down.
Waiting For. Things you've delegated or are waiting on someone else to deliver. Each entry includes what you're waiting for, who from, and when you delegated. Review weekly.
Someday/Maybe. Ideas and possibilities you're not committing to right now. Vacation destinations, business ideas, courses to take, books to read. Review monthly or during your weekly review.
Calendar. Only hard landscape items: appointments with a specific date/time, day-specific actions (like filing taxes on April 15), and day-specific information (a colleague is on vacation). The calendar is sacred — only things that must happen on that day go here.
Reference. Non-actionable information you might need later. Filing system, digital or physical.
4. Reflect (Review)
A system you don't review is a system you don't trust. And a system you don't trust is a system you'll abandon.
The weekly review is GTD's most important habit. Allen calls it “the critical success factor for the entire methodology.” Once a week, you:
Empty all inboxes to zero.
Review every active project — does each one have a next action?
Review Waiting For — follow up where needed.
Review Someday/Maybe — promote or delete.
Look at the calendar for the next 1–2 weeks.
Get creative — capture new ideas triggered by the review.
The weekly review typically takes 30–60 minutes. Most people who abandon GTD don't abandon the capture or the lists — they abandon the review. And without the review, the lists decay, trust erodes, and the system collapses. This is the habit worth protecting above all others.
5. Engage (Do)
When it's time to work, you choose what to do based on four criteria, in order:
Context. What can you do where you are, with the tools you have? If you're on a train with just your phone, @computer tasks aren't available.
Time available. You have 15 minutes before a meeting — pick a quick task, not a deep-work project.
Energy available. Low energy? Do admin. High energy? Do creative work. Match the task to your current state.
Priority. Given the first three filters, which of the remaining tasks matters most right now? Trust your intuition here — if your system is clean and current, your gut knows.
At any given moment, Allen says you're doing one of three types of work: (1) predefined work from your Next Actions list, (2) ad-hoc work that appears and is genuinely urgent, or (3) defining work — processing your inboxes and clarifying new items. GTD doesn't tell you what to do. It gives you the clarity to choose wisely.
The processing flowchart
The Clarify step is where most people get stuck. Here's the decision tree as a visual walkthrough. For each item in your inbox, follow the branches:
Pick up the next item from your inbox
↓
Is it actionable?
NO →
Is it trash? → Delete it
Might you need it later? → File as Reference
Might you want to do it someday? → Someday/Maybe list
Need a reminder on a specific date? → Tickler / Defer date
Need to discuss with someone? → Agendas list
YES → Define the next physical action
Can it be done in under 2 minutes? → Do it now
↓ (longer than 2 minutes)
Does it depend on someone else? → Delegate → Waiting For list
Is it tied to a specific date/time? → Calendar
Not yet actionable? → Set a defer date
Actionable now? → Next Actions list (by context)
Does it require more than one step? → Create a Project (define the outcome, add first next action)
Repeat for every item until inbox is at zero. Don't skip items, don't put them back, don't re-read without deciding.
The key discipline is: you process items one at a time, top to bottom. You don't cherry-pick. You don't skip the hard ones. For each item, you make a decision and move it to the right place. If you can't decide, it's because you haven't defined the next action concretely enough.
Projects, areas, and the horizons of focus
GTD defines a project as any desired outcome that requires more than one action step. “Replace kitchen faucet” is a project. So is “Hire a junior developer” and “Plan Mum's birthday.” Most people have 30–100 active projects at any time. That number often surprises people — but once you start listing every multi-step commitment, it adds up.
Every project needs two things: a clear definition of “done” (what does the finished state look like?) and at least one next action. A project without a next action is dead weight in your system. The weekly review catches these.
Above projects, Allen defines Areas of Responsibility — ongoing roles and standards you maintain. Health, finances, career, family, home maintenance. Areas don't have end dates; they're the categories your projects live within. And above areas, he maps out higher “horizons” — from one-to-two-year goals up to your life purpose. These higher levels inform which projects you take on, but the day-to-day system operates at the ground level: next actions.
Some GTD apps support this hierarchy natively. In SingleFocus, areas contain projects, which contain tasks. Projects can be sequential (only the first task is visible, reducing clutter) or parallel. This mirrors Allen's model directly. See Best GTD App 2026 for how different tools handle this.
Where GTD goes wrong
GTD has a high adoption rate and a high abandonment rate. The methodology itself is sound, but the implementation often fails. The most common failure points:
The inbox becomes a second brain
People capture diligently but never clarify. The inbox grows to 200 items. Opening it feels overwhelming, so they stop opening it. The fix: process to zero daily. It takes 10–15 minutes. Not every item needs a decision — most get trashed or filed.
Next actions are too vague
“Work on thesis” isn't a next action. Neither is “Figure out taxes.” When a task is vague, your brain resists it because it needs to do more thinking before it can act. A good next action is a physical, visible activity: “Open tax software and enter W-2 from employer.”
The weekly review gets skipped
This is the single most common reason GTD systems collapse. Without the review, projects stall, lists go stale, and trust evaporates. Scheduling a consistent time — and using an app with a built-in review mode — makes a significant difference.
The tool doesn't match the method
GTD requires specific capabilities: defer dates (to hide non-actionable tasks), sequential projects (to show only the next action), contexts or perspectives (to filter by situation), and a review workflow. Most task managers don't support all of these. Using a general-purpose app for GTD means building workarounds — and workarounds erode consistency. See our comparison of apps for how they stack up.
Perfectionism over progress
Some practitioners spend more time refining their system than using it. Tweaking tag taxonomies, reorganizing areas, debating the perfect app. GTD is meant to be a frictionless pipeline, not an art project. A messy but consistent system beats a perfect but abandoned one.
What GTD actually feels like when it works
When the system is running well, GTD doesn't feel like productivity. It feels like relief. You sit down to work and you don't wonder what you should be doing. You open your Next Actions list, filtered by context, and you pick something. You know everything else is captured and organized. Nothing is falling through the cracks.
The weekly review becomes a reset rather than a chore. You close open loops, clean stale items, and walk away knowing the system is current. The Sunday-evening anxiety about Monday morning fades because you already know what Monday looks like.
The hard part is getting there. The first two weeks of GTD are the hardest — you're building new habits, processing a backlog, and learning the workflow. Most people who stick with it past the third week never go back. Not because they're disciplined, but because the cognitive relief is too valuable to give up.
“GTD isn't about getting more done. It's about being appropriately engaged with your work and your life.” — David Allen
Choosing a GTD tool
You can practice GTD with paper and folders. Allen himself started with manila folders and a label maker. But a digital tool that supports the methodology natively removes friction that paper can't:
Defer dates let you set a task to appear on a future date and disappear until then. No manual re-filing.
Sequential projects show only the next action in a multi-step project. Everything else is hidden until it's relevant.
Custom perspectives let you build context-based views — @computer, @phone, @errands — that filter your list to what's actionable right now.
A review mode walks you through every project, checking for next actions, stalled work, and completed items.
Cross-platform sync ensures ubiquitous capture. If your system isn't available on your phone, your commute, and your work PC, you'll start using a second system — and two systems means no system.
For a detailed breakdown of which apps support these features, see Best GTD App 2026. For Windows users coming from OmniFocus, see OmniFocus for Windows. For the specific case of missing start dates in Todoist, see Todoist Start Dates.
Related guides
How to do a GTD weekly review
The five-step weekly review that keeps your system trustworthy and your mind clear.
Best GTD app in 2026
Which apps actually support GTD? Honest comparison of every option with the features that matter.
GTD at work
How to use Getting Things Done alongside Jira, Slack, and email in a corporate environment.
GTD, built in from day one
SingleFocus is a task manager designed around GTD. Defer dates, sequential projects, custom perspectives, and a guided weekly review — on every platform. Free during early access.
Also see: How to Do a Weekly Review · Defer Dates Explained · ADHD Task Manager
Start free todayYour data stays yours. Export anytime. No lock-in. Data Manifesto →