Why I Quit Getting Things Done (And What I Do Instead)
by admin in Productivity & Tools 24 - Last Update December 2, 2025
I have a confession to make. For years, I felt like a failure because I couldn\'t make the Getting Things Done (GTD) method work for me. I read the book, I bought the special folders, I set up the digital apps. On paper, it was the perfect system for a brain like mine that juggles dozens of ideas at once. But in practice, it was a disaster.
Honestly, I spent more time managing my GTD system than I did actually, well, getting things done. The weekly review became a multi-hour chore I dreaded. The intricate web of contexts and projects felt less like a trusted system and more like a second job. I was supposed to feel \'mind like water,\' but instead, I just felt a constant, low-grade anxiety that I was doing it wrong.
Why GTD didn\'t work for me
After several failed attempts over the years, I took some time to reflect on why this celebrated method just didn\'t click. I realized it came down to a few core issues that were personal to my workflow and mindset.
The friction of over-organization
The core of my problem was cognitive overhead. The process of capturing, clarifying, organizing, reflecting, and engaging for every single thought, email, or minor task was exhausting. My \'inbox\' was overflowing, and the effort required to process it all to zero felt monumental. I found myself procrastinating on my productivity system, which is a truly special kind of irony.
The context system is outdated for modern work
When the method was created, having a context like \'@phone\' or \'@office\' made sense. Today, my \'@computer\' context is... everything. My work, communication, and planning all happen on the same device. The lines are so blurred that separating tasks by these old-school contexts felt arbitrary and added a layer of complexity that provided almost no value for me.
The simple system that finally clicked
So, I quit. I deleted the complicated app setups and put the book back on the shelf. I decided to build something from scratch, based on what I learned from my failure. My goal was radical simplicity. What I ended up with isn\'t a branded methodology, but it\'s a fluid system that works for my brain.
1. The \'three buckets\' method
I abandoned dozens of project lists and complex tagging. Now, I operate with just three primary lists, or \'buckets\': Now, Next, and Later.
- Now: A tiny list of 1-3 things I am absolutely committed to doing today. No exceptions.
- Next: A slightly longer list of things that need to be done this week. This is my pool for tomorrow\'s \'Now\' list.
- Later: Everything else. Big ideas, \'someday/maybe\' projects, things I\'m waiting on. I only look at this list during my weekly reset.
2. A weekly reset, not a review
The formal GTD weekly review felt like an audit. My \'Weekly Reset\' is a 15-minute coffee session on Friday afternoons. I don\'t follow a strict checklist. I simply look at my \'Next\' and \'Later\' buckets and ask myself: \'What feels important for next week?\' I drag a few items into the \'Next\' bucket, delete things that are no longer relevant, and that\'s it. It’s a gentle course correction, not a rigid inspection.
3. Action over perfection
My biggest takeaway was that I was using the system as an excuse to avoid the actual work. Now, if a task takes less than five minutes, I just do it. I don\'t capture it, I don\'t tag it, I don\'t file it. I\'ve come to believe that the friction of processing a tiny task is often greater than the effort of simply completing it. It\'s liberating.
It’s about principles, not dogma
I still think the core principles of GTD are brilliant. Getting ideas out of your head is crucial. Having a system you trust is paramount. But I learned that you have to separate the principles from the prescription. For me, the rigid, all-encompassing structure of GTD was the problem, not the philosophy behind it. My simple system works because it\'s mine—it\'s just enough structure to keep me on track, but not so much that it gets in the way.