In the late 1980s, in a small office in Ojai, California, a former karate teacher and Episcopalian seminary dropout named David Allen began consulting with executives at corporations like Lockheed and Ford. He had wandered, by the unusually circuitous route that is sometimes the path of people who eventually invent things, through training programs in personal development, organisational psychology, and a brief and somewhat surprising stint as a martial-arts instructor for at-risk youth. He had also, more importantly for what would follow, spent years quietly observing what the people he worked with actually did with their time, and what they did not do, and what the gap between the two was costing them. The observation that eventually crystallised into the system he would call Getting Things Done was simple enough that, when he first articulated it, it sounded almost too obvious to be useful.
The observation was this: the human brain is a terrible storage device, and almost everyone is using it as one. People were carrying around hundreds of small unfinished commitments — things they had agreed to do, things they were worried about, things they meant to remember — and the act of carrying these commitments was consuming the cognitive bandwidth that the same brains needed for the work itself. The more commitments a person held in working memory, the worse she performed on whatever she was actually trying to focus on. The brain, asked to hold and execute simultaneously, did neither well. Allen’s solution, which he developed and refined over the next decade and a half before publishing it in 2001 in a slim and almost defiantly unpoetic book titled simply Getting Things Done, was to externalise all of those open commitments into a system the brain could trust — and then to free the brain to do what it was actually good at, which was thinking.
The book became one of the most quietly influential productivity texts of the new century. It was not a bestseller in the dramatic, week-on-the-list sense. It was something stranger: a slow, steady cult title that built its audience over years through word of mouth among engineers, consultants, academics, designers, and the small population of people whose work consisted mostly of managing complexity. The acronym GTD, drawn from the title, became a kind of shibboleth in certain corners of the professional world. People asked each other whether they were “doing GTD” the way an earlier generation might have asked whether they were getting enough sleep. The system, despite its forbidding completeness — Allen’s book runs over three hundred pages and includes diagrams that look like they were drawn for a NASA mission briefing — became something close to a standard reference for the kind of person who took the management of their own attention seriously.
What follows is an attempt at the practical breakdown the original book never quite offered: a beginner’s guide to what GTD actually is, why it works when it works, and how to use it without disappearing into the considerable complexity Allen built around the underlying ideas.
The Insight Underneath the System
To understand GTD as a beginner, it helps to start with the insight rather than the procedures. The insight, which has been confirmed many times over by subsequent cognitive science, is that the brain’s working memory is small, expensive, and easily clogged. The smallness was first quantified by the psychologist George Miller in 1956, who proposed that the average mind could hold roughly seven items in active awareness at once. Subsequent research has revised the number downward — the current estimate is closer to four — but the principle has held up. Working memory is finite. When it is full, performance on whatever task occupies it drops sharply.
The expense of working memory is less obvious. Each item the brain is holding consumes a slot, and each slot consumed is a slot unavailable for thinking. The unfinished email you have been meaning to write occupies a slot. The vague worry about a project deadline occupies a slot. The idea you had in the shower three days ago and have not yet written down occupies a slot. None of these things, individually, feels like much. Cumulatively, they fill the working memory ceiling long before the day has actually begun. The professional sitting down to write a strategic memo at 9 AM may have only one or two slots available — the rest are taken — and those one or two slots are insufficient for the work the memo actually requires.
Allen’s contribution was to recognise that this was not an attention problem in the usual sense. It was a storage problem. The brain was being asked to do two things at once — store commitments and process work — and was failing at both. The fix was not to try harder. The fix was to give the storage function to a different system entirely, a trustworthy external system that could hold the commitments faithfully so that the brain did not have to. The system would do the remembering. The brain would do the thinking. The two functions, separated, would each perform much better than they had when crammed into the same overloaded cognitive container.
The Five Steps, in Plain Language
The architecture of GTD consists of five steps that, performed in sequence, get every commitment out of the head and into a system the head can trust. Allen named them, with characteristic dryness, Capture, Clarify, Organize, Reflect, and Engage. The names sound corporate. The actions they describe are mundane and almost embarrassing in their simplicity. They are also, when performed faithfully, transformative in a way that few productivity practices have ever managed to be.
Capture is the first step, and it is the foundation on which the rest of the system depends. The instruction is to write down — immediately, without filtering, without evaluating — every commitment, idea, worry, task, errand, and obligation that surfaces in your awareness. The medium does not matter. A notebook works. A note-taking app works. A dictation tool works. The only requirement is that the capture be reliable: that the thing, once captured, will not be lost. The purpose of capture is not to make a list of tasks. The purpose is to assure the brain that nothing is being held in working memory anymore — that whatever surfaces will be safely stored elsewhere, available when needed but not consuming a cognitive slot in the meantime. The first time most people do this honestly, they discover that they have been carrying around between fifty and two hundred open commitments at any given moment. The discovery is itself a relief, and the relief is the first sign that the system is doing what it claims to do.
Clarify is the second step, and it is where most beginners falter. The instruction is to take each captured item and decide, in turn, what it actually means. Is it actionable? If yes, what is the very next physical action required to move it forward? If not, is it reference material to file, an idea to incubate, or something to simply discard? The clarification step turns vague worries into concrete decisions. “Mom’s birthday” is not a clarified item. “Buy a card and write a message by Friday” is. “Project review” is not clarified. “Email Sarah to schedule a meeting” is. The clarification forces the worker to confront items that have been floating in her head precisely because she has not yet done the small mental work of figuring out what to do about them. Once they are clarified, they can be acted upon. Until they are clarified, they cannot.
Organize is the third step, and it is the easiest of the five for people who like organisational systems and the hardest for people who do not. The instruction is to put each clarified item into the appropriate place: tasks with specific deadlines onto a calendar, tasks without deadlines onto a list sorted by context (errands, calls, computer work, and so on), reference material into files where it can be retrieved, projects into a separate list where their multiple action steps can be tracked. The organising system is meant to be exhaustive — every clarified item should have a definite place to live — but it is not meant to be elaborate. Allen’s recommendation, which has held up over twenty years of practice, is to keep the system as simple as possible while still being complete. Complexity introduced for its own sake usually collapses under its own weight within a few months.
Reflect is the fourth step, and it is the one most people skip — which is a shame, because it is the step that keeps the system honest. The instruction is to review the entire system on a regular basis, usually weekly, in a session Allen called the Weekly Review. The review involves looking at every list, every project, every commitment, and asking whether it is still current, whether it has moved forward, whether it should be deleted, deferred, or escalated. The Weekly Review takes between thirty minutes and two hours, depending on how complex one’s life happens to be. It is the maintenance task that prevents the system from drifting into a state where the brain no longer trusts it — and once trust is lost, the whole system collapses, because the brain starts holding commitments again as a hedge against the possibility that the external system has dropped them. Without the review, GTD slowly stops working. With the review, it can run for years.
Engage is the fifth step, and it is the step at which the system finally produces results. The instruction is to actually do the work — to choose, in any given moment, the next action that best matches your current context, energy, and available time. Allen called this the “four criteria” for choosing actions: context, time available, energy available, and priority. The system, having captured and clarified and organised everything, now permits the worker to look at her lists and see, immediately, what she could be doing right now — without the cognitive overhead of trying to remember what she had committed to or what mattered most. The choice becomes clear because the alternatives have been laid out in advance.
"The point of writing everything down is not to remember it. The point is to give your brain permission to forget."
Why the Brain Loves a System It Can Trust
The reason GTD works, when it works, is almost entirely psychological. The brain, once it believes that an external system is reliably holding its commitments, releases the working-memory slots those commitments had occupied. The release is not metaphorical. It is measurable. People who have practised GTD for several months consistently report a reduction in the background hum of mental noise — the low-grade anxiety that comes from suspecting one has forgotten something but not knowing what it is. The reduction is the brain trusting the system and stepping out of the storage role it was never well suited for.
A 2016 study published in the journal Acta Psychologica tested a related hypothesis: that participants who externalised their open commitments to a written list performed better on subsequent cognitive tasks than participants who tried to keep the commitments in memory. The results confirmed what GTD practitioners had been saying for years. The externalised group not only performed better — they also reported lower stress and rated their own focus as significantly clearer. The act of writing the commitment down was, in some sense, the entire intervention. The writing was not a tool for remembering. It was a tool for forgetting, in the specific cognitive sense of releasing the working-memory slot.
This is the part of GTD that distinguishes it from the simpler productivity practices it superficially resembles. A to-do list is not GTD. A to-do list is a record of obligations. GTD is a system for managing the relationship between obligations and the brain that has to execute them — a system whose success depends not just on what is written down but on the trust the brain develops over time that the writing-down is comprehensive. The trust takes weeks or months to build. Until it is built, the brain continues to hedge, holding commitments in memory as a backup. Once it is built, the holding stops, and the cognitive bandwidth that had been consumed by storage becomes available for thinking.
What the Beginner Should Actually Do
Because GTD is a complete system rather than a single technique, it has a steep initial learning curve. Most people who try it get overwhelmed in the first few weeks and abandon it before the trust has had time to develop. This is the most common failure mode, and it is largely preventable. The trick is to begin smaller than the book suggests.
The minimum viable GTD setup is this. First, do a single capture session — sit down for an hour and write down every open commitment you can think of, without filtering. The list will be longer than you expected. That is normal. Second, go through the list and clarify each item by writing the very next physical action required. Third, sort the items into two simple buckets: things with specific dates (which go on a calendar) and things without (which go on a single list). Fourth, do this much consistently for two weeks. Fifth, after two weeks, schedule a thirty-minute Weekly Review and look at everything you have captured. If the system is helping, expand it gradually — add context lists, add a separate projects list, add the more elaborate features Allen recommends. If it is not helping, simplify until it is.
The mistake most beginners make is to try to implement the entire system on day one. Allen’s book is comprehensive, and the comprehensiveness makes it look like the system requires all of its components from the start. It does not. The two essential components are capture and reflect — the disciplined writing-down of open commitments and the regular reviewing of what has been written down. Almost everything else can be added later, once the basic habits have taken hold.
Try this: Set aside one uninterrupted hour this week. Sit down with a blank sheet of paper or an empty note. Write down every open commitment, worry, task, idea, errand, and obligation that surfaces in your mind. Do not filter. Do not organise yet. Just write. When you stop, count the items. Whatever the number is, it is the number of things your brain has been carrying around as background load. Most people find the number startling. That number is what GTD is trying to release.
The Limits of the Method
GTD has limits, and any honest account should name them. The first is that the system is more complex than it needs to be for many users. Allen’s book contains a great deal of nuance and many optional components — context tags, energy-level tagging, project hierarchies, “someday/maybe” lists, tickler files — that are helpful for some people and unnecessary for others. The full system can become an obsession in its own right, with practitioners spending more time maintaining their GTD setup than doing the work the setup was supposed to enable. This is the system-as-procrastination failure mode, and it is more common than the productivity literature usually admits.
The second limit is that GTD is fundamentally a system for managing commitments, not for choosing them. It can tell you what your next action is on any given project. It cannot tell you whether the project is worth doing in the first place. The “engage” step, when used badly, becomes a kind of well-organised reactivity — the worker dutifully executes the next action on every list, never asking whether the lists themselves are pointed at anything that matters. A well-implemented GTD system run by someone with no clear priorities will produce a great deal of efficiency in service of nothing in particular. Allen acknowledged this in later writings, recommending the integration of GTD with longer-horizon planning practices, but the integration is not built into the core system in a way that beginners can easily see.
The third limit is that GTD assumes a certain disposition toward writing things down and maintaining lists. People who find this disposition congenial often love the system. People who resist external structure often find it suffocating, no matter how much sense it makes in the abstract. Allen’s writing tends to assume that anyone who tries the system properly will come to love it. This is not always true. Some minds genuinely work better with looser systems, and the GTD approach is not the only legitimate way to manage one’s attention.
What David Allen Was Really Selling
When you strip GTD of its terminology, its diagrams, and its considerable cult, what remains is a single observation about how the human brain operates: that the brain is bad at holding commitments and good at processing them, and that separating the two functions is the highest-leverage productivity intervention most people will ever encounter. Allen built an elaborate system around this observation, and the system has helped a great many people. But the underlying insight is older and simpler than the system, and it can be honored even by people who never read the book. Anyone who carries a notebook and writes down what she means to do, and then trusts the notebook enough to stop carrying the obligations in her head, is doing GTD in the only sense that ultimately matters.
A 2019 survey of knowledge workers conducted by the productivity software company Doist found that the single practice most strongly correlated with self-reported high performance was “I have a reliable system for capturing tasks outside my head.” The respondents who agreed with that statement also reported significantly lower stress, better sleep, and greater satisfaction with their work than those who did not. The survey did not ask whether the respondents were practising GTD specifically. It did not need to. The capture habit was the variable that mattered, and capture is the first and most important step in Allen’s system. Everything else is, in some sense, scaffolding around that foundational practice.
Allen, who is now in his seventies, still teaches the system through his consulting practice and various seminars, although he has long since handed off most of the day-to-day work to a network of certified trainers. The book has sold more than two million copies in some twenty-eight languages, which is unusual for a productivity manual that contains no charisma, no personal narrative, and very few jokes. Its appeal has always been mechanical rather than charismatic. The system works, in the limited but real sense that it does what it says it will do, and that has been enough to sustain it across three decades and several generations of knowledge workers struggling with the same underlying problem. The brain is small. The world is full of commitments. The two have to be reconciled somehow, and Allen offered the cleanest reconciliation anyone had yet proposed.
What he actually sold, when he sold the books and ran the seminars and wandered into corporations in his slightly rumpled Californian way, was a kind of permission. Permission to stop trusting your memory. Permission to write down the silly small thing rather than carrying it. Permission to let the brain do the thinking it was built for and let the notebook do the holding it was built for. The permission is the most useful thing a productivity system can offer, and it remains, even in the era of apps and algorithms and the endless multiplication of digital tools designed to do the same job, as valuable as it was when Allen first articulated it in his small office in Ojai. The brain is a terrible filing cabinet. It is, however, an extraordinary processor. Anything that frees the processor by relieving it of the filing is, almost by definition, worth doing. GTD just happens to be the most thoroughly worked-out version of how to do it that anyone has yet produced.