I've used GTD for seven years. I've read the book three times. I've built elaborate systems in OmniFocus, Things, Notion, and paper. And like clockwork, every 3-4 months, the whole thing collapses.
Not because I forget to capture. Not because I stop doing weekly reviews. It collapses because my lists become so long that looking at them induces the same overwhelm I was trying to escape.
This isn't a personal failing. It's a structural flaw in how we think about productivity.
The GTD Promise
David Allen's core insight is profound: your brain is for having ideas, not holding them. Capture everything. Process it into actionable next steps. Review regularly. Your mind becomes "like water" - clear and responsive.
It works. Until it doesn't.
The problem isn't the methodology. The problem is that GTD has no native concept of cognitive load. It treats all captured items as equal citizens, when in reality, different items impose vastly different cognitive costs.
The Hidden Variable: Decision Load
Consider two items on your Next Actions list:
- "Call Mom" - Simple. You know what this means. Minimal cognitive overhead.
- "Figure out Q2 hiring plan" - Complex. Requires research, stakeholder alignment, budget analysis, and multiple sub-decisions. Massive cognitive overhead.
GTD would have you process both into "next actions." But even after processing, the second item carries residual decision load - ongoing cognitive weight that doesn't disappear just because you wrote it down.
Now multiply this by 200 items across 15 projects. Your "trusted system" has become an anxiety-inducing inventory of everything demanding your future attention.
Why Weekly Reviews Stop Working
The weekly review is supposed to keep things current. But here's what actually happens when decision load gets high:
- You open your system and feel a wave of dread
- You skim rather than engage (because engaging is exhausting)
- You "review" by scrolling, not by truly re-deciding
- Stale items accumulate, increasing future review burden
- Eventually you avoid reviews entirely
- System collapses. Start over.
This cycle isn't about discipline. It's about unmeasured cognitive load exceeding your processing capacity.
What GTD Gets Right
Let's be fair: GTD remains one of the most influential productivity frameworks ever created. Its core insights are valid:
- Capture reduces cognitive leakage
- Next actions reduce ambiguity
- Contexts reduce friction
- Projects need outcomes defined
- Regular review prevents drift
These principles are sound. The issue isn't the framework - it's the missing metric for how much you're carrying.
The Missing Metric
What if you could see, objectively, when your decision load was reaching unsustainable levels?
Not a vague feeling of overwhelm. Not "I have too many projects." But an actual number that synthesizes:
- Open loops without clear next actions
- Unprocessed inputs awaiting decisions
- Ambiguous items requiring clarification
- Overdue commitments creating background pressure
- Active project count
This is what Decision Load Index (DLI) attempts to provide. Not a replacement for GTD, but a companion metric that tells you when your system is approaching overload.
A Different Approach
Instead of asking "what's the next action?" for every item, consider asking:
"What is my current decision load, and can I sustainably process what I'm carrying?"
If your decision load is high:
- Stop capturing new commitments temporarily
- Focus on closing loops, not opening them
- Defer, delegate, or delete items more aggressively
- Simplify contexts to reduce decision points
If your decision load is low:
- You have capacity for new projects
- Weekly reviews will feel manageable
- Your system is working as intended
The key insight: decision load is a leading indicator. It tells you your system is approaching failure before the collapse happens.
Why This Isn't About Tools
I've switched task managers a dozen times thinking the tool was the problem. OmniFocus was too complex. Things was too simple. Notion was too flexible. Paper was too unstructured.
None of these were the problem. The problem was invisible decision load accumulating regardless of which tool held it.
The solution isn't a better app. It's awareness of the variable we weren't measuring.
A Reflection
If your productivity system has collapsed before - and if you're reading this, it probably has - consider that the failure wasn't about discipline or tools.
It may have been decision load exceeding your capacity to process. And if you couldn't see it, you couldn't manage it.
What would change if you could?