Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
Waiting for -- what level list?
bengoshisan | May 22 2007
Dear All, I was thinking about "waiting for" items. Is that a "project level" or a "NA level" list? The problem occurred to me when processing emails I send -- I am waiting for an answer, which could come in 30 seconds, if the partner is on-line, and could come in two days or a week, if they are on holiday. Now, in the first case, it is enough to jot an item to the waiting for section of my NA lists, while in the latter, it is rather well placed among a list in projects. Or, for that matter, it could go to my diary. What do you think? (And, of course, I mean that I don't know when the answer would come. 11 Comments
POSTED IN:
 I treat it as a NASubmitted by Marmotte_masquee on May 22, 2007 - 9:14am.
Hi I treat a "waiting for" as a NA, because sometimes its what makes a project go further or stall. Example: If I send an email with a text that somebody must revise, I have a context card called "@waiting for" and I add something like: "Revision on text from H". The person may reply in 60 minutes or one week. If the answer comes back in 5 minutes, then it seems like a waste of time to write the "waiting for" NA down, but I'd rather process all my waiting for the same way, so nothing slips into the cracks and I don't spend time thinking "Is this going to take enough time to come back that I should write it down?" on a card. I just take it out of my head, no matter what the topic is. I cannot find an example of a project that would BE waiting for something. To me, waiting for something is always tied to a lower level. Like Berko said, if it involves a deadline, its better if it is in a hard landscape too in some way. » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
