From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: [off-topic/GTD]Only Next Actions list to rule them all ?
Date: Wed, 21 Oct 2009 00:15:24 -0500 [thread overview]
Message-ID: <1e5bcefd0910202215n660589c9h65ffe5603b1bf8db@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1499 bytes --]
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.
[-- Attachment #1.2: Type: text/html, Size: 1590 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
_______________________________________________
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
next reply other threads:[~2009-10-21 5:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 5:15 Marcelo de Moraes Serpa [this message]
2009-10-21 5:51 ` [off-topic/GTD]Only Next Actions list to rule them all ? Manish
2009-10-21 12:13 ` Desmond Rivet
2009-10-21 12:22 ` Bernt Hansen
2009-10-21 18:06 ` Marcelo de Moraes Serpa
2009-10-21 18:30 ` Marcelo de Moraes Serpa
2009-10-21 19:05 ` Matt Lundin
2009-10-21 19:15 ` Bernt Hansen
2009-10-21 22:15 ` Marcelo de Moraes Serpa
2009-10-22 1:48 ` Bernt Hansen
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=1e5bcefd0910202215n660589c9h65ffe5603b1bf8db@mail.gmail.com \
--to=celoserpa@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).