emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Cc: Rene <jlr_0@yahoo.com>
Subject: Re: Is OrgMode really GTD compliant?
Date: Sun, 27 Apr 2014 17:21:50 -0700	[thread overview]
Message-ID: <87wqeaqp5t.fsf@berkeley.edu> (raw)
In-Reply-To: loom.20140427T224929-90@post.gmane.org

Hi Rene,

Rene <jlr_0@yahoo.com> writes:

> According to David Allen, whenever you define an action you need to
> assign three pieces of information that you will later use as criteria
> to decide what to do (in order of precedence):
>  1. Context: Where should I be (@home, @work, etc.) and/or which tools
>     should I have at my disposal (@computer, @internet, etc.) to do
>     this action?
>  2. Time needed: Which amount of time available must I have to do
>     this action?
>  3. Energy needed: How wasted/fresh can I be to do this action?
> Then, when you're up for executing an action, you use "context", "time
> available", and "energy available" as a sieve to sift out what can be
> done. Only after you've looked at these three can you determine what
> is the priority for right now, the present moment.
> ...
> Orgmode helps you capture
>  - the context: by means of tags,
>  - the time needed: by means of an "effort" property,
>  - the ABC priorities: by means of cookies.
> Has anyone tried to customize orgmode so as to make it really GTD
> compliant?

I am not really familiar with the official GTD methodology, and I don't
know exactly how you would normally represent the "energy needed"
associated with a task, but here's a suggestion.

It occurs to me that you could just use the A/B/C priority cookies to
represent energy levels, since you don't want to use them to encode
priorities.  Something like:
  #A: need to be fresh
  #C: can be wasted
  #B: everything else
or whatever would work for you.  If that's granular enough to represent
your energy-needed levels, then it's a neat hack that requires zero
customization.  Sorting and filtering by energy needed is then already
built into the agenda functions, etc.  Just think "energy needed"
whenever Org says "priority" (which isn't very often), and you're good
to go.


  reply	other threads:[~2014-04-28  0:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-27 20:51 Is OrgMode really GTD compliant? Rene
2014-04-28  0:21 ` Richard Lawrence [this message]
2014-04-28 17:18   ` Rene
2014-04-29  6:51     ` Alan Schmitt
2014-04-29 10:30       ` Samuel Loury
2014-04-29 10:49         ` Alan Schmitt
2014-04-29 13:26           ` Samuel Loury
2014-04-29 13:31             ` Bastien
2014-04-29 13:37               ` Alan Schmitt
2014-04-29 13:42                 ` Bastien

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=87wqeaqp5t.fsf@berkeley.edu \
    --to=richard.lawrence@berkeley.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=jlr_0@yahoo.com \


* 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).