emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Charles Cave <charles_cave@optusnet.com.au>
To: Alex Bochannek <alexb@juniper.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Another GTD question.
Date: Wed, 27 Sep 2006 22:39:07 +1000	[thread overview]
Message-ID: <451A70EB.2000003@optusnet.com.au> (raw)
In-Reply-To: <ud59ipf8o.fsf@juniper.net>

Hi Alex,

 > I am currently using a system that isn't
> that different from it, but I am trying to figure out the "best" way
> to use Org-mode for GTD.

I don't think there is any "best" way to use GTD system or org-mode
for that matter.  One of the core principles of GTD is creating
lists of next actions organised by context. A context is some
restraint that only allows the action to be done in a particular
place, time, or with particular resources.

> my first instinct would be to group all my work next actions under
> specific headlines (e.g., hardware, software, etc.) since I work in
> different areas.

I think that is a good idea because when you review your "system"...
the org-mode file you can use these headlines if hardware, software,
etc as a checklist for the question "Are there any outstanding actions
on this equipment?".

 >  It's not
> really a context since while I am at work, I can work on any number of
> tasks in the different areas. The context talks about what it is I
> need, where I need to be, or a type of activity. Maybe I overlooked
> something, but it seems like another dimension to the problem.

Maybe WORK is a sufficient context for your office related
activities. I don't think you need to break it down any further than

> How does this relate to Org-mode? In Org-mode I see different
> approaches to how one could structure these lists:
> - Outlines
> - Tags
> - ToDo keywords
> - Categories (files)

The lists can be structured anyway you want, but the strength of 
org-mode is scanning your whole file to build up a list of lines
matching a tag.  Organising the actions under specific category tags
is extra (unnecessary) work since org-mode does it for you.
Keeping the actions in context with other items may make more sense.

Let me add my context tags to yourlist

> o Call the bank about personal statements   :PHONE:
> o Go to post office to buy stamps  :ERRANDS:
> o Wait for SysAdmin to finish server install :WAITING:
> o Hang new pictures at home :HOME:
> o Discuss new development process with boss  :BOSS:
     (Create a tag for items (agenda) to discuss with your boss
> o Read through vendor proposal  :READING:
    (Can this reading be done at home or on your train trip to
      work? Reading is one of those activities that can be done almost
> o Server Install project at work    :OFFICE:
> o Install software upgrade on laptop :OFFICE:
> o Learn more about font-lock in Org-mode :OFFICE:

So when you are at the office, you display the tags for OFFICE.

If you set up a meeting with your boss, you search for :BOSS so you
get the most out of your meeting with the boss.

When you are reviewing what you are waiting for, use the WAITING tag.

During your lunch break, you search for ERRANDS.

> I am really looking forward to hear what people who are already using
> GTD with Org-mode suggest and hope that those how are not familiar
> with GTD may still find the discussion interesting.

I'm still refining my system with org-mode so I am keen to hear from
others on this.


  reply	other threads:[~2006-09-27 12:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 20:03 Another GTD question Alex Bochannek
2006-09-27 12:39 ` Charles Cave [this message]
2006-09-29 10:07   ` Christopher Kuettner
2006-09-30  5:25   ` Alex Bochannek
2006-09-30 11:28     ` Carsten Dominik
2006-10-01 14:41       ` Piotr Zielinski
2006-10-02  8:58         ` Chris Lowis
2006-10-14  4:44       ` Alex Bochannek
2006-10-01 23:54     ` Charles Cave
2006-10-14  4:53       ` Alex Bochannek
2006-09-27 14:18 ` Uwe Jochum
2006-10-04 16:11 ` Carsten Dominik
2006-10-04 17:11   ` Piotr Zielinski
2006-10-20  7:54     ` Carsten Dominik
2006-10-21 20:54       ` Christopher Kuettner
     [not found]         ` <b71b18520610211738s297f8f79u227d2ce32e10d2d9@mail.gmail.com>
2006-10-22  0:39           ` Eddward DeVilla
2006-10-23  6:10             ` Carsten Dominik
2006-10-23  7:21               ` Xiao-Yong Jin
2006-10-23  7:36                 ` Carsten Dominik
2006-10-23 20:30                   ` Xiao-Yong Jin
2006-10-23 13:24               ` Eddward DeVilla
2006-10-22 11:28         ` Pete Phillips
2006-10-05 13:01   ` Jason F. McBrayer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=451A70EB.2000003@optusnet.com.au \
    --to=charles_cave@optusnet.com.au \
    --cc=alexb@juniper.net \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).