From: Bastien <firstname.lastname@example.org>
To: Marcelo de Moraes Serpa <email@example.com>
Cc: Org Mode <firstname.lastname@example.org>
Subject: Re: [OT][GTD] GTDish next action "todo" keyword, could that influence your productivity in any way?
Date: Mon, 20 Aug 2012 05:54:42 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <CACHMzOH=LeJs_1WPTOoWo_K_EPXYgeV5WLEE6c_OtvLfirstname.lastname@example.org> (Marcelo de Moraes Serpa's message of "Sun, 19 Aug 2012 21:59:48 -0500")
Marcelo de Moraes Serpa <email@example.com> writes:
> What do you think; and what word do you use as your TODO keyword?
NEXT(/) TODO(t) STRT(s) WAIT(w@) | DONE(d) DELEGATED(D@) CANCELED(c@)
The difference between NEXT and TODO is because I want to always keep
less than 10 NEXT items on a project, but I still want to distinguish
between TODOs and those entries without a TODO keyword. If I had only
TODO, there would be often too many entries without a TODO keyword.
I use STRT mostly in combination with a Read/Write/Watch tag, to spot
things I started to Read/Write/Watch.
I check WAIT once in a while for pending tasks.
The rest is quite common I guess.
I tried to avoid keywords proliferation and I stabilized this setup
over the years. My main issue was about this NEXT/TODO distinction,
but I found out it's more a matter of discipline than of semantics...
next prev parent reply other threads:[~2012-08-20 3:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 2:59 [OT][GTD] GTDish next action "todo" keyword, could that influence your productivity in any way? Marcelo de Moraes Serpa
2012-08-20 3:54 ` Bastien [this message]
2012-08-20 13:03 ` John Hendy
2012-08-20 16:32 ` Samuel Wales
2012-08-20 17:54 ` Bastien
2012-08-21 11:22 ` Mike McLean
2012-08-21 22:50 ` Bastien
2012-08-22 1:17 ` Mike McLean
2012-08-29 16:09 ` Marcelo de Moraes Serpa
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).