Getting Things Done

[Stephen Chakwin]

On 1/17/04 3:00 PM, "omnioutliner-users-request at omnigroup.com"
<omnioutliner-users-request at omnigroup.com> wrote:

> Send OmniOutliner-Users mailing list submissions to
> omnioutliner-users at omnigroup.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.omnigroup.com/mailman/listinfo/omnioutliner-users
> or, via email, send a message with subject or body 'help' to
> omnioutliner-users-request at omnigroup.com
> 
> You can reach the person managing the list at
> omnioutliner-users-owner at omnigroup.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OmniOutliner-Users digest..."
> 
> 
> Today's Topics:
> 
>  1. Getting Things Done? (Richard Sandilands)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sat, 17 Jan 2004 09:35:51 +1100
> From: Richard Sandilands <lists at infoarts.info>
> Subject: Getting Things Done?
> To: omnioutliner-users at omnigroup.com
> Message-ID:
> <R02010000-1032-5712F41E487411D8BECB000A9566B434@[10.0.0.1]>
> Content-Type: text/plain; charset=US-ASCII
> 
> Hi there
> 
> It's a long shot I know but is anyone out there using OO to implement
> David Allen's "Getting Things Done" time-management method?
> 
> If so, I'd love to hear how you set up your outline.
> 
> More info at http://www.davidco.com and no, I'm not connected with them
> in any way, apart from having bought the book.
> 
> Regards
> 
> Richard

I tried and decided that it was not the right format for an OO-type outline.
I'm now working something up in Tinderbox, which is a lot more complicated
to work with, but offers the flexibility that you need.

In my experience, OO is fine for the project list aspect of GTD (what you
use for a weekly review) but without a cloning ability, which I'm informed
we won't see even in the currently planned OO3, won't really do to keep your
To-Dos set up the way they would have to be in this type of outliner - as
both subheads of their respective projects and as organized into contextual
tasks (telephone, at computer, home, at office, etc.).

Also, if you are serious about using GTD, you really ought to have the to-do
list with you at all times so if you find yourself with a few moments and a
telephone, you can pull out your call list and get to work.  This means that
you either have to find a way to translate your OO outlines to an electronic
organizer or print them out.  I would print them out, but some might find
that a problem.

In Tinderbox, everything is a separate note of information that you can
gather and organize by using functions called "Agents" [they have wraparound
sunglasses and attitude problems].  Thus, you create a prototype for To-dos
which shows, among other things, their parent projects and a prototype for
Projects which shows, among other things, their parent projects, so you can
have sub-projects (or go as deep as you want) and then set up the contexts
as part of your to-Dos.  The agents will sort them by context and you've got
your lists (you can tell the agents that you don't want any completed To-dos
showing up in your lists if you wish).

Tinderbox is not cheap and has a learning curve that is not enhanced by its
opaque documentation, but if you are patient and willing to work your way
through it (or know the product and want me to send you a dummy file
off-list) you may find it worthwhile.  Note that you have the same issues
about portability that you have with OO - it doesn't do portables so you
have to do printouts.

Stephen