I've had trouble figuring out exactly where 'Waiting for' lives in information model. I too have thought of it as a triage status. I wonder though if it's not really a part of the 'communication status' family.

Read, Unread, Needs reply, Waiting for.

That way, 'Waiting for' items can have their own triage status. 'Waiting for' something NOW versus 'Waiting for' something LATER versus a completed 'Waiting for', DONE.

Now the question is, how do we integrated 'Whom we're waiting for' into the model?

Mimi

On Jul 10, 2007, at 5:09 AM, Andre Mueninghoff wrote:

Hi Davor,

You may be thinking of the GTD triage status of "'Waiting for'". My
interpretation is that it is a type of Later. If I mark an item with
"'Waiting for'", in theory I know what I'm 'Waiting for' to be able to take
the next action step, Later. If and when custom triage status and
sections become available, I will implement 'Waiting for' immediately.
IMO, since Chandler is designed with GTD as one of its conceptual
sources, I think 'Waiting for' should be an OOTB triage status. This could
also draw more user adoption of those using GTD.

Enjoy, Andre

On Tue, 10 Jul 2007 00:05:36 -0700, "Davor Cubranic"
<[EMAIL PROTECTED]> said:
On Thursday 05 July 2007 04:57:43 Mimi Yin wrote:
Would it make sense to add a 4th triage status for something along
the lines of Archive?

Isn't there a triage status in GTD named "Get to it"? (It's been a while
since I skimmed the book.) Although, I guess it works sort of like
Chandler's "Later" without an alarm. Plus there is the "Reference
file", which sounds like the "Archive" status for contacts that you
mentioned.

Davor
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

Reply via email to