From: John Hendy <email@example.com>
To: Bastien <firstname.lastname@example.org>
Cc: Org Mode <email@example.com>,
Marcelo de Moraes Serpa <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 08:03:53 -0500 [thread overview]
Message-ID: <CA+M2ft97mN=SPDjF8mtpi4kHcdw1mS4_K0ODfC=rwMn7fSOqTw@mail.gmail.com> (raw)
On Sun, Aug 19, 2012 at 10:54 PM, Bastien <email@example.com> wrote:
> Hi Marcelo,
> Marcelo de Moraes Serpa <firstname.lastname@example.org> writes:
>> What do you think; and what word do you use as your TODO keyword?
> I use
> NEXT(/) TODO(t) STRT(s) WAIT(w@) | DONE(d) DELEGATED(D@) CANCELED(c@)
I use something similar, but don't have a start or delegated tag.
"Next" is key, in my opinion and I use it for the same reasons as
Bastien. I have lots of todos and it's nice to scan through them
during the course of a week and mark those "next" that I know need to
be done... next.
Makes it much easier to do this regularly and then work on the next
items vs. identifying something to do next and then having to re-scan
the massive todo list every time for a good thing to work on.
I use "wait" as well, though one issue I've had is forgetting about
them. Though, I put my wait after the "|", which perhaps doesn't make
sense. Seeing Bastien's list makes me want to think about rethinking
that. Or adjusting the "todo" date to reflect when I need to follow up
about why I'm waiting or with to whom I've delegated the task.
next prev parent reply other threads:[~2012-08-20 13:04 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
2012-08-20 13:03 ` John Hendy [this message]
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).