For a long time I thought I had to choose between GTD and PARA. They showed up on the same lists, with fans arguing one against the other, like two tools that do the same job.
They do not. It took me a while to see it because I was asking the wrong question. I was asking which one was better. The useful question is: better at what?
Once you ask that, the argument disappears. What is left is a smaller and more interesting choice.
The difference in one sentence
GTD organises what you have to do. PARA organises what you know.
That sounds minor. It is not. GTD deals in commitments: a call, a report, a bill. Its unit is the physical next action. PARA deals in material: the meeting note, the contract PDF, the draft you wrote six months ago. Its unit is the file.
A commitment has a moment when it has to happen. Material does not; it has a moment when it will be useful, and that moment may never come. That is why an action system has to find you, and a material system only has to be there when you look.
Relatives, not competitors
This is where it gets interesting. GTD, published by David Allen in 2001, already had a drawer for things that are not actions. In the method's workflow, an item that asks nothing of you but might be consulted later goes to Reference, a file that, in Heylighen and Vidal's description, is organised so things are easy to classify and retrieve.
It was a drawer, not a system. GTD spends nearly all its engineering on the path of actions and leaves reference as a supporting act.
Tiago Forte pointed at exactly this in a 2017 essay on GTD and personal knowledge management. In the GTD diagram, he wrote, actionable information flows down the central spine and is clearly the priority; non-actionable information gets diverted to the sides. He quotes Allen himself, in the revised 2015 edition, saying the reference file is, for most of the executives he coached, one of the biggest opportunities for improvement.
PARA was born in that gap. Forte introduced it on his blog around the same time and later built it into Building a Second Brain, in 2022. Even the vocabulary is shared: "project" and "area" were part of GTD long before they became folders.
So the honest reading is this: PARA is not the modern version of GTD. It is GTD's reference drawer taken seriously.
Ask what you lost last time
If the two solve different problems, choosing means working out which problem is yours. The quickest way I have found is to look back, not forward.
Think of the last time your organisation actually failed. Not a vague unease: an incident.
If it was a missed deadline, a reply you forgot to send, a bill that went overdue, what failed was a commitment. You were missing GTD, or something doing its job.
If it was rebuilding a presentation because you could not find the old one, losing twenty minutes hunting for a note, or discovering you had already researched this back in March, what failed was material. You were missing PARA.
Most people I know discover their problem is the first one and then build the second. It makes sense: tidying folders is pleasant and it ends. Keeping commitments is dull and never does.
What the evidence supports, and what it does not
Neither has a controlled study showing that it works. Heylighen and Vidal's paper, the most cited on GTD, is a theoretical analysis: it shows the method fits what we know about distributed cognition, the idea that we use our surroundings as an extension of memory. They also note that GTD starts from the bottom, with concrete issues, rather than from the top, with abstract goals. Fitting a theory is not a test. On PARA I found no study at all; the public evidence is testimonials from students of the author's own courses.
What does exist is neighbouring research on how people use what they save. Bergman, Whittaker and Schooler asked 50 people to find web pages again, including pages they had bookmarked themselves. Of the 250 bookmarked targets, only 41 were found through the bookmark, or 16%. Only 9, 4%, through the folder hierarchy; the rest sat in the browser's visible toolbar. Unless a bookmark was highly visible, the authors conclude, people simply did not use it.
That does not sink PARA, but it applies to both systems: saving does not guarantee use, and what is out of sight tends not to exist.
How to choose
Side by side
| GTD | PARA | |
|---|---|---|
| Question it answers | What do I do now? | Where is what I already know? |
| Unit | Physical next action | Note or file |
| How it fails | You forget to do it | You cannot find it, or redo it |
| Costly part to maintain | Capture and review | Sorting and archiving |
| Evidence | Theoretical analysis, no controlled test | No published study |
You can use both, with one seam
The joint is the project. When a project starts, it goes on the GTD list with a next action and gets a folder in PARA. When it ends, it leaves the list and the folder goes to Archive. One gesture, in both places.
The honest limit: two systems cost more than one, and the part most people abandon (upkeep) does not get cheaper by being split. If only one is going to survive, make it the one that handles what you have to do. Lost material costs time. A lost commitment costs trust.
Why this matters for what I built
I have had both at once: immaculate folders and leaking commitments. It took me a while to see they were two problems, and that the second one is not solved by more organising, because a commitment only works if something finds you when it is due.
ASB sits on that side. It does not tidy your folders; it takes what you have to do in a sentence, on WhatsApp, and comes back to ask when the time comes.