GTD Basics
By Daniel Miessler on November 19th, 2006: Tagged as GTD | Productivity
Collect
Capture everything that you need to track or remember or act on in what Allen calls a ‘bucket’: either a physical inbox, email inbox, tape recorder, notebook, or any combination of these. Get everything out of your head and into your collection device, ready for processing. All buckets should be processed to empty at least once per day.
Process
When you process your inbox, follow a strict workflow:- Start at the top.
- Deal with one item at a time.
- Never put anything back into ‘in’.
- If an item requires action:
-
- do it (if it takes less than two minutes),
- delegate it, or
- defer it.
- If not,
-
- file it for reference,
- throw it away, or
- incubate it for possible action later.
Organize
Allen describes a suggested set of lists which you can use to keep track of items awaiting attention:- Next actions - For every item requiring your attention, decide what is the next action that you can physically take on it. For example, if the item is ‘Write project report’, the next action might be ‘Email Fred for meeting minutes’, or ‘Call Jim to ask about report requirements’, or something similar. Though there may be many steps and actions required to complete the item, there will always be something that you need to do first, and this should be recorded in the next actions list. Preferably, these are organized by the context in which they can be done, such as ‘in the office’, ‘by the phone’, or ‘at the store’.
- Projects - every ‘open loop’ in your life or work which requires more than one physical action to achieve becomes a ‘project’. These are tracked and periodically reviewed to make sure that every project has a next action associated with it and can thus be moved forward.
- Waiting for - when you have delegated an action to someone else or are waiting for some external event before you can move a project forward, this must be tracked in your system and periodically checked to see if action is due or a reminder needs to be sent.
- Someday/Maybe - things that you want to do at some point, but not right now. Examples might be ‘learn Chinese’, or ‘take diving holiday’.
A final key organizing component of GTD is the filing system. Getting Things Done says that a filing system, if it is to be used, must be easy, simple and fun. Even a single piece of paper, if you need it for reference, should get its own file if it doesn’t belong in a folder you already have. Allen’s suggestion is that you keep a single, alphabetically organized filing system, in order to make it as quick and easy as possible to store and retrieve the information you need.
Review
The lists of actions and reminders will be of little use if you don’t review them at least daily, or whenever you have time available. Given the time, energy and resources that you have at that particular moment, decide what is the most important thing for you to be doing right now, and do it.At least weekly, the discipline of GTD requires that you review all your outstanding actions, projects and ‘waiting for’ items, making sure that any new tasks or forthcoming events are entered into your system, and that everything is up to date. Allen suggests the creation of a tickler file in order to help refresh your memory each week with your outstanding tasks and projects.
Do
Any organizational system is no good if you spend all your time organizing your tasks instead of actually doing them! David Allen’s contention is that if you can make it simple, easy and fun to take the actions that you need to take, you will be less inclined to procrastinate or become overwhelmed with too many ‘open loops’.(All Content From Wikipedia’s Article on GTD)
--

Hey Daniel,
Have you, by chance, read “Time Management for System Administrators”? (I’d give you a link, but I think you have HTML disabled, so the ISBN is 0596007833 (it’s available used from Amazon for $11).
I picked this up a month or so ago when Borders was giving a 25% discount to “educators”, which somehow included me — I work at an .edu, but I’m a network admin, not a professor.
Anyways, for the last few months, I’ve been reading some of the various GTD articles and sites and trying to find ways to… well, get things done. My department is pretty small — just five full-time staff, a few part-time staff, and a handful of student workers.
While, looking back, I realize that much of what is written in the book is “common sense”, a lot of it didn’t really hit me until I read it in print. I’ve now read it twice, and started implementing what I could from the first day. The big thing for me was eliminating distractions — mainly that new mail notification from Outlook coming outta my PC speakers every few minutes. I’m to the point where I open Outlook three or four times a day, read/reply to what I need to right then, and close it out again. Perhaps 30 minutes before the workday is over and I start “winding down”, I open it one last time and deal with the mail that I put off for the day.
Obviously, that’s only one of any possible number of interruptions we “sysadmins” face and that’s not all of what the book covers. I really believe that being in the I.T. world has its own unique “challenges” with regards to managing your time — as well as many other professions do, I’m sure — and this book really hit home with me.
I won’t ramble any further, but if you’re really into GTD, pick up a copy of the book. If you read much of the GTD-type articles/sites, a lot of what it’s in the book will be familiar to you — at least in concept, but the author has found a way to relate it to the I.T. world and some of the unique challenges we face.
-j
Comment by Jeremy L. Gaddis — 11/21/2006 @ 2:47 am
Awesome, thanks man. :)
Comment by Daniel Miessler — 11/22/2006 @ 12:59 am