The GTD Paradox
Getting Things Done is one of the best-selling productivity books of all time. Millions have read it. A much smaller number have successfully implemented it. And of those who have, many abandoned the system within a few months.
The paradox is that GTD is genuinely excellent. The system is logically sound, comprehensively designed, and flexible enough to work in almost any context. Yet the implementation failure rate is remarkably high. After years of observing how people approach GTD, five recurring mistakes account for the vast majority of these failures.
Mistake 1: Over-Engineering the System on Day One
The most common mistake is spending days or weeks building an elaborate GTD setup before capturing a single task. People research tools, design custom database schemas in Notion, create intricate folder hierarchies, and debate the merits of digital versus analog capture.
This is procrastination disguised as productivity. GTD works with a pen and a stack of index cards. It works with a basic notes app. It works with a spreadsheet. The tool is almost irrelevant to the outcome.
The fix is to start with the simplest possible implementation. Use a single text file or a basic to-do app. Create five lists: Inbox, Next Actions, Waiting For, Projects, and Someday/Maybe. That is it. You can optimize later, but only after you have lived inside the system for at least four weeks and discovered what actually needs improvement through experience rather than speculation.
Mistake 2: Treating the Inbox as a To-Do List
The inbox in GTD is a temporary holding area. Everything goes in, and then during a processing session, each item gets clarified and moved to its correct location. The inbox should be empty after every processing session.
Most people never empty their inbox. They capture items and then scan the list each day, doing whatever catches their eye. This defeats the entire purpose of the capture-clarify-organize workflow. The inbox becomes a sprawling, anxiety-inducing list of undifferentiated stuff, which is exactly the mental state GTD was designed to eliminate.
The fix is to process your inbox at least once per day. For each item, ask: What is this? Is it actionable? If yes, what is the next physical action? Does it take less than two minutes? If so, do it now. If not, delegate it or put it on your Next Actions list with a clear next step.
The two-minute rule is critical here. If you can do something in under two minutes, always do it immediately during processing. The overhead of capturing, storing, and retrieving a two-minute task exceeds the cost of just doing it.
Mistake 3: Writing Projects Instead of Next Actions
A project in GTD is any outcome that requires more than one action step. "Redesign the website" is a project. "Call the designer to schedule a kickoff meeting" is a next action. Most people put the project on their to-do list and then wonder why they never make progress.
The reason is psychological. When you look at "redesign the website" on a list, your brain cannot execute it because it is not a single doable step. It triggers overwhelm and avoidance. When you look at "call Sarah at the design agency," your brain knows exactly what to do. The activation energy drops to near zero.
The fix is to maintain a separate Projects list that tracks your multi-step outcomes, and ensure that every project has at least one corresponding item on your Next Actions list. During your weekly review, verify that no project is "stuck" without a defined next action. If a project does not have a clear next step, that project is stalled and needs attention.
Mistake 4: Skipping the Weekly Review
Of all five mistakes, this one is the most destructive. The weekly review is not optional. It is the engine that keeps the entire GTD system functional. Without it, lists become stale, projects go untracked, and the system gradually drifts back into chaos.
The weekly review has a specific checklist. Get clear: process all inboxes to zero. Get current: review your Next Actions, Waiting For, Projects, and calendar to ensure everything is accurate. Get creative: review your Someday/Maybe list and consider whether any items should become active projects.
Most people skip the weekly review because it feels like overhead. It takes 30 to 60 minutes and does not feel like "real work." But this view is short-sighted. The weekly review is what maintains your confidence that nothing is falling through the cracks. That confidence is what allows you to focus fully on whatever you are doing right now, because you trust that everything else is handled.
The fix is to schedule your weekly review as a recurring calendar event and treat it with the same seriousness as a meeting with your most important client. Friday afternoon works well for many people because it clears the mental deck before the weekend. But any consistent time works as long as you protect it.
Mistake 5: Ignoring Contexts in a Digital World
GTD was originally designed in an era when physical location constrained what you could work on. The @office context meant tasks you could only do at the office. @phone meant tasks requiring a phone call. @errands meant things you could only do while out of the house.
In a remote-work, always-connected world, these contexts have less meaning. Most tasks can be done from anywhere with a laptop and an internet connection. As a result, many people either abandon contexts entirely or create so many that navigating them becomes its own burden.
The fix is to redefine contexts around energy and tool requirements rather than location. @deep is for tasks requiring sustained concentration. @quick is for tasks you can knock out in a few minutes during low-energy periods. @waiting is for tasks blocked on someone else. @calls is still useful because phone calls require a different mode of engagement.
You should rarely need more than four or five contexts. If your context list is longer than that, you are over-categorizing. The goal is to quickly filter your Next Actions list to show only the tasks you can and should do right now given your current energy, time available, and tools at hand.
Building GTD That Lasts
The common thread across all five mistakes is premature complexity. People try to build the perfect system before they understand how they actually work. GTD is a practice, not an installation. Start simple, do the weekly review religiously, and let the system evolve based on what you learn about your own patterns.
If you have tried GTD before and abandoned it, consider which of these five mistakes might have contributed. Often, fixing just one of them, especially reinstating the weekly review, is enough to make the system click.
The goal is not to have a pretty productivity system. The goal is to have a clear mind that trusts its external system enough to focus completely on the task at hand. That is what GTD delivers when implemented correctly, and it is worth getting right.