From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manish Subject: Re: [off-topic/GTD]Only Next Actions list to rule them all ? Date: Wed, 21 Oct 2009 11:21:38 +0530 Message-ID: References: <1e5bcefd0910202215n660589c9h65ffe5603b1bf8db@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N0U7B-0001xL-HL for emacs-orgmode@gnu.org; Wed, 21 Oct 2009 01:52:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N0U76-0001wp-6k for emacs-orgmode@gnu.org; Wed, 21 Oct 2009 01:52:04 -0400 Received: from [199.232.76.173] (port=39638 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N0U75-0001wl-VH for emacs-orgmode@gnu.org; Wed, 21 Oct 2009 01:52:00 -0400 Received: from mail-iw0-f174.google.com ([209.85.223.174]:52978) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N0U75-0000uj-Hy for emacs-orgmode@gnu.org; Wed, 21 Oct 2009 01:51:59 -0400 Received: by iwn4 with SMTP id 4so3310556iwn.14 for ; Tue, 20 Oct 2009 22:51:58 -0700 (PDT) In-Reply-To: <1e5bcefd0910202215n660589c9h65ffe5603b1bf8db@mail.gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Marcelo de Moraes Serpa Cc: Org Mode On Wed, Oct 21, 2009 at 10:45 AM, Marcelo de Moraes Serpa wrote: > Hello list, > > This is for the GTD orgers out there. I've taken the article written by > Charles as a basis for my GTD implementation. In the end, it's all about > what works for you, but I'd like to get some insights/opinions from you: For > Next Actions, are you using a single list OR you organize them > hierarchically under each project (in the projects list)? > > I started with the second one, putting each next action (TODO) item under > its correspondent project, however, it quickly became too bloated, and a mix > of projects, sub-projects and next-actions. Of course, org helps there with > sparse trees and other functions to filter trees, but still, I found it was > too complex, albeit more specific and I did felt I was more "organized", > even though I was getting lost. > > So, I just let go of my obsession about the perfect thing and decided to try > a single Next Actions list, together with a Projects list. The next actions > is a single list with all the actionable items from all the projects. I've > lost the relationship between a next action item and a project, but I can do > this easily by just looking at the action, having the system tell me is not > that important. Usually, you define all actions for a project under the same hierarchy. You can decide how you want actions to be designated "next" (and projects to be designated "project") -- using keywords or tags and have a custom agenda command collect the next actions for you from all agenda files in a single list. -- Manish