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 Search Today's Posts Mark Forums Read

How do you handle task slippage? Thread Tools Search this Thread Display Modes
Originally Posted by Brian View Post
I'd probably make that task the parent item of an action group, with the hard due date attached. Then make items in the action group for each of the check-points you'd like, with start dates for when you want the reviews to pop onto your radar screen.

Would that work for you?
It would work for some things, and not for others. I tend to put a LOT of questions out and don't necessarily want something that's too top-heavy. Often times, the question is the only action. If I created a project for each of them, I'd sit around managing my GTD all day and not getting much done. I actually do tend to use this for multi-step projects today. It's the small one-offs that I'm trying to capture.

A more granular review system would be great. Like, if I could click on a task and say "review in 3 days", that would solve everything, I think.
You should think more about standardizing your own workflows and habits. Its more about you than the software in this case, i.m.o.

I don't think pushing due dates is a good idea at all. Set a due date and let it be hard. Then put a next review of e.g. 1 day. Now, if you make certain that you review every day; that project will be popping up every day and you can decide on a daily basis if you want to contact that guy and ask him how that task is moving. Use flags if you want, it doesn't matter (although flags can be used for individual actions). Again you must make absolutely sure you review all flagged items daily. Its about getting into a routine...
Originally Posted by colicoid View Post
I don't think pushing due dates is a good idea at all. Set a due date and let it be hard. Then put a next review of e.g. 1 day.
I agree on the due date thing, but I only do it because I can't see any way to do a review of 1 day. I can do that for projects, but that breaks down for individual tasks. I have about 50 individual items I'm waiting on an answer for. I slam them all into a single-action project, so I don't want to review each one every day. If the review process were more granular, this would work for me.
Yes, the granularity of the review mechanism in OF is flawed. Its a well known/discussed fact at the moment. I deal with "waiting" by using contexts like this:

@waiting for
@waiting for: person 1
@waiting for: person 2

I review these contexts daily.
The plain @waiting for is for misc stuff/people Im waiting for.
People I work with all the time (person1/2) I have specific contexts for. This system is separate from the flags/reviews for me and the trick is to review it on a regular basis. It also supports granularity on a task level.
It doesn't sound like anything is eluding me, but I have tried out a slightly revised workflow: I assign due dates only to very important items that have firm dates, and to any "Waiting" context that I'd want to tickle someone. In tha sense the Waiting due dates are not firm, but the rest are. This seems to work fine, though I would prefer some separate way of being able to designate when to tickle an item. I wait on a LOT of answers, so reviewing them all isn't very practical at the moment.
chrobb: you are right, there is no built in system that supports exactly what you need.

Perhaps you could combine the waiting-for-context system with review dates. But you would have to consistently name those waiting-for actions in a special manner so that you can separate them from non-waiting-for actions during the review.

During review, when you see an action called: "wait-for steve to repair the router" you can decide on a date when you want to phone the guy and ask how its progressing and set the next-review date to that.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Similar Threads
Thread Thread Starter Forum Replies Last Post
Need ideas on how to handle these concepts TwoGuns Applying OmniFocus 5 2013-01-08 05:54 PM
How do you handle with goals in OF? vitvit2002 Applying OmniFocus 1 2011-10-22 04:59 AM
How do you all handle clients? kampana OmniFocus 1 for Mac 2 2011-09-19 04:26 PM
OmniWeb can't handle HTTP? hhm OmniWeb Bug Reports 1 2009-05-23 04:25 PM
How do you handle reading? SpiralOcean Applying OmniFocus 4 2008-12-18 09:19 AM

All times are GMT -8. The time now is 12:03 AM.

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