Coming from early Kinkless and GTD reading, I have to say that I think single context is best, even though at times it's confusing. For *me* (not to get anyone's goat up) if I don't chose a single context, I have trouble juggling the context lists at all. Never mind trying to print them out for lo-fi carry... I'll have duplicates everywhere.
But, now, Tags, in my mind could be horribly useful. The reason I mention it at all, is merely because you can do so many things with a flexible tagging system. One, which can be extremely useful, is merely to get a list of all tasks related to a client (perhaps there are many projects with said client, over many different contexts etc.). So, typing &ElementalSystems could load all items currently available etc., for that particular client. Might be nice to know which tasks are out there related to this particular client. It's not really a context, it's not really a project. Sure, its' related to one dude, but perhaps you buy stuff from this client as well as serve stuff to this same client? A project mess can surely ensue.
Another wonderful tagging benefit would be to implement other decision factors. For instance, high cost, low cost. You could easily tag something $$$$ -v- $$. Then, added to the choices of errands, you could select a low $$ errand list (perhaps you're poor this month) and get thigns done that are needed still. The list is pretty endless.
So, I see tags as an added filtering ability, leveraging the idea of 'Focus'. To be honest, I'd love to see more serious reporting of completed and archived tasks. For instance, show me all the tasks associated with &ElementalSystems and all dates of tasks completed. Or, show me all tasks related to three contexts, and how many were completed last month as a pie-chart or bar-chart. [Somewhat useless, but perhaps you're spending all your time on the computer tasks, and never getting done your calls?] These types of things can be found out as you start to take data.
Ok, sorry I went off on a bit of a tangent there. My couple farthings worth, is to keep single context, for me it just makes sense that way, and add Tagging and support for filtering by tags, even focusing by tags. Wouldn't be nice to see all items in every context that is associated with "Sue" as previously mentioned? or, if you like "Low Energy"? [which is a GTDism]
Just my thoughts...
-Allen
BTW, there are 4 items that you are to use for choosing next actions in GTD...
- Context
- Time available
- Energy Available
- Priority
Omnifocus currently only consists of the first two in this list. And I suspect most people (including me) live out of the Project View, which isn't really leveraging the GTD habits... Speaking of Habits, if you're Covey-esque, you use a few more as well as this short list... Tagging would fit the bill there as well.
If the above list were implemented, a Focus session could include something like:
"Show me all available items with high priority that takes 30 minutes or less and are low-energy. [it's friday after all, and almost quitting time...]" Now, *that* would produce a set of data that would help you chose your next action...