Quote:
Originally Posted by colicoid
I don't understand why you keep these projects on hold. Then you won't know who you are waiting for. If you kept them active and assigned the task "waiting for X to phone me back" to a special "waiting for:X" context you would have a lot less stalled projects and your action-less projects would be easier to find. Just a thought...
|
Actually, the OmniFocus manual itself suggests assigning "waiting for" contexts to an "on hold" status, which is what I've done. For me, this makes sense, since any project with a next action that is waiting for someone isn't really available for me to do anything on it.
Practically speaking, I suppose it's true that I could make those contexts active instead and simply keep them collapsed when working in context mode. But the disadvantage here is that they'd still show up as available actions if I decided to sort by anything other than context.
But if I were to do that, then what would be the point of having "on hold" contexts at all? I mean, isn't the whole point of assigning contexts to "on hold" status that those actions (and therefore those projects) are stalled until something changes? For me, that concept makes sense as something separate from projects that are simply waiting on me to decide the next step.