Getting Started with GTD: The buddy system

Source: HitchFit.com

Introduction

When I was getting started with Getting Things Done (see GTD Notable PDF), I had two buddies. First, an experienced GTD buddy Ian Watson, and another novice buddy, Mark VanderSys whom I mentioned in yesterday’s Getting Started with Getting Things Done post as well as in earlier RestartGTD posts here and here.

GTD Experienced Buddy Lessons Learned

  1. I want your word that you will read the book … I won’t get off your chest until you promise. This was the GTD start for me. “Yes, I give you my word :-(” … hey, they have GETING THINGS DONE on Audible!
  2. Project file folders need to be kept separate from reference file folders.
  3. “Go to David Allen’s seminar. Do not bitch at me about the cost. No, never mind, I’ll pay the cost for you!”
  4. Check ins with an experienced GTDer help A LOT.

GTD Novice Lessons Learned

  1. I’m not the only one who gets overwhelmed.
  2. When I get overwhelmed, the best thing to do is to go back to chapters 1 through 3 of GTD, and review.
  3. We CAN do this!
  4. When writing down a next action, nothing less than a complete sentence. Cryptic next actions on cards take time to remember. And, can cause your subconscious to loose trust in your system.
  5. When creating project names, make them short, memorable, and funny. Short, memorable, funny project names are easier to remember.

How a GTD buddy helps

GTD buddies help you by:

  • Giving tips that build early GTD implementation momentum.
  • Checking in, which forces you to reflect and realize that GTD is working, even though new GTD users obsess exclusively about how GTD seems not to be working
  • Encouraging you to keep on. A month or so into my GTD implementation Ian Watson (Experienced GTD buddy) said “Wow. Having a meeting with you, is like … having a meeting with me!” HUGE!

How to find GTD buddies

  • Novice GTD buddies are found by reading chapters 1-3 of GTD, then evangelizing the idea of GTD to your friends. See who takes up the challenge, and wants to talk to you about it.
    • *Note* do not be discouraged if your spouse is not your GTD buddy. Spouses are too close to be good GTD buddies. And often, spouses read GTD and being the more organized member of your union, say “But, … I already do all of this!” Not building on your momentum.
  • Experienced GTD buddies have probably, already found you. In my rich fantasy life, I like to think that this blog is an experienced GTD buddy finding people. But, … not. RestartGTD readers have already been found, evangelized, and have taken a shot at implementing GTD before they find this blog.
  • If you don’t have an Experienced GTD buddy, try Appendix B: Talk to an experience GTD Buddy below to send questions to me. I hereby volunteer (for now) to being an experienced GTD buddy to RestartGTD readers.
    • [9 hours later 0 takers, c’mon!]

How to use GTD buddies

  1. Find the recipe …
    that you want to use to take a(nother) crack at getting on the GTD band wagon. Pick a “getting started” recipe from the book (and/or David Allen has a new introduction to GTD focusing on fundamentals
    ), RestartGTD’s blog post recipe, or other any other recipe.
  2. Tell them
    That you are trying to implement GTD again. Send them an email. Point them to your recipe. Ask them for their recipe. I benefitted enormously from Ian Watson’s being at my elbow, eager to answer questions.
  3. Ask them to help
    specifically, if you can once a week, for one month, talk to them about their use of GTD, and get them to review your use. After a month, check in occasionally on a timed basis (8 weeks) or whenever one buddy feels overwhelmed. Read Appendix A: Using Skype to implement your GTD buddy system below. And then do your weekly show and tell, sharing screens. Just for a month.
  4. Follow up
    when a week passes and it is time to check in with your GTD buddy. Just Do It! This may be mentally tough, the universe (you may have noticed) resists us becoming organized.

Try GTD Before you Give UP

If I can implement GTD, … anyone can implement GTD. I was the worst organizational sinner on Earth. Here, … see if you can guess which desk is before GTD, and which is after GTD.

If you want to see more, then check out my before GTD after GTD post. And, my post on how procrastination and guilt go down over time with GTD.

bill meade


 Appendix A: Using Skype to implement your GTD buddy system

Using Skype to share screens is easy!
1. Get your Skype session going. If you need to set up Skype, click here for a YouTube tutorial.
2. Click on the plus thought bubble at the bottom of the screen
3. Click share screen in the pop up:
4. One buddy goes first, showing how s/he has implemented GTD. Questions go back and forth.

5. Then whoever went first, clicks the + thought bubble, stops screen sharing, and it is the turn of the other buddy to give a walk through of their system. Questions go back and forth.

6. MOST IMPORTANT after you sign off, each buddy writes four “lessons learned” bullet points, and emails them to the other buddy.


 Appendix B: Talk to an experienced GTD Buddy

Getting Things Done: Reviewing GTD in a complicated organizing program

Source: PixelLight.com

Introduction

I have an artist friend, Mark VanderSys

Source: BetterLight.com (2/3 down the page)

who runs a small, extremely high-touch graphics business: PixelLight.com. By extremely high-touch I mean: gigapixel pictures with digital scan backs, heavily customized web sites, and seemingly impossible pictures without parallax (i.e., the entire width of the picture is taken at a perfect 90 degree angle to the subject) and …

extremely clean low-retouch photography

New Addition:
The picture at the top of this post is an un-retouched image taken of objects spinning. It was taken with a BetterLight.com digital scan back in a standard 4×5 industrial bellows camera, Mark gave a tutorial at BetterLight where he showed step by step how the picture was taken. Click here for the magic pixie dust demo via an .mov file that shows the process.

Mark and I have been implementing Getting Things Done together for several years. Mark uses a customer requirements planning program, Asana.com, to organize, share, and track his work. Mark and I just spent two hours looking over his implementation of Asana, and reflecting on how GTD lives in very complicated, very powerful systems like Asana.

Lessons Learned

  • Using Skype to share screens is easy!
    1. Get your Skype session going.
    2. Click on the plus thought bubble at the bottom of the screen
    3. Click share screen in the pop up:
    4. Continue your conversation while sharing your screen!
  • Complexity of the tool, Asana, Omni-Focus, whatever, expands like a gas to fill your energy and memory, leading to feelings of being overwhelmed. And,
  • … complexity crowds GTD logic out of your mind.
  • When GTD gets crowded out by a tool, we naturally stop managing self-expectations. You are now standing at the top of the GTD off-ramp.

How to implement a new program

  • Get some work into the system. Don’t worry be crappy.
  • Get to know the system, really try to make it work. But, relax. Rome was not built in day.
  • When you get frustrated, talk to your GTD buddy. Getting started with GTD is much easier when you have a buddy. Mark VanderSys is my GTD buddy.

What your GTD buddy will tell you:

  • Slow down.  Rome was not built in a day.
  • Go back to basics. Now that you know a bit about Asana (or OmniFocus, or whatever) it is time to re-read the first three chapters of Getting Things Done. As you go through the chapters s-l-o-w-l-y, write ideas on 3×5 cards, page by page through chapters 1 through 3.
  • Focus on how the program allows each of GTD’s tools to be implemented. Make notes of next actions for doing GTD more fully.

Organizing Work with Hierarchy … and in an Intertwingled World

 

Source: Preface Intertwingled

 

  • Organizing tools allow different kinds of organization. In particular, different kinds of project-next action relationships.
    • Paper
      … with a next action focus, manila folders, creates an implicit one-to-many work hierarchy. One project, one manila folder, and inside many next actions. All the next actions relate only to the project indicated by the folder’s name.  
    • Outline tools
      … like OmniFocus (built around OmniOutliner), Evernote, and OneNote use an implicit one-to-many work hierarchy. That is, you start with a project, and then create N next actions to complete the project. But advanced tools like OmniFocus go a bit further. Next actions can relate not only to projects in a hierarchical way. Next actions can also relate to contexts. So the simple one-to-many hierarchy of project and actions, begins to fray. GTDers are coached to think of projects and contexts as a kind of matrix organization structure, and then next actions live at the intersection of project and context.
    • CRM (Customer Requirements Management)
      … systems like ASANA however, are not limited to one-to-many work hierarchy. Yes, you can create a project and then a task underneath the project. But in addition, Asana tasks can be related explicitly to multiple projects.

      This is a many-to-many link which CRM systems have evolved so that a next action can be tracked in relation to many projects. With many-to-many relationships, CRM allow GTDers to use “more colors of the rainbow” by tracking multiple projects that a next action relates to, but CRM systems shatter top-down one-to-many work hierarchy that a GTD person is used to seeing, and substitute an extra step of running queries, to see the full status of a next action against its projects. Very disorienting … at first.

  • Ugh, I’m feeling scared. Overwhelmed, dizzy. What can I do if I need to use a CRM system to implement GTD in my intertwingled life?
    • Go back up to what your GTD buddy told you above:
    • Just be aware of what the electronic system can do. And use GTD within that electronic system, as fully as you can. Don’t force yourself to use too much complexity.
    • Wait. Over time, as you keep your eye on GTD inside the system, you’ll have ideas. For example, you might have the idea in Asana, of doing a query that shows you the next actions in the system, that will move the most projects forward. Might be useful to try!
    • Experiment. Let these ideas come, and then experiment with them.

Thanks Mark VanderSys for a fun afternoon of GTD buddy check in!

bill meade