Getting Things Done, simplified: the parts worth keeping

Filed under Guide

By Gerald · 3 August 2026

A small wooden box sitting empty on a desk, standing in for an inbox that has actually been cleared

Getting Things Done has two kinds of readers. People who treat it like scripture and run the full system for years, and people who tried it once, built a dozen context lists, and quietly went back to a plain notepad three weeks later.

Both groups are reacting to the same book. The core of GTD is genuinely good. Most of the apparatus built around that core is not, and David Allen's own site still teaches the full five-step version: capture, clarify, organize, reflect, engage. That is not wrong. It is just more than almost anyone sustains.

Capture, decide the next action, and review weekly. That is the whole method that actually survives contact with a real job.

Here is the simplified version, what I dropped, and what dropping it costs you.

The three GTD ideas that survive

Capture everything, immediately, without sorting it first. The moment you try to decide where something belongs while you are also trying to remember it, you lose both. A single inbox, a phone app or a notebook you always have on you, is the entire mechanism. The genius of this part is that it asks nothing of you except noticing.

The two-minute rule. If acting on something takes less time than deciding what to do with it would, just do it. This one rule prevents more inbox rot than any organizing scheme. Replying to a short email, filing a receipt, scheduling a call: these are the tasks that pile up precisely because they feel too small to deserve a place in a real system, and then there are four hundred of them.

A defined next action, not a vague project name. "Plan the office move" is not a task, it is a folder with no floor in it. "Call the moving company for a quote" is a task. The habit of asking "what is the next physical action here" is the single highest-leverage move in the entire methodology, because it turns a paralyzing blob into something you can actually start.

Those three ideas are why GTD became influential in the first place. They would still be worth teaching if the rest of the book did not exist.

The parts I dropped and why

A hand holding a blank sticky note above a grid of other blank sticky notes on a desk — Sorting a stack of captured items by hand is the whole discipline. GTD just gives it a name and a shape.

Contexts. GTD asks you to tag every next action with where or how it can be done: @calls, @computer, @errands, @home. This made real sense in an era when you genuinely could not answer email from the grocery store. On a smartphone, almost every context collapses into one: wherever you are, you can probably do the task. Maintaining tags that no longer separate anything is pure overhead.

The tickler file. A 43-folder system (31 for days of the month, 12 for months) that resurfaces items on a future date. It is an elegant solution to a problem that a calendar reminder or a due date field already solves, with far less physical or digital furniture to maintain.

The someday/maybe list, treated as a first-class system. Keeping a list of things you might do eventually is fine. Treating it as a formal, regularly reviewed component of your system usually turns into a guilt archive: a growing pile of good intentions you revisit weekly and never act on. I still keep a rough version of this, I just do not pretend it needs its own review ritual.

Project support material as a formal category. GTD separates "projects" from "next actions" from "reference material" into distinct, tracked buckets. In practice, most personal work does not have enough moving parts to justify three separate taxonomies. One list of active commitments, with detail attached to each item when it needs it, does the same job with a fraction of the setup.

A simplified GTD setup in three lists

Inbox. Everything lands here first, no exceptions, no pre-sorting. A capture app, a paper notebook, whatever you will actually use in the moment an idea shows up.

Active. The short list of things you have committed to doing soon. Not everything you have ever thought of. If this list is longer than what you could plausibly finish in a week, it has stopped being a active list and become a second inbox wearing a costume.

Done. A visible record of what moved. This one is optional for GTD purists but it matters more than people expect, because seeing progress is what keeps you trusting the system on the weeks it is hardest to trust it.

This maps directly onto a three-column board: a triage column for the inbox, an executing column for active work, and a done column for the record. If you already use a kanban tool for anything, you already have the scaffolding for this version of GTD without adding a new app.

Turning a next action into something you will actually do

The GTD habit worth stealing on its own, separate from the rest of the system, is the next-action test. Look at anything sitting in your active list and ask: what is the literal next physical or digital step. Not the outcome. The step.

"Fix the website" fails the test. "Open the contact form and check why it is not sending email" passes. The failed version sits untouched for a month because starting it requires a decision you have not made yet. The passed version gets done in the next open ten minutes, because there is nothing left to decide.

Apply this test only when something is stuck. Do not force every item on your list through a formal clarify step, that is exactly the overhead this simplified version exists to avoid.

What the simplified version costs you

Be honest about the tradeoff, because there is one. Dropping contexts means you lose the ability to filter "what can I do right now, standing in this specific place, with this specific tool." For most personal work in 2026 that filter rarely matters. For a plumber, an electrician, or anyone whose work is genuinely location-bound, it still might.

Dropping the tickler file means date-sensitive items live on a due date field instead of a physical resurfacing mechanism. That is fine as long as your tool actually surfaces due items reliably. If it does not, you will drop things.

Dropping the formal someday list means good ideas you are not ready to act on need somewhere to live that is not your active list and not nowhere. A notes app with a tag works. The point is that it needs to exist somewhere, even in the simplified version, or you will lose ideas you would have wanted back.

Dropping the weekly review entirely, rather than simplifying it, is the one cut I would not make. Reflect is the step that keeps the other four honest. A five to twenty minute version, look at the inbox, look at the active list, cut what no longer matters, still needs to happen on a fixed cadence or the whole thing quietly drifts back into chaos over a few months.

Who still needs full GTD

If you run multiple active projects with real dependencies, people to delegate to, and deadlines that genuinely shift based on external factors, contexts and formal project tracking earn their keep. Full GTD was built for exactly that kind of complexity, and the simplified version above will feel thin if that is your actual situation.

If your work is mostly personal, with a handful of active commitments and no team to coordinate, the three-list version will do everything full GTD does for you, with a fraction of the maintenance.

Frequently asked questions

What is the simplest version of GTD? Capture everything into one inbox, sort it into a short active list using a clear next action for each item, mark things done visibly, and review the whole thing for a few minutes once a week. That is the version that survives.

Do I still need contexts in GTD? Almost never, for personal work in 2026. Contexts solved a problem from an era of separate work and non-work tools and locations. On a phone, most tasks can be done from most places, so the tag stops doing useful filtering.

Is GTD outdated in 2026? The core ideas, capture, a clear next action, a regular review, are not outdated at all, and gettingthingsdone.com still teaches them as the foundation. The apparatus built around that core, contexts, tickler files, formal someday lists, is what shows its age. Keep the core, drop the rest.

What is the difference between GTD and a kanban board? GTD is a decision-making method: how you clarify and organize what lands in front of you. A kanban board is a visual layout: columns showing where things sit in a workflow. They are not competitors. A simplified GTD system maps cleanly onto a three-column board, triage, active, done, so you can run the method inside the layout.

Which app works best for a simplified GTD system? Almost anything that lets you capture fast, keep a short active list, and mark items done will work. The method matters more than the app. A three-column personal kanban board is a natural fit because it mirrors the three-list version directly, without forcing contexts or tags you do not need.