From: Bernt Hansen <bernt@norang.ca>
To: Friedrich Delgado Friedrichs <friedel@nomaden.org>
Cc: Emacs-orgmode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Supporting non-stuck projects view with minimal effort
Date: Sat, 26 Dec 2009 11:30:34 -0500 [thread overview]
Message-ID: <87zl55r93p.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <20091226162047.GA5928@orion.pre-sense.de> (Friedrich Delgado Friedrichs's message of "Sat\, 26 Dec 2009 17\:20\:52 +0100")
Friedrich Delgado Friedrichs <friedel@nomaden.org> writes:
> Hi!
>
> Carsten Dominik schrieb:
>> On Dec 22, 2009, at 6:58 PM, Friedrich Delgado Friedrichs wrote:
>> >I've been thinking, the view of stuck projects is nice, but I'd need a
>> >view of non-stuck projects to complement it.
>> can you describe how you would use such a view in your workflow?
> ---Zitatende---
>
> Sure. I'll mostly use it in my reviews or mindsweeps. I am using the
> trigger list from the GTD book (also on
> http://wiki.43folders.com/index.php/Trigger_List ) so I'll start by
> looking through the projects that are already started to see if
> something requires my attention, then review the list of stuck (or
> unstarted) projects and see if I can come up with a next action for
> them.
>
> It's important for me that there are no items that occur on both
> lists, since that means I will review them twice (and might end up not
> reviewing them thoroughly). Without the list of unstuck projects I can
> only look at stuck projects and then at all projects.
Or you can look at NEXT actions which should only be unstuck project
tasks you can work on immediately.
-Bernt
next prev parent reply other threads:[~2009-12-26 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 17:58 Supporting non-stuck projects view with minimal effort Friedrich Delgado Friedrichs
2009-12-26 11:06 ` Carsten Dominik
2009-12-26 16:20 ` Friedrich Delgado Friedrichs
2009-12-26 16:30 ` Bernt Hansen [this message]
2009-12-26 18:14 ` Friedrich Delgado Friedrichs
2010-01-04 16:51 ` Carsten Dominik
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=87zl55r93p.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=friedel@nomaden.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).