From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: [off-topic/GTD]Only Next Actions list to rule them all ? Date: Wed, 21 Oct 2009 08:22:54 -0400 Message-ID: <87y6n57x7l.fsf@gollum.intra.norang.ca> References: <1e5bcefd0910202215n660589c9h65ffe5603b1bf8db@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N0aDY-0005lM-5J for emacs-orgmode@gnu.org; Wed, 21 Oct 2009 08:23:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N0aDU-0005gG-Ak for emacs-orgmode@gnu.org; Wed, 21 Oct 2009 08:23:03 -0400 Received: from [199.232.76.173] (port=33228 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N0aDU-0005fz-47 for emacs-orgmode@gnu.org; Wed, 21 Oct 2009 08:23:00 -0400 Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:59712) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1N0aDT-0003ve-Ro for emacs-orgmode@gnu.org; Wed, 21 Oct 2009 08:22:59 -0400 In-Reply-To: (Manish's message of "Wed\, 21 Oct 2009 11\:21\:38 +0530") 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: Manish Cc: Org Mode Manish writes: > 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. I define NEXT actions as a tag on some TODO item under the project hierarchy. I then pick NEXT actions off of the custom agenda view for NEXT actions using agenda filtering to limit the total number of things I'm looking at. -Bernt