Getting Things Done (GTD) in 2026: What Still Works, What Doesn't

David Allen’s Getting Things Done turned twenty-five in 2026. The book has sold over 3 million copies. Its terminology — next action, capture, inbox, contexts, weekly review — is now embedded in the language of personal productivity. Almost every modern productivity tool inherits assumptions from GTD whether the founders read the book or not.

But the world has changed a lot since 2001. Knowledge work has been reshaped by Slack, by smartphones, by remote distribution, by AI. The GTD method survives where it should, struggles where the world has moved past it, and gets quietly replaced in places where better solutions now exist.

This article is the honest 2026 review. We’ll cover what GTD got right and still holds, what it gets wrong by today’s standards, what it left unanswered, and how to assemble a modern workflow that takes the best of GTD and adds the pieces it doesn’t have.

If you’ve tried GTD and bounced off, this is the piece that says it isn’t your fault — and points at the structural gaps.

What GTD got right (and still right)

Several core ideas in GTD remain correct twenty-five years later.

Capture everything. The single most enduring GTD principle. Anything that’s pulling at your attention should be written down in a trusted system, so the brain can stop holding it. The cognitive load reduction is real and the research (see What is a brain dump?) supports it.

Process to a clean state. GTD’s emphasis on emptying inboxes regularly — not for the aesthetic but to keep the system trustworthy — is correct. A system you don’t trust is worse than no system.

Define the next action. GTD’s insistence on defining the next physical action for each project is one of the book’s most useful contributions. Vague task descriptions (plan birthday party) don’t ship. Specific next actions (text venue to confirm date) do. This idea predates GTD but Allen made it canonical.

Weekly review. The single non-negotiable maintenance ritual in GTD. We agree completely; the version we recommend (see How to run a weekly review in 25 minutes) is structurally similar.

Contexts. GTD’s idea of contexts — sorting tasks by where they can be done (@home, @phone, @errands) — was brilliant for the early 2000s where mobility constraints structured what you could do when. It’s less load-bearing in 2026 because most knowledge work happens on the same laptop in the same place, but the underlying idea (tasks have prerequisites; surface them when you can act) is still right.

These are real contributions. The book is still worth reading.

What GTD struggles with in 2026

Three areas where the world has moved past the book.

Volume. Allen’s 2001 examples imagine an executive processing maybe two hundred items a week. Modern knowledge workers process closer to two thousand — Slack messages, emails, notifications, tasks, automated alerts, calendar invitations. The GTD ritual of clarify, organize, reflect on every item is structurally impossible at this volume without AI assistance.

The fix: aggressive AI-assisted triage. Most modern operators we know who run a GTD-influenced workflow use AI to compress the clarify step from minutes to seconds — see How CEOs use AI to save 10 hours a week.

Hierarchy. GTD’s hierarchy is flat. Tasks belong to projects; projects belong to areas of focus and higher horizons (3-5 year vision, life purpose). The horizons are aspirational, not operational. There’s no concrete connection between today’s next action and tomorrow’s life goal.

The fix: replace GTD’s horizons with the four-layer hierarchy (life goals → objectives → problems → tasks) we cover in How to streamline your life goals. The four-layer hierarchy is more operational — every task is traceable up to a life goal, and AI ranking can use the trace as the prioritization axis.

Prioritization. This is GTD’s biggest gap. The book is explicit that GTD doesn’t prioritize — you use intuition in the moment to pick the next action from the context. In 2001, with smaller task volumes, intuition was good enough. In 2026, with much larger volumes and more competing demands, intuition systematically underperforms structured ranking. Operators end up doing whatever’s loudest, not whatever matters most.

The fix: AI prioritization layered on top of GTD’s capture and processing. The model ranks tasks against your active objectives; the human reviews and overrides. See AI task prioritization explained.

What GTD doesn’t address

Two things the book is silent on that working operators need.

Decision-making about strategic direction. GTD is excellent at execution and weak on direction. The what should I be working on question is largely handed off to higher horizons, which are too abstract to operationalize daily. Operators following GTD strictly tend to ship a lot — but sometimes ship in the wrong direction because the strategic layer is underdeveloped.

The fix: the personal OKR framework (see The personal OKR framework) sits above GTD and provides the strategic anchor.

Energy and emotional regulation. GTD treats tasks as cognitively interchangeable — a task is a task. In practice, tasks have very different emotional and energetic loads, and pretending they don’t produces a recognizable failure mode: you ship the easy stuff and procrastinate on the heavy stuff, even though the heavy stuff is where the leverage is.

The fix: the procrastination science (see How to stop procrastinating) sits next to GTD and addresses the emotional layer the book doesn’t.

The modern GTD-influenced workflow

A workflow that takes the best of GTD and adds the missing pieces.

Layer 1: Capture (GTD-pure). Anything that pulls at your attention goes into the planning surface, immediately. The capture inbox is the trust foundation; without it, the brain holds inventory and gets exhausted.

Layer 2: Process with AI assistance. Open the inbox once a day. Run AI-assisted extraction — see From brain dump to backlog. The AI surfaces the structure; you review and edit. Process time drops from thirty minutes to ten.

Layer 3: Route to the four-layer hierarchy. Each item routes to life goal → objective → problem → task, or to the someday list. The hierarchy provides the strategic anchor GTD’s horizons don’t.

Layer 4: AI-rank against objectives. The Today view shows tasks ranked by impact on active objectives. This is the prioritization layer GTD lacks.

Layer 5: Execute via deep work + Pomodoro. Morning deep-work block on the top-ranked task; Pomodoro for resistible afternoon work. The focus methods sit on top of the prioritization. See Pomodoro vs Deep Work vs Time Boxing.

Layer 6: Weekly review. GTD-style weekly review on Sunday or Monday morning. Touches the hierarchy, sets the week’s three outcomes, calendars the deep-work blocks. See How to run a weekly review in 25 minutes.

This is what GTD looks like rebuilt for the 2026 stack. The bones are familiar; the layers above and the AI assistance are the additions.

A common question: do I still need contexts?

GTD’s contexts (@home, @phone, @errands) were peak-useful in 2003. In 2026, knowledge work has converged onto roughly two contexts: anywhere with a laptop and anywhere without one. Most operators don’t need granular contexts anymore.

The exception: parents and operators with structurally split locations (office, lab, field site). For these operators, contexts still help.

The structural replacement for contexts is time-of-day energy. Tasks with high cognitive load go to the morning deep-work block; tasks with low cognitive load go to the afternoon. Energy-of-day is the new context.

A common pitfall: GTD as theater

The most common GTD failure pattern is the same as the Eisenhower Matrix’s — the system gets set up elaborately and then never gets used after week three.

The signs: a beautifully configured planning tool that gets opened on Sundays for the review and never on Tuesdays. An inbox that’s empty after the Sunday processing and overflowing by Wednesday. A next-actions list that never gets touched between weekly reviews.

The fix is operational, not structural. The system has to be opened daily — ideally as part of the morning ritual and the evening shutdown — or the trust erodes and the system collapses. GTD without the daily check is a Sunday hobby, not a productivity method.

For the daily structure, see How to organize your day for maximum output.

What modern tools change

Three structural changes between 2001 and 2026 that the book couldn’t have anticipated.

Cloud sync. GTD in 2001 assumed paper inboxes and folders; the digital versions were imperfect and fragile. In 2026, every modern tool syncs across devices in real time. The trusted system is now genuinely trusted in a way it wasn’t.

AI extraction and ranking. The clarify/organize/reflect cycle in GTD is the most time-expensive part. Modern AI compresses both clarify (what is this thing) and the ranking step (which tasks matter most) by an order of magnitude. The full GTD cycle that took an hour in 2003 takes fifteen minutes in 2026 with AI.

Voice capture. Most modern operators capture half their tasks by voice — into Apple Notes, into Siri, into a dedicated voice-first tool. The activation cost of capture has dropped to near-zero, which is exactly what GTD wanted.

These changes make GTD’s core ideas easier to live by. They don’t change the underlying logic.

Should you read the book in 2026?

If you’ve never read it, yes. Read the first hundred pages. Skip the technology recommendations (they’re dated). Take the central principles — capture, process, define next action, weekly review — and integrate them into whatever modern stack you use.

If you’ve read it before, skim the chapter on the weekly review (it remains the canonical version) and move on. The book’s value-per-page drops sharply in the second half, where it gets into specific filing systems most people won’t use.

A second book worth reading: Tiago Forte’s Building a Second Brain, which addresses the knowledge management side that GTD treats lightly. See also What is a personal OS for the framing we’d use to combine the two.

How braindump.work integrates GTD

braindump.work follows GTD’s capture/process/review structure and adds the hierarchy and AI ranking GTD lacks. The capture inbox is the brain-dump surface. Processing happens with AI extraction. Routing into the hierarchy replaces GTD’s horizons. AI ranking against objectives replaces intuition-based next-action selection. The weekly review is built in.

For GTD practitioners migrating from another tool, the workflow feels familiar — same bones — with the strategic layer that the original framework left as homework.

A note on the GTD purist trap

A specific failure mode worth naming. Some operators read Getting Things Done and treat it as a complete system that shouldn’t be modified. The purist’s GTD attempts to follow every recommendation: filing cabinets, tickler files, weekly horizon reviews up through 50,000 feet.

In 2026, the purist version is impractical for most working operators. The volume of inbound, the speed of work, the disappearance of paper-based reference material — all of these mean the purist GTD takes 8-10 hours a week to maintain. The maintenance cost exceeds the benefit.

The honest version is the adapted one: keep the capture, the next-action discipline, the weekly review; drop the elaborate filing and the higher-horizon rituals; layer AI assistance on top. The result is GTD’s core insights running at 30% of the maintenance cost.

TL;DR

GTD’s enduring contributions: capture everything, define next actions, weekly review. Its 2026 weaknesses: no hierarchy above areas of focus, no prioritization, no AI-scale processing. The modern adaptation: capture (GTD-pure) → AI extraction → four-layer hierarchy → AI ranking → deep-work execution → weekly review.

The book remains worth reading. The system needs the additions. braindump.work integrates the adapted workflow — free during early access.