I spent three years as a true believer. Dog-eared copy of the book. Custom Notion database with every GTD context tag you can imagine: @phone, @computer, @waiting-for, @someday-maybe. Weekly reviews every Sunday at 6pm, non-negotiable. I had a system that GTD practitioners on Reddit would nod approvingly at.

And then, slowly, it stopped working. Not dramatically — it didn't collapse overnight. It just quietly decayed, the way a garden does when you miss a few weeks of watering. Tasks piled up in my inbox. My "Someday/Maybe" list became a graveyard. The weekly review started feeling like a chore I was always behind on, and eventually I stopped doing it at all.

Here's the thing: I don't think GTD is a bad system. David Allen built something genuinely brilliant in 2001. But I've talked to enough people — freelancers, founders, people with ADHD, remote workers juggling multiple roles — to know that my experience isn't unusual. GTD works beautifully for a specific kind of person in a specific kind of work environment. For everyone else, it creates its own kind of overwhelm.

So let's talk about what's actually going on — why GTD breaks down for so many people, what the research and practice of modern productivity tells us about better alternatives, and what I actually use now instead.

What GTD Gets Brilliantly Right

Before I criticize it, I want to be fair. GTD's core insight is genuinely profound: your brain is for having ideas, not holding them. The cognitive load of keeping track of open loops — tasks you haven't committed to or captured properly — creates a low-level anxiety that drains your mental energy all day.

Allen called this the "psychic RAM" problem. Every uncaptured task, every vague commitment you've made to yourself, is running in the background consuming processing power. His solution — capture everything, clarify it, organize it, review it regularly — is elegant and, in principle, correct.

The other thing GTD nails is the clarification step. The question "What is the next physical action?" is one of the most useful questions in productivity. It forces vague projects like "sort out the website" into concrete actions like "email the developer to ask about the nav menu." That specificity matters enormously for actually getting things done.

So when I say GTD stopped working for me, I'm not dismissing it. I'm saying that the system has some structural assumptions baked in that don't match how a lot of us actually work today — and those mismatches are what cause it to break down.

The Problems That Nobody Talks About Honestly

GTD was designed for a pre-smartphone knowledge worker

Allen wrote the book based on his consulting work with executives in the late 1990s and early 2000s. The archetypal GTD user is someone with a physical inbox, a PA, scheduled meetings, and relatively clear separation between work and personal life.

That world barely exists anymore. Most of us are managing 4-6 different communication channels simultaneously. Messages arrive via email, Slack, WhatsApp, Instagram DMs, text messages, project management tools, and the occasional actual phone call. The idea of a single "inbox" you can fully process to zero every day is — for most people — fiction.

Context tags like @phone and @errands made sense when you were batching tasks by physical location. Now that work is largely device-agnostic and location-independent, those categories lose most of their utility. I'm always at my computer. I can always make a phone call. The contexts collapsed.

The maintenance overhead is brutal

A faithful GTD practice requires significant time just to maintain the system itself. You need to do a thorough weekly review (Allen suggests 1-2 hours), regularly process your capture tools, update project lists, prune your someday/maybe list, and ensure every open loop has a next action attached.

When life is busy — and life is usually busy — this maintenance is the first thing that slips. And here's what nobody warns you about: a partially-maintained GTD system is worse than no system at all. Because you have the illusion of control without the reality of it. You trust your lists, but your lists are stale. Tasks fall through cracks you didn't know existed.

I remember the specific moment I realized this was happening. I had 340 tasks across my various GTD lists. I'd missed two weekly reviews. I sat down to plan my day, looked at the lists, and felt more paralyzed than I would have with nothing at all. The system had become its own source of overwhelm.

It doesn't account for energy, mood, or cognitive capacity

GTD is fundamentally context-and-priority-based. You look at your @computer list, consider your energy level and available time, and pick a task. But "energy level" in the GTD framework is treated as a simple filter — high energy, pick a hard task; low energy, pick an easy one.

The actual psychology of human performance is far more complex than this. What researchers call cognitive load, ego depletion (though its replication record is mixed), and circadian rhythm effects on executive function all shape what you're actually capable of at any given moment. Some days I can write complex analytical content at 9am. Other days I'm good for nothing cognitively demanding until 11. A system that ignores this is leaving performance on the table.

More importantly, GTD has no mechanism for the emotional relationship you have with your tasks. Why do we procrastinate? Usually not because we forgot something exists — we know perfectly well that it exists. We avoid it because of fear, perfectionism, ambiguity, or low motivation. GTD surfaces the task but doesn't help you actually do it.

The "someday/maybe" list is a guilt factory

I say this with love. The someday/maybe list is where good intentions go to die. Allen's vision is that you review it regularly and occasionally promote items to active projects. In practice, most people add things to someday/maybe and never look at them again — except during the occasional anxious scroll where you feel vaguely bad about all the things you're not doing.

My someday/maybe list at its peak had 87 items. Learn Portuguese. Read the complete works of Montaigne. Start a podcast. Build a personal finance tracker. I hadn't looked at most of them in six months. The list wasn't a useful planning tool — it was a monument to optimism that mocked me every time I opened it.

What the Research Says About How We Actually Work

Since leaving GTD, I've spent a lot of time reading cognitive science and organizational psychology research — not the pop-productivity version, but the actual studies. A few findings have shaped my current approach significantly.

We overestimate what we can do in a day

This isn't new information, but the degree of overestimation is striking. Research on planning fallacy — originally described by Kahneman and Tversky — consistently shows that people underestimate task duration by 25-50% on average, even when they know about the planning fallacy. Even experts who work on similar tasks regularly still underestimate.

GTD doesn't really address this. It asks you to capture and organize tasks, but it doesn't build in a forcing function for realistic daily planning. You can have a perfectly processed GTD system and still commit to twice as much as you can actually accomplish each day.

Decision fatigue is real and it starts early

Every time you look at a task list and decide what to work on next, you're making a decision. Decision fatigue research (from Roy Baumeister's lab and others) suggests that each decision depletes a resource — willpower, executive function, whatever you want to call it — that affects subsequent decision quality.

A system that requires you to repeatedly choose from a large list of tasks throughout the day may be creating unnecessary friction at precisely the moments when you need to be doing the work, not deciding what to do.

Implementation intentions dramatically increase follow-through

This one was a revelation for me. Peter Gollwitzer's research on implementation intentions — "if-then" planning — shows that committing to when and where you'll do something (not just what) increases the likelihood you'll actually do it by a factor of two to three. "I will exercise" is far weaker than "I will exercise on Monday, Wednesday, and Friday at 7am in the park."

GTD focuses heavily on what (next actions) but very little on when. The calendar is almost treated as a sacred space for hard-landscape commitments only — Allen is quite explicit about not clogging your calendar with tasks. But the research suggests this might actually be backwards: getting tasks onto a specific time and place in your day dramatically increases execution rates.

The System I Use Now (And Why It Works Better for Me)

What I've landed on is less of a single named system and more of a set of principles drawn from several places: Cal Newport's time blocking, the Ivy Lee method, some ideas from Tiago Forte's PARA, and a healthy dose of cognitive science. It's messier than GTD to describe but cleaner to actually live with.

One capture tool, aggressively limited

I still believe in capture — Allen was right about psychic RAM. But I've ruthlessly reduced my capture surface. One app (not email, not Slack, not sticky notes). One physical notebook. That's it. Everything else is noise.

The discipline isn't about the tool — it's about the constraint. When you have one place, you have one place to check. The overhead drops to almost nothing.

Three tasks per day, max

This is the Ivy Lee method, slightly modified. Every evening, I pick three things that genuinely matter for tomorrow. Not "would be nice to do" — things that will move something important forward. I write them down in order of importance.

The next day, I work on the first one until it's done, then the second, then the third. Anything else that gets done is a bonus.

This sounds painfully simple. It is. And it works better than any complex prioritization matrix I've ever tried, because it forces a single brutal question: if I could only do three things tomorrow, what would they actually be?

Time blocking for depth work, not for everything

I block time for my most important work — usually writing or complex analysis — before anything else enters my day. Not because time blocking is a perfect system (it isn't — I've written about why time blocking keeps failing people and the fixes that actually help), but because protecting deep work time is the only reliable way I've found to ensure it actually happens.

I don't block every hour. Trying to schedule your entire day in 30-minute increments is a recipe for frustration when reality inevitably diverges from the plan. I block 2-3 anchor periods and let the rest flex.

Weekly review: 20 minutes, not two hours

I kept the weekly review but gutted it. My version takes 20 minutes maximum. I ask three questions: What actually happened last week? What needs to happen next week? What's stuck that I need to decide about?

I don't review every project. I don't update every context list. I look at my calendar for the coming week, check my project list for anything that's gone quiet, and write down the most important three things for the week.

That's it. Because a review you actually do is infinitely more valuable than a comprehensive review you skip.

Energy mapping instead of context tags

Instead of tagging tasks by context (@computer, @phone), I tag them by cognitive demand: Deep, Shallow, or Quick.

Deep work: writing, analysis, complex problem solving. Requires my best cognitive hours (morning).

Shallow work: email, admin, scheduling, returning calls. Fine for afternoon when my energy dips.

Quick: anything under 5 minutes. These I batch and do in short gaps between meetings.

This maps to how my brain actually works across a day, not to where I happen to be standing.

Where AI-Powered Planning Changes the Game

Here's something worth saying directly: a lot of what makes these principles hard to execute consistently is the ongoing cognitive work of applying them. Knowing you should protect your deep work hours is different from actually blocking them every day. Knowing you should limit yourself to three priorities is different from having the discipline to choose three and only three when you have 40 things clamouring for attention.

This is where I've found tools like DayBrain genuinely useful — not as a replacement for thinking, but as a thinking partner for the daily planning process. Instead of sitting down with a blank calendar and a task list and trying to assemble a coherent day from scratch, you can describe what you have on and what matters, and get a structured plan that accounts for your energy and constraints.

It's the difference between knowing the principles and having something that helps you apply them under the real-world pressure of a busy morning when three things have already gone sideways before 9am.

If you're managing complex schedules — particularly if you're a solo founder or running multiple projects simultaneously — that kind of adaptive planning support is hard to replicate with a static system. I wrote more about the solo founder planning challenge here, and a lot of what makes it hard is exactly this: you need a system flexible enough to survive contact with reality.

What to Do If You're In the Middle of GTD Collapse

If you're reading this and nodding because you're currently living in a half-abandoned GTD system — inbox at 400, someday/maybe list you haven't opened in weeks, project list that fills you with dread — here's what I'd actually suggest.

Don't try to fix the system. Archive it.

Seriously. Take everything in your GTD setup and move it into an archive folder. Not delete — archive. You can come back to it. But trying to "fix" a broken GTD system is like trying to renovate a house while living in it with no walls. It's too hard and it never feels done.

Start fresh. Literally open a new document or a new app and start from zero.

Do a brain dump, but set a timer

Spend 20 minutes writing down everything that's on your mind. Tasks, worries, projects, things you've promised people, things you've been avoiding. Everything. Don't organize as you go — just dump.

Then, when the timer goes off, stop. You don't need a complete list. You need enough of a list to feel like your head is lighter.

Pick your three for tomorrow

From that dump, pick three things that genuinely matter. Not three things that are urgent — urgent and important are different. Three things that will feel meaningful if you get them done. Write them down somewhere you'll see them in the morning.

That's your new system for now. You can make it more sophisticated later. But right now, you need wins, not architecture.

The Question Nobody Asks About Productivity Systems

There's a question that rarely gets asked in productivity circles because it's a little uncomfortable: what is this system actually for?

For many people — and I was absolutely guilty of this during my GTD years — the system becomes the goal. A perfectly maintained GTD setup is the prize. Getting things done is almost secondary to the satisfaction of having everything captured and organized and reviewed.

This is productivity cosplay. It feels productive without necessarily being productive.

The uncomfortable truth is that no system — not GTD, not time blocking, not any app or methodology — can substitute for clarity about what you're actually trying to accomplish and why. A system is just scaffolding. If the building is unclear, better scaffolding doesn't help.

This matters especially if you have ADHD or executive function challenges. The failure mode for ADHD and planning systems is almost always the same: the system becomes too rigid or too complex to maintain, and then the whole thing gets abandoned in a wave of shame and frustration. The answer isn't a better system — it's a simpler one, with more built-in flexibility and fewer moving parts.

What I'd Tell My GTD-Obsessed Past Self

If I could go back and have a conversation with myself during those three years of faithful GTD practice, here's what I'd say.

The capture habit is worth keeping. The next-action question is worth keeping. The idea that your brain needs external systems to function well — that's absolutely worth keeping.

But stop trying to maintain a perfect system. Stop treating the weekly review as a sacred obligation that, when missed, means the whole thing has failed. Stop collecting productivity methodologies the way some people collect cookbooks — owning them as a substitute for actually cooking.

Work is not a puzzle to be optimized. It's a series of messy, human, often unpredictable days that you're trying to navigate with as much clarity and energy as you can muster. A system that helps you do that — even imperfectly, even roughly — is worth a thousand elegant systems that collapse under real-world pressure.

The goal isn't a perfect GTD setup. The goal is to do meaningful work and not feel destroyed at the end of the day. Keep your eye on that.

The Practical Takeaways (Because I Know You Want a List)

If you've read this far, here's a condensed version of what I've actually changed:

None of this is revolutionary. Most of it is common sense that's surprisingly hard to actually practice. But it's held up for me over the past couple of years in a way that GTD — for all its elegance — never quite did.

If you're looking for a tool that actually applies these principles in a practical, day-to-day way rather than just theorizing about them, DayBrain is worth a look. It's built around the idea that planning should adapt to how your day actually unfolds — not lock you into a structure that starts breaking the moment reality shows up.

And if you're curious about how different approaches stack up in practice — GTD, time blocking, app-based planning — the honest roundup of daily planning apps we put together is a good place to see how the tools actually compare in real-world use.

The system isn't the point. Getting the things done that matter is the point. Don't lose sight of that.