The History of Getting Things Done: From Seminar Room to Cognitive Science

By Victor Hoang · Updated Oct 24, 2026

In the early 1980s, the people struggling most with open commitments were not factory hands. They were managers and professionals whose work arrived as requests, ideas and half-finished projects. A consultant named David Allen taught them how to deal with that backlog.

Getting Things Done, or GTD, is the personal productivity method Allen created. By his company's own account it started in 1981 as a consulting practice and a seminar add-on. It reached the public as a book in 2001. Its throughline is simple: get everything out of your head and into a trusted system, then decide the next action for each item. Writing things down is centuries old. What Allen added was a complete, repeatable routine for doing it.

He spent roughly two decades teaching it before he put it in a book. This article follows the method from its precursors to its first courses, the book, the 2004 moment when it escaped the seminar circuit, the apps built on it, and the scientific paper that tried to explain why it works.

Timeline at a Glance

The Notebook Years (1600s-1979)

People kept external memories long before anyone called it a system

Picture a reader in the early 1700s with a bound blank book open on a desk, copying passages and ideas under headings so they can be found again. That is a commonplace book, and it is the oldest ancestor of the idea at the center of GTD. When Locke's A New Method of Making Common-Place-Books was printed in English in 1706, keeping such a notebook was already a skill worth writing a manual about.

This is a precursor, not GTD. A commonplace book stored passages worth remembering. It had no list of next actions, no review ritual, no way to tell a commitment from a quotation. The same is true of other list-based habits that followed, such as the daily short list described in our guide to the Ivy Lee method, or the sorting grid in the Eisenhower Matrix, whose own history runs from a 1954 remark to Covey's quadrants. Each is a tool for deciding or remembering. None is a complete workflow for everything that lands on a person's desk.

What changed in the twentieth century was the kind of work. In 1959, Peter Drucker published Landmarks of Tomorrow, the book usually credited with introducing the term "knowledge worker" (the date appears as 1957 in some bibliographies; our history of knowledge work covers the variants). A knowledge worker's job is defined by what they decide to do with information, not by a task a foreman hands them. That is where the problem Allen later tackled lives. Nobody tells you which of your fifty open items to do next.

What this means for teams today: a notebook, a wall calendar and a to-do list were never the problem. The missing piece was a rule for what to do with each thing once it was written down.

Allen's Seminars (1981-1995)

A consultant tests a method on managers in a classroom

According to the David Allen Company's own timeline, the story begins in 1981, when it dates the establishment of the David Allen Consulting practice and the development of a "pre-GTD" course, an add-on to the Insight Seminars course on personal productivity. The company's phrase for the period is best practices "researched and tested in real time", which is a fair description of how a method gets built in a classroom: teach it, watch where people get stuck, change it.

In 1983, by the same timeline, a two-day course was developed and delivered, and Insight Consulting Group was established with Russell Bishop. In 1985 an early version was rolled out to a large corporate client in the United States as part of training programs in aerospace. In 1990 the first international course was delivered in Prague, which the company describes as a service donated to the East-West Institute.

Nothing in this period is a published book, so the evidence for it is the company's own account and not an independent record. What the dates do show is the order of events. The method was taught, to groups, for roughly twenty years before it was printed. That matters because the book is a record of practice, not a theory from a desk. In their later paper, the scientists Francis Heylighen and Clément Vidal described GTD as based on "years of experience in teaching knowledge workers" how to handle their backlog of unprocessed issues.

What this means for teams today: a working method usually comes from teaching it to real people first. If your team is designing a process, run it with a small group, watch where it breaks, and revise before you write it down for everyone.

The Book Years (1996-2003)

Weekly essays turn into a manual

In 1996, the company's timeline says the David Allen Company was established, the first version of its website was created, and Allen started writing weekly essays. Those essays were later used in his book Ready for Anything, published in 2003.

The book that carried the method was Getting Things Done: The Art of Stress-Free Productivity, published in New York by Viking in 2001 according to the Internet Archive's catalogue record, with a Penguin paperback following in 2003. In it Allen set out five stages of work. Heylighen and Vidal quote his own summary: people collect things that command their attention, process what they mean, organize the results, review them as options, and then do. The same paper cites Allen's description of the ideal result as a "mind like water", borrowed from martial arts, a calm state in which you respond to what is in front of you.

The core instruction was to move everything that nags you into a trusted external place. The David Allen Company still prints a tagline that says it plainly: "Your mind is for having ideas, not holding them".

The book was a full written statement of a method that had so far been passed on in rooms. How far it reached beyond those rooms was settled in 2004.

What this means for teams today: a method needs a name for each step so people can talk about it. GTD's five stages gave managers a vocabulary ("what's the next action?") that they could use in meetings.

The Lifehack Boom (2004-2008)

Programmers adopt Allen and a movement is named

On 11 February 2004, the technology writer Danny O'Brien gave a talk on how highly productive technologists organize their work at O'Reilly's Emerging Technology conference. A blog post written the same day summarized the findings: these "alpha geeks" lived in shells and text editors, distrusted complicated applications, and kept simple to-do files. The writer Cory Doctorow, who attended, later recalled that one takeaway from the talk was a recommendation to read David Allen's 2001 book. By 2004, he wrote, he had bought and given away half a dozen copies and put the method in place.

The effect was to move GTD out of corporate training rooms and into a community that blogged. Software people were also the first to build tools for it. In 2006, the Omni Group asked Ethan Schoonover and Merlin Mann to help turn Schoonover's GTD add-on for OmniOutliner into an official application. After more than a year of private development, OmniFocus entered public beta in November 2007 and reached version 1.0 on 8 January 2008, according to a history of the product. The method now had software that mirrored its vocabulary: inboxes, projects, contexts, reviews.

Meanwhile, the academics noticed. Heylighen and Vidal wrote that as of October 2007 no academic papers had examined the method in any detail. They reported that, at that time, Allen's book ranked first on Amazon's "time management" and "business: health and stress" bestseller lists and that a search found more than a million web pages referring to GTD. Their paper, published in Long Range Planning in December 2008, argued that the theories of situated and distributed cognition support the idea of using the environment as an external memory. They also noted why GTD is hard to test: it has no explicit priorities or optimization criteria, so there is no obvious standard against which to measure improvement. Their answer was a theoretical grounding, not an experiment. They also proposed extending GTD to collaborative work through stigmergy, where people coordinate through marks left in a shared environment.

What this means for teams today: the research gave a respectable reason for something managers already felt. Offloading commitments to a reliable external place reduces the load on memory. It does not prove that GTD outperforms other methods, and its authors did not claim that.

The Second Edition (2009-present)

A rewrite for inboxes that never close

The company's timeline lists the first GTD Summit in San Francisco in 2009, a gathering of enthusiasts sharing practices, and a 2008 book, Making It All Work, that took the method wider. It also records a moment in 2013 when Allen visited a classroom and saw a group of 23 children aged 8 to 10 doing a Weekly Review, an indication of how far the routine had traveled from the aerospace training rooms of 1985.

In 2015, the company says, a second edition of the book was published, completely rewritten and released in 25 languages. The Internet Archive lists a 2015 Penguin edition alongside the original. The method's current public description uses a new set of verbs: capture, clarify, organize, reflect and engage, where the 2001 summary quoted by Heylighen and Vidal used collect, process, organize, review and do. The steps are the same in spirit. The names are friendlier and a bit more active, and the first step now covers "any and everything" that has your attention.

The book is now published in over 28 languages by the company's account, and its 2019 summit in Amsterdam celebrated 35 years of the methodology. If you want the practical walk-through of today's version, our guide to Getting Things Done covers each step in detail. For the paper and digital tools GTD lists have lived in, see the history of the day planner.

What this means for teams today: GTD is a personal system. When a team adopts it, the weak point is usually shared work: whose next action is it, and where does the team see it? That is the gap Heylighen and Vidal's stigmergy proposal tried to address, and it is the same gap a shared task board addresses.

Key People

Key Facts

Key Facts: Getting Things Done

• The David Allen Company dates the start of Allen's consulting practice to 1981 and the first book edition to 2001.
• The 2001 book names five stages: collect, process, organize, review, do.
• The current public description names capture, clarify, organize, reflect and engage.
• Danny O'Brien's 11 February 2004 talk is the talk Doctorow recalled pointing him to Allen's book.
• OmniFocus 1.0, built on a GTD add-on, launched on 8 January 2008.
• A 2008 peer-reviewed paper argued that cognitive science supports GTD, but it did not run an empirical test.

The Pattern Behind the History

The Trusted Outside is our synthesis of the pattern, not a published model. Every stage of this history is a version of the same move: put the commitment somewhere outside your head, then keep that place trustworthy.

1. The notebook comes first. From commonplace books to the to-do list, people have always offloaded memory.
2. The rule comes second. What GTD added was a decision when each item is processed: what is the next action?
3. Review keeps it alive. A list you stop trusting is worse than none, so the review is what makes the system last.
4. Tools follow the vocabulary. Software arrived only after the method had names for inboxes, projects and reviews.
5. Theory arrives late. The cognitive science came seven years after the book, and it explained the practice instead of inventing it.

What It Teaches Teams Today

• Offload, then decide. Capture alone creates a bigger pile. The step that helps is deciding the next action when an item is clarified.
• Make the review a habit. The weekly review is the part most people drop, and it is the part that keeps the list believable.
• Build from practice. Allen taught the method for about twenty years before the book. Test your own processes with real people first.
• Be honest about the evidence. The best-known research on GTD is theoretical. Treat the method as a well-reasoned habit, not a proven productivity multiplier.
• Place it in the long story. GTD sits inside the arc of productivity and our guide to time management covers adjacent skills.