Getting Things Done is famously elaborate, which is a shame, because the part of it that actually works is about fifteen minutes of setup. The rest is elaboration — useful for some, fatal for many, because elaborate systems don’t survive a bad week.
Here is the whole thing, stripped to what earns its keep.
You need five things
- An inbox. One place where anything goes when you think of it. No folders, no categories. Just a capture surface that’s faster than the thought it’s catching.
- A triage step you do regularly. Weekly is enough. The job is to decide what each inbox item is — task, project, reference, or delete — and move it out of the inbox. The inbox is not storage. It’s a staging area.
- One goal. Not five. The active outcome you’re working toward — “get finances under control,” “ship the launch.” Goals are the why; they scope everything beneath them.
- One project. The current chunk of work toward that goal. Something with a clear done state. If you can’t say what done looks like in one sentence, it’s not a project yet, it’s an intention.
- One task. The next concrete action on that project. Small enough to start. Verbable. Not “do taxes” but “open last year’s return and find the carryover.”
That’s it. Inbox, triage, goal, project, task. You can build this on paper. The elaborate five-phase flowchart is a description of how this works at scale, not a requirement to start.
Why this is enough
The mistake is thinking the system needs to be complete before it’s useful. It doesn’t. A partial system you actually use beats a perfect one you avoid, every time, because the value is in the practice — the regular capture and the regular triage — not in the taxonomy.
You will notice, after a week or two, that certain things don’t fit. A second goal emerges. A project turns out to be two. A task keeps stalling and needs breaking down. That’s how the structure grows — from use, from the friction you actually hit, not from a template you build up front. The fifteen-minute start is honest because it’s under-built, and under-built systems get shaped by reality. Over-built ones get abandoned by it.
The one habit that makes it work
If there’s a single thing to lock in, it’s the weekly triage. Not doing the work. Just looking at the inbox and deciding, item by item, what each thing is and where it goes. Twenty minutes. It is, by a wide margin, the highest-leverage twenty minutes in any system, because it’s the step that keeps the inbox from becoming a swamp and the task list from becoming a wishlist.
Most people never establish it. They capture, they act, they wonder why the list is a mess. The triage is the missing step, and it is also the only step that feels like overhead, which is why it gets skipped. Do it anyway. For a month. After that the relief is its own argument.
What this becomes
From these five things, the full methodology opens up if you need it. Someday lists for the maybes. Multiple goals once one is rolling. Projects broken into sub-projects when they get complex. A lens or context system for separating work from life.
But none of that is required to start, and most of it is wrong to build before you need it. The fifteen-minute system is not a stepping stone to the real thing. For a lot of people, it is the real thing, and the elaboration is what sinks them.
Start small. Triage weekly. Let the structure earn each new piece.