Thanks, that's exactly what I needed.
On Aug 5, 10:36 am, ike9898 ike9...@gmail.com wrote:
You could use 'depends on' this makes all the critiques except for
the next one 'future actions'. Once you complete the next critique,
mark it complete, and one from the future actions will become your
Create a project for Doing Critiques, add your first do critique
action as the next action then queue up all the other critique actions
on the one before it. This will mean that you have them all listed as
needing done but only the first one will show up in the Next Actions
list. Clutter = gone.
Hmm.. Any chance of quitting and coming back after a month with a clean
slate?
It sounds to me that the issue lies further up stream versus your GTD
system.
Before I stumbled on to GTD [in reading a book called Dreaming in Code] ,
I use to use make up these to do lists. It seems like wound up
I've got an answer, but you're not going to like it!
It sounds like you are 'time bankrupt'! You have taken on too much and you
can't meet your commitments as they fall due. (Don't feel bad - this is really
normal!) No matter how much you tinker with a fancy system, you're not going
to find
In any case, I think I've figured out a way to do this. If I make each
one dependent on the one previous, so that only the first one shows up
in the list. When I have to add a new critique, then I can simply make
the most current one dependent on yet another critique.
Now, all I need is to be
I've been using mGSD for a couple of weeks, and so far it's been going
pretty well.
I have what I think is a special use case, but I'm looking for ideas
on how to make it easier for me, or to see how other people have
solved it.
Here's my scenario: I'm a member of a writing group, which requires
