Poojan (Wagh) Blog

Requests for comment

GTD Seminar

with 2 comments

A few weeks ago, I got to go to the David Allen Company’s “Mastering Workflow” Seminar. I’m glad I did. The seminar resolved several misconceptions I had about how GTD works, despite my owning Getting Things Done: The Art of Stress-Free Productivity in both text and audio form.

The seminar was lead by Chris McIntyre. He was an impressive presenter. I noticed that he immediately asked who had read the book and was implementing the system. He asked those who raised their hand what they liked about the system. Very smart: I’ve seen many a presentation get derailed by “experts” who want to either show their knowledge or derail the presenter. By identifying the “experts”, Chris recognized their expertise and brought them into the fold.

The seminar isolated several reasons why GTD wasn’t working as effectively for me as it could be:

  • Processing: I (for some reason) didn’t get that one should process all inboxes once a day. I was tending to do it as part of the weekly review, which left me feeling very behind. I thought I was deviating from the system when I processed more often. In addition, since I wasn’t sure I was going to process daily, I tended to try to process things as they came—which disrupted my focus.
  • Collecting: Ask, “Do I need more collection buckets or less?” I tried my best to have just one bucket. However, that’s a bit unreasonable. There’s an optimal value for each person (and it probably changes from month to month).
  • Someday/Maybe: I never could figure out whether I should put more or fewer items on the S/M list (versus the next-action context lists). The answer: are you repelled by the number of actions on your next-action lists? If so, move some of them to the Someday/Maybe list.
  • Multiple Someday/Maybe lists: There’s no reason to have one. If there’s a major project you want to do sometime in the future, you can have a separate list for that.
  • Email: I try to follow the 3-folder arrangement (Inbox, Follow-Up, Archive). However, what I didn’t realize was that instead of processing things in my inbox, I was deferring them by putting them in the “Follow-Up” folder. When an action needs to be performed on an email, it should go in the Follow-Up folder, but the action needs to get recorded somewhere (@Email for example).
  • Action Support: If something wasn’t in my inbox, it was either in trash or in a Reference file. I found myself creating new filing folders for even the smallest things. Instead, Chris recommends having an “Action Support” folder for active things. This really simplified my filing. I didn’t need to create a “tuition” file just so I can pay the tuition. Technically, my wife came up with this idea before I went to the seminar, but I didn’t listen.
  • Ticklers: I could never figure out how to separate between a tickler file and a Someday/Maybe. Chris cleared up the confusion by pointing out that the Someday/Maybe list gets checked every week (during your weekly review), while the tickler gets checked on a specific day/month. I asked whether I could use a calendar for this purpose. The answer was yes, except that a tickler file is useful if you want the actual object (bill, concert tickets, etc.) to be the reminder.
  • Managing No’s (Someday/Maybe): The Someday/Maybe list is a way of not making an agreement. Trick to managing your next-actions is to figure out how much you can do this week.

I had a few other random, non-actionable thoughts:

  • Did David Allen come up with the runway, 10,000-foot, 50,000-foot model due to his consulting relationship with Lockheed-Martin? Perhaps it was the best metaphor for the clientele. Perhaps their nomenclature inspired him.
  • Capture everything: I always thought GTD was compulsive in the habit of capturing everything even if it’s not important. However, I think the reason for this is that there are things that we just don’t want to do (we want to procrastinate) and leaving the decision of what to capture to your intuition can be dangerous. It’s better to retain everything and analyze it clearly.

The biggest thing I learned from the seminar was that I need to experiment more. I had taken the GTD methodology to be a mandate. However, during the seminar, Chris McIntyre makes it clear that the GTD recommendations are merely practices that have been found to be effective. I’ve found that my ideal GTD system as the following traits (personal preferences):

  • Very little setup: things such as contexts, etc., should not require setup. I should be able to add/remove contexts on demand.
  • Printing: I find it hard to organize work (that’s usually on a computer) with a computer. It’s nice to have a printed checklist.
  • Computer automation: I find it tedious to do things (such as match a project with an action) that can be automated.
  • Paper capture: …however, I can draw diagrams and capture information much easier on paper.

GTD isn’t for everyone, but I’m getting much more value out of it now that I understand it better. Before, it seemed overly complicated. Now it seems a simpler and effective.

In a future post, I’ll describe the GTD system that I’m using now.

Written by PoojanWagh

May 13th, 2009 at 10:08 pm

Posted in Uncategorized

Tagged with

2 Responses to 'GTD Seminar'

Subscribe to comments with RSS or TrackBack to 'GTD Seminar'.

  1. “GTD isn’t for everyone.”
    I have a theory a person’s productivity method marry up to Myers-Briggs test results.


    15 May 09 at 8:18 pm

  2. Hi Poojan,
    Great writing about some compelling topics within GTD. I’ve been studying GTD too, but I’ve never been to a live conference (lots of audio though) and indeed, the horizons of focus ‘altitude’ idea came from David’s work consulting for aerospace corps.

    One thing in your post that caught my eye is this: You say that you would like to automate linking projects to their actions. Even this is unnecessary–in the DavidCo podcast, there’s a great interview between Kelly Forrister and David Allen where they address this very point. David says that we should never worry about linking projects to NEXT actions–this is done in our minds during the weekly review. The ‘then I need to, then I need to…’ ad hoc project planning should go onto a mindmap or other project support document, not on the action list. If you do this, there is no need to link next actions to the project they drive forward.
    Kind Regards,
    Matthew Smith


    17 May 09 at 2:00 am

Leave a Reply