From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo de Moraes Serpa Subject: [off-topic/GTD]Only Next Actions list to rule them all ? Date: Wed, 21 Oct 2009 00:15:24 -0500 Message-ID: <1e5bcefd0910202215n660589c9h65ffe5603b1bf8db@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1961026048==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N0TXm-0006Yf-FJ for emacs-orgmode@gnu.org; Wed, 21 Oct 2009 01:15:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N0TXi-0006WW-3H for emacs-orgmode@gnu.org; Wed, 21 Oct 2009 01:15:29 -0400 Received: from [199.232.76.173] (port=37999 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N0TXh-0006WT-Kw for emacs-orgmode@gnu.org; Wed, 21 Oct 2009 01:15:25 -0400 Received: from mail-yx0-f177.google.com ([209.85.210.177]:56519) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N0TXh-0005Ds-BT for emacs-orgmode@gnu.org; Wed, 21 Oct 2009 01:15:25 -0400 Received: by yxe7 with SMTP id 7so151846yxe.25 for ; Tue, 20 Oct 2009 22:15:24 -0700 (PDT) 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: Org Mode --===============1961026048== Content-Type: multipart/alternative; boundary=001636c5bc25f38e6604766b1009 --001636c5bc25f38e6604766b1009 Content-Type: text/plain; charset=ISO-8859-1 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. So, basically, a bunch of projects and next actions, weekly review, collect-process-organize-review-do and that's all. Who knows, over time I might find that there's a better way... well, but Keeping It Simple is sometimes the best approach, even though org is so flexible that one might fall in the rabbit hole :) Thanks, Marcelo. --001636c5bc25f38e6604766b1009 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 en= d, it's all about what works for you, but I'd like to get some insi= ghts/opinions from you: For Next Actions, are you using a single list OR yo= u organize them hierarchically under each project (in the projects list)? <= br>
I started with the second one, putting each next action (TODO) item und= er 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 "or= ganized", even though I was getting lost.

So, I just let go of my obsession about the perfect thing and decided t= o try a single Next Actions list, together with a Projects list. The next a= ctions 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 t= ell me is not that important.

So, basically, a bunch of projects and next actions, weekly review, col= lect-process-organize-review-do and that's all.

Who knows, over= time I might find that there's a better way... well, but Keeping It Si= mple is sometimes the best approach, even though org is so flexible that on= e might fall in the rabbit hole :)

Thanks,

Marcelo.
--001636c5bc25f38e6604766b1009-- --===============1961026048== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============1961026048==--