Getting Things Done

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Getting Things Done: The Art of Stress-Free Productivity
Getting Things Done.jpg
Getting Things Done: The Art of Stress-Free Productivity cover, first edition
Author David Allen
Subject Business
Publisher Penguin
Publication date
2002
Pages 267
ISBN 978-0-14-200028-1 (Reprint Edition)
OCLC 51540420

Getting Things Done is a time-management method, described in a book of the same title[1] by productivity consultant David Allen. It is often referred to as GTD.

The GTD method rests on the idea of moving planned tasks and projects out of the mind by recording them externally and then breaking them into actionable work items. This allows one to focus attention on taking action on tasks, instead of on recalling them.

Themes

Allen first demonstrates stress reduction from the method with the following exercise, centered on something that has entered your life that has an unclear outcome or where the next action is not defined. (Allen calls these sources of stress "open loops," "incompletes," or "stuff.")[1]:13

  • Pick an "incomplete": What most annoys, distracts, or interests you?
  • Write down a description of the successful outcome in one sentence. What is your definition of "done"?
  • Write down the next action to move toward the desired outcome
  • Notice how you feel after the exercise compared to before it.

He claims stress can be reduced and productivity increased by putting reminders about everything you are not working on into a trusted system external to your mind. In this way, you can work on the task at hand without distraction from the "incompletes."[1]:14 The system in GTD requires you have to hand an inbox, a trash can, a filing system for reference material, several lists (detailed below), and a calendar. These tools can be physical or electronic as appropriate (e.g. physical in tray or email inbox).[1]:88 As "stuff" enters your life, it is captured in these tools and processed with the following workflow.[1]:27

Workflow

Logic tree diagram illustrating the second and third steps (process/clarify and organize) of the five-step Getting Things Done workflow

The GTD workflow consists of five stages: capture, clarify, organize, reflect, and engage.[2] (The first edition used the names collect, process, organize, plan, and do; the description of the stages are the similar in both editions). Once all the material ("stuff") is captured (or collected) in the inbox,[1]:106 each item is clarified[1]:122 and organized[1]:141 by asking and answering questions about each item in turn as shown in the black boxes in the logic tree diagram. As a result, items end up in one of the eight oval end points in the diagram:

  • in the trash
  • on the someday/maybe list
  • in a neat reference filing system
  • on a list of tasks to defines the outcome and next action if the "incomplete" is a "project" (i.e. if it will require two or more steps to complete it).
  • immediately completed and checked off if it can be completed under two minutes
  • delegated to someone else and, if you want a reminder to follow up, added to a "waiting for..." list
  • on a context-based "next action" list of there is only one step to complete it
  • on your calendar[1]:27

Empty your inbox or inboxes daily or at least weekly ("in" to empty).[1]:122 Don't use your inbox as a "to do" list. Don't put clarified items back into the inbox.[1]:27 Emptying your inbox doesn't mean finishing everything. It just means applying the "capture, clarify, organize" steps to all your "stuff."[1]:27

Next, reflection (termed planning in the first edition) occurs. Multi-step projects identified above are assigned a desired outcome and a single "next action."[1]:191 Finally, a task from the your task list is worked on ("engage" in the 2e, "do" in the 1e) unless the calendar dictates otherwise. You select which task to work on next by considering where you are ("context" i.e. at home, at work, out shopping, by the phone, at your computer, etc.), time available, energy available, and priority.[1]:204

Implementation

Because hardware and software is changing so rapidly, GTD is deliberately technologically neutral. In fact, Allen advises people to start with a paper-based system,[3] many task management tools claim to implement GTD methodology[4] and Allen maintains a list of some technology that has been adopted in or designed for GTD. Some are designated "GTD Enabled", meaning Allen was involved in the design.[5]

Perspective

Allen emphasizes two key elements of GTD — control and perspective. The workflow is the center of the control aspect. The goal of the control processes in GTD is to get everything except the current task out of your head and into this trusted system external to your mind. He borrows a simile used in martial arts termed "mind like water." When a small object is thrown into a pool of water, the water responds appropriately with a small splash followed by quiescence. When a large object is thrown in the water again responds appropriately with a large splash followed by quiescence. The opposite of "mind like water" is a mind that never returns to quiescence but remains continually stressed by every input.[1]:12 With a trusted system and "mind like water" you can have a better perspective on your life. Allen recommends reflection from six levels or "horizons:"[1]:54

  1. current actions
  2. current projects
  3. areas of responsibility
  4. 1–2 year goals
  5. 3–5 year goals
  6. Life

Unlike some theories, which focus on top-down goal-setting, GTD works in the opposite direction. Allen argues that it is often difficult for individuals to focus on big picture goals if they cannot sufficiently control the day-to-day tasks that they frequently must face.[1]:54 By developing and using the trusted system that deals with day-to-day inputs, an individual can free up mental space to begin moving up to the next level.

Allen recommends scheduling a weekly review, reflecting on the different levels. The perspective gained from these reviews should drive one's priorities at the project level.[1]:50 Priorities at the project level in turn determine the priority of the individual tasks and commitments gathered during the workflow process. During a weekly review, determine the context for the tasks and put each task on its appropriate list. An example of grouping together similar tasks would be making a list of outstanding telephone calls, or the tasks/errands to perform while out shopping. Context lists can be defined by the set of tools available or by the presence of individuals or groups for whom one has items to discuss or present.

Summary

GTD is based on storing, tracking and retrieving the information related to the things that need to get done. Mental blocks we encounter are caused by insufficient 'front-end' planning. This means thinking in advance, generating a series of actions which can later be undertaken without further planning. The minds's "reminder system" is inefficient and seldom reminds us of what we need to do at the time and place when we can do it. Consequently, the "next actions" stored by context in the "trusted system" act as an external support which ensures that we are presented with the right reminders at the right time. As GTD relies on external reminders, it can be seen as an application of the theories of distributed cognition or the extended mind.[6]

Reception

In 2005, Wired called GTD "A new cult for the info age",[7] describing the enthusiasm for this methodology among information technology and knowledge workers as a kind of cult following. Allen's ideas have also been popularized through the Howard Stern Show (Stern referenced it daily throughout 2012's summer) and the Internet, especially via blogs such as 43 Folders,[8] Lifehacker,[9] and The Simple Dollar.[10]

In 2005, Ben Hammersley interviewed David Allen for The Guardian article titled "Meet the man who can bring order to your universe",[11] saying: "For me, as with the hundreds of thousands around the world who press the book into their friends' hands with fire in their eyes, Allen's ideas are nothing short of life-changing".

In 2007, Time Magazine called Getting Things Done the self-help business book of its time.[12]

In 2007, Wired ran another article about GTD and Allen,[13] quoting him as saying "the workings of an automatic transmission are more complicated than a manual transmission... to simplify a complex event, you need a complex system".

A paper in the journal Long Range Planning by Francis Heylighen and Clément Vidal of the Free University of Brussels showed "recent insights in psychology and cognitive science support and extend GTD's recommendations".[6]

See also

References

  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links