Home | Site Map | Disclaimer | E-mail me

Getting Things Done!

Introduction

 

 

Why GTD?

During 1999 and 2000 was overwhelmed with the number of things that I had to do. By chance I read an internet article on a local web site, now defunct, that had rights to publish Fast Company magazine articles. This article, entitled You can do anything but not everything, started a search, I gleaned things off the David Allen web site, found a couple of other articles and in a patchy way put it all together.

 

When the book eventually came out I found that I had had got some of it right but not all of it.

 

But it had already transformed my life. I got to things I had never got to before and felt a greater sense of power and accomplishment.

 

The sources

 

 

Books

Allen, David,  2001 Getting Things Done – The Art of Stress-Free Productivity New York : Penguin

Allen, David,  2003 Ready for anything – 52 Principles for increased Productivity

 

Web site

http://www.davidco.com

 

Resources

 

 
Introductory resources

I have put together the following resources:

  • Workflow diagram
  • Some articles, including the one minute workflow manager
  • PowerPoint presentation
  • Click here to download resources in a Zip Archive
 
Wenzani - an Excel based planning tool

This is my spreadsheet planning tool I use to run the affairs of my small company. The current version is 4.2
I removed all the macros from version 3 which seem to cause difficulties with other language editions. This version makes more use of filtering.

As of Version 4 I renamed it the file 'Wenzani' which in Zulu means "What are you doing?"

Click to download as a Zip archive

 

2006-12-28: I've developed a slightly simpler version Version 5.0 >>Click to Download

 

 

Some tips

 

 
Projects

This caused me considerable confusion in the beginning.
David Allen defines a project "as any desired result that requires more than one action step."
That's clear enough. But the trouble was that my thinking was contaminated by work projects which had several results areas, sub-results, milestones etc.
Eventually I realised that larger (mostly work) projects could also be broken down into David Allen projects. This means that within the larger projects you may be working simultaneously on a number of small DA-type projects.
Those I then started thinking of those as "Outcomes". Each outcome is a desired result- something that required several actions to complete. This created an extra bit of complexity but the reason stays the same.
A number of outcomes eventually lead to the completion of the larger project.

 
Describing projects and outcomes

Where you can, phrase the project or outcome (the desired result) in the past tense, as though it has been done, eg

  • New accountant appointed

  • Final report and invoice submitted

  • Articles reviewed and summarised

Do this by visualising what the last completed step in the process is.

I learned this from moderating (facilitating) participative planning processes such as ZOPP and Log Frame. It shifts your attention from objectives (easy to say) to concrete results (easier to do).

 

 

 

 


 

 

 

 

Copyright © 2001 - 2011 Xasa Facilitating (Pty) Ltd. Home | Site Map | Disclaimer | E-mail me