Quote:
Originally Posted by zoisite
Please use my concrete example. How to avoid missing the „Buy hardware item xyz for Bob“ action when looking at the @Bob context when nothing hints/reminds me that there is an very important action that is related to Bob waiting in the @Hardwarestore context?
|
It sounds like this task actually has two separate actions which you could complete independently, one which you would do in the @Bob context and another which you would do in the @Hardwarestore context. In OmniFocus, you would model this by breaking down the task into those two subtasks ("Talk with Bob about buying hardware item xyz @Bob" and "Buy hardware item xyz @Hardwarestore").
In OmniFocus, you can decide whether you need to talk with Bob before buying the item (by making the group sequential), or after, or both (by putting in two Bob actions), or neither (by making the group parallel). Or you could even check in with Bob every week until the entire project is done (by making the Bob action repeating). None of this flexibility or clarity is possible unless you actually break down the task into its individual actions.
I suspect that might be one reason that Things needs multiple tags: when you can't break down your work into individual actions (since Things has no support for subtasks), you end up with multi-step tasks which you need to be reminded of in multiple contexts.
Does that make sense? Or am I missing something about how multiple tags would be helpful for a single action?