Habits & Systems

GTD in 2026: A Practical Walkthrough of Getting Things Done

A modern, practical walkthrough of Getting Things Done, covering capture, clarify, organize, and review so nothing important ever slips through.

Desk with lists and sticky notes
Photograph via Unsplash

David Allen's Getting Things Done is old enough now that people treat it like furniture, which is a shame, because the core idea has aged better than almost any productivity book I can name. I have run some version of GTD for years, abandoned it twice, and rebuilt it each time from the same handful of moving parts. This is the walkthrough I wish someone had handed me: not the theory, but how the pieces actually fit together on a normal Tuesday in 2026.

Why GTD still holds up#

The pitch has never really been about doing more. It is about getting commitments out of your head and into a system you trust, so your brain stops trying to remember them at 2am. That single move — externalizing everything — is the reason the method survives, even as the apps around it have changed a dozen times.

What has changed since the book came out is the sheer number of inboxes. In 2003 you had email, voicemail, and a physical tray. Now a single request can arrive by Slack, a text, a shared doc comment, a calendar invite with a buried action, or a voice memo you left yourself in the car. GTD does not care which channel something arrives on. It just insists that everything funnels down into a small number of places you actually look at. That funnel is the whole game.

The system has five stages: capture, clarify, organize, reflect, and engage. They sound bureaucratic written out like that. In practice they are quick, and most of your time is spent in the last one — actually doing the work — which is exactly how it should be.

Capture: get it out of your head#

Capture means writing down, recording, or otherwise trapping every open loop the moment it appears, without judging it. The rule I hold to is that a thought worth having twice is worth capturing once.

The trap people fall into is having too many capture tools, or too few. Too few and things slip because your one notebook is upstairs. Too many and you never remember where you put anything. I keep it to three:

  • A phone app for anything that hits while I am walking around. Whatever you already have open fastest wins here; the specific app matters far less than the speed.
  • A physical notebook on the desk, because writing by hand catches a different kind of thought and never needs a login.
  • My email inbox, which is a capture tool whether I like it or not, so I have stopped fighting it.

The discipline is not in the capturing — capturing is easy and slightly addictive. The discipline is that these are inboxes, not storage. An inbox you never empty is just a pile with better marketing. Which brings us to the step almost everyone skips.

Clarify: decide what the thing actually is#

Clarifying is where GTD earns its keep and where most people quietly give up. You take each captured item and ask one question: is this actionable?

If it is not actionable, it goes one of three places:

  1. Trash, if it no longer matters. Be ruthless here. Most captured thoughts are like moths — bright for a second, then gone.
  2. Someday/maybe, if it might matter later but not now. This is your list of half-formed ambitions and "would be nice" projects.
  3. Reference, if it is information you may need but requires no action. A confirmation number, a link, an address.

If it is actionable, you ask a second question: what is the very next physical action? This is the part that took me years to do properly. "Plan Mum's birthday" is not an action; it is a project. The next action might be "text my sister to agree a date." The difference sounds pedantic until you notice that vague items are the ones that rot on your list for weeks. Your brain refuses to start "plan Mum's birthday" because it does not know where to grab it. It will happily send one text.

A few clarify rules worth internalizing:

  • If an action takes under two minutes, do it now. Filing it costs more than doing it.
  • If it belongs to someone else, hand it off and track it on a waiting-for list so it does not vanish.
  • If it has to happen on a specific day, it goes on the calendar — and only genuinely date-specific things go on the calendar. The calendar is sacred ground, not a wish list.
  • Anything with more than one action becomes a project, which just means it needs a defined outcome and its own next action.

Organize: put actions where you will see them#

Once things are clarified, they need homes. The list structure I use maps directly onto how the day actually unfolds:

  • Next actions, split by context (more on that below)
  • Projects, each one a line with a clear finish state
  • Waiting for, everything I have delegated or am blocked on
  • Someday/maybe, reviewed but not acted on weekly
  • Calendar, for hard dates only

Contexts, updated for how we work now#

The original contexts were things like @phone, @office, @errands — physical constraints on where you could do a task. Half of those have dissolved. I can make a call from anywhere and I no longer drive to a shop for most errands.

So I have quietly redefined my contexts around energy and tools rather than location:

  • @deep for work that needs a focused, uninterrupted block
  • @shallow for the admin I can knock out while half-awake
  • @calls for anything requiring a live conversation
  • @errands for the genuine leave-the-house tasks that still exist

The point of contexts has not changed even though the labels have. When I have twenty low-energy minutes before a meeting, I do not want to scroll my entire task universe. I want to open @shallow and see six things I can plausibly finish now. Context lists exist so your list matches your situation instead of taunting you with work you cannot start.

Reflect: the weekly review is the whole system#

Here is the uncomfortable truth I learned the hard way. Every time GTD collapsed on me, it was the same failure: I stopped doing the weekly review. Capture, clarify, and organize are the visible parts, but the review is the load-bearing wall. Skip it for two weeks and your lists silently stop reflecting reality. Once you sense they are out of date, you stop trusting them, and once you stop trusting them, you go back to running your life out of your head and your inbox.

My review takes somewhere between forty minutes and an hour, usually Friday afternoon when my brain is too tired for real work anyway. The checklist is fixed so I do not have to think:

  1. Empty every inbox to zero — email, notebook, phone app, the lot.
  2. Review the projects list and confirm each one has a live next action. Projects without a next action are where things stall.
  3. Scan waiting-for and chase anything that has gone quiet.
  4. Look at the calendar two weeks back and three weeks forward, to catch loose ends and prep for what is coming.
  5. Skim someday/maybe and promote anything whose time has come.

The magic of the review is not organization for its own sake. It is that once a week you look your commitments in the eye. That honesty is what makes the whole system trustworthy, and trust is the only thing that keeps you using it.

Engage: actually doing the work#

All this scaffolding exists to make the moment of choosing what to do next simple. In the moment, you weigh four things almost automatically: your context (what can I even do here), your time available, your energy, and then priority. Notice priority comes last, not first. It only helps once you have narrowed to what is actually possible right now.

This is where I gently disagree with people who turn GTD into a full-blown priority-ranking religion. In real life you rarely pick the single most important task from a master list. You pick the most important thing you can do given the fifteen minutes and the mental state you have. GTD's context lists are built for exactly that, and I think that pragmatism is why it survives contact with a chaotic week.

Common ways it goes wrong#

A few honest caveats from someone who has broken this system repeatedly:

  • Over-tooling. The urge to find the perfect app is procrastination in a nice outfit. A plain-text file and a notebook will run GTD fine. Pick something boring and stop shopping.
  • Fake next actions. "Look into the thing" is not an action. If you cannot picture yourself physically doing it, clarify it further.
  • A dead someday/maybe list. If you never review it, it is a graveyard. Reviewed weekly, it is one of the most reassuring lists you own, because it proves you have not forgotten your own ambitions.
  • Treating the calendar as a to-do list. Put a non-dated task on a specific day and, when you inevitably miss it, you learn to distrust your own calendar. Guard it.

A modest starting point#

You do not need to adopt all of this at once; doing so is how people burn out on GTD by Wednesday. Start with two habits. First, capture relentlessly for a week into one or two inboxes and notice how much your head quiets down. Second, book a recurring weekly review and actually keep it, even a scrappy twenty-minute version.

Those two habits carry most of the benefit. The context lists and the project structure can grow in later, once you trust that things you capture no longer disappear. GTD in 2026 is not really about the tools, which will change again next year. It is about the promise that nothing important slips through — and that promise is still worth keeping.

Sam Whitfield
Written by
Sam Whitfield

Sam is a former operations lead who has built, broken and rebuilt more personal systems than he can count. He favours small, boring habits over grand overhauls, and tests every routine on his own messy schedule before recommending it.

More from Sam