Hi Rene, Rene <jl...@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. -- Best, Richard
