The Omni Group
These forums are now read-only. Please visit our new forums to participate in discussion. A new account will be required to post in the new forums. For more info on the switch, see this post. Thank you!

Go Back   The Omni Group Forums > OmniFocus > OmniFocus 1 for Mac
FAQ Members List Calendar Today's Posts

 
An idea for "Awaiting" Thread Tools Search this Thread Display Modes
Many people on this forum have written questions and ideas about how to handle actions where you are specifically awaiting a response from someone else before you can proceed further.

At first I wondered about this a lot too, but now I have taken the attitude that nothing is actually ever in "awaiting" status... it is always an action that I must do. So if I have given Joe my hammer and must wait for him to return it to me before I can assemble my dream mansion, then my action item in OF is something like "follow up with Joe to return hammer". I assign a certain start date and a certain end date to make sure that I follow up by a certain time if I have not received the hammer from him by that time.

I just thought I'd throw that out as a suggestion to other OF users.
 
I agree. That's exactly how I do it. Although, I only add start and end dates when absolutely necessary.
 
Yes, I would do it that way too. I would call it something like "Receive hammer from Joe" and give it a context of "Waiting for ...".

If the project is sequential, it effectively stops progress until Joe returns my damn hammer.
 
 




Similar Threads
Thread Thread Starter Forum Replies Last Post
Missing "ToDo" in "Due" area [A: Poster confused about how Due field works.] morkafur OmniFocus 1 for Mac 3 2012-05-24 02:39 AM
German localization problems, WebDAV iCal export due: "fällig" vs. "Fälligkeitsdatum" FatalError OmniFocus 1 for Mac 5 2011-04-08 06:32 AM
Planning / Reviewing - a wish for "idea groups" janT OmniFocus 1 for Mac 2 2007-09-29 05:06 PM


All times are GMT -8. The time now is 02:18 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.