Getting Things Done (GTD): A Beginner's Guide to David Allen's Method

GTD's foundation is a single observation: your brain is good at generating thoughts and bad at storing them. Every open loop you try to remember — a task, an errand, an idea — takes up mental bandwidth and tends to resurface at the worst possible moment. Allen's solution is to move all of it out of your head into an external system you genuinely trust, so your mind is free to focus on the work in front of it.

This isn't just a productivity slogan. A 2008 peer-reviewed analysis in the journal Long Range Planning by Francis Heylighen and Clément Vidal argued that GTD aligns with the cognitive-science idea of distributed cognition — the principle that the brain offloads work onto the environment, using external tools as a kind of extended memory. Writing things down isn't a crutch; it's how thinking is supposed to work.

Allen describes the goal state with a martial-arts metaphor, mind like water: a mind that responds proportionately to what comes in and then returns to calm, rather than churning over everything at once.

GTD is a workflow with five stages. In the current edition of the method, Allen's organization names them as follows:

The single most quoted piece of GTD is the two-minute rule, and it lives inside the Clarify step. The rule: while you're processing your inbox, if an action will take less than two minutes, do it immediately rather than recording it for later.

The logic is purely practical. Capturing a tiny task, organizing it onto a list, and coming back to it later costs more total effort than the two minutes the task itself takes. Below that threshold, tracking is more expensive than doing. Above it, the task goes onto a list where it belongs. It's a small rule, but applied consistently it stops dozens of trivial loose ends from piling into a backlog.

A capture system you don't trust is worse than no system, because you'll keep using your head as a backup. What earns that trust is the weekly review — a recurring habit, part of the Reflect step, of going through your lists, clearing your inboxes, checking your calendar and projects, and getting your head empty again.

Without it, lists go stale, you stop believing they're complete, and the whole thing quietly collapses back into mental clutter. With it, you can genuinely let go of remembering, because you know everything will be surfaced and updated on a reliable cadence. If you adopt only two things from GTD, make them the capture habit and the weekly review — they carry most of the benefit.

GTD has a reputation for being heavy, and a full implementation — contexts, project lists, tickler files — can be. You don't need all of it to get most of the value. Start light.

Do one big capture: spend half an hour writing down absolutely everything on your mind, in one list, no organizing. That brain-dump alone is often a relief. Then practice just two habits for a couple of weeks — capture new things as they arise instead of trusting your memory, and apply the two-minute rule when you process. Add a short weekly review once those feel natural. The contexts and elaborate lists can come later, if you ever want them.

Treat GTD as a toolkit, not a test you can fail. The aim is a clear head and a trusted list, and you can reach that with a fraction of the full system.

GTD begins with Capture and leans on a trusted place to keep reference material — the documents, notes, and sources you'll need to look up later but don't want cluttering your mind. A note app is a natural home for that layer, and PocketNote keeps your notes and source documents together in one searchable space, so 'where did I put that?' stops being a question you have to answer from memory.

It isn't a task manager, and GTD's lists and calendar live wherever you keep them. But when the work a task points to is studying or understanding your material, PocketNote earns its place: source-grounded chat and auto-generated flashcards and quizzes turn the reference pile you captured into something you can actually act on.