Contexts should be left navi menu, not tags
I understand that I can implement "@" contexts through tags, but
one thing I have never found in a GTD system before is a
infrastructure where I can create the contexts I want, then add
tasks to, and view tasks in those contexts quickly. Instead, I
would like to use tags separately to group projects/tasks by other
qualities: whether they are personal, or for work, etc.
Ideally, I would like to see Contexts the same way you currently have "FOCUS" in the left hand menu, even above the Active Projects list. I think these contexts would need to be customizable, as the ones in Allen's book aren't necessarily right for everyone, but if this were a feature, it would set Nirvana apart from any other GTD interface I've ever seen.
Furthermore, while I imagine it might be a pain in the @$$ to program, what would be great for me is if these contexts became buttons or checkboxes on every task I create, so that I could plan a bunch of tasks for a project, then quickly assign those tasks to the contexts they are appropriate for.
Thanks, and happy holidays,
Zach
Support Staff 2 Posted by Christiane Magee on 06 Jan, 2010 03:13 PM
Hello Zach... thanks for your comments and suggestions.
We will be be implementing a feature called AREAS OF FOCUS which would be like uber-contexts if you will - i.e. HOME, WORK - so when you want to focus on personal/home tasks only, you simply just need to switch to that focus and you will see only your HOME tasks. How tasks are assigned to that area of focus is still in development, so if it will be done via a checkbox or another way is to be determined.
As for your custom contexts - another feature we are looking at is SMART LISTS. These are lists that you can define a set of rules so that certain tagged tasks will automatically filter into these lists. So for example if you were to have a smart list with the rules "show all tasks with tag
errand+grocery" any tasks that are marked with these tags will appear in that list.Once these features are in place, I think they'll address what you are looking for.
thanks!
3 Posted by Proximo on 12 Jan, 2010 07:17 PM
Context are Areas of Focus.
If you look Context up in David Allen's book. You will find that context are considered Areas of Focus and Resource Requirements.
This can be accomplished many ways. If Nirvana decides to add an Areas of Focus to the Navi, I would like this very much. It must be customizable by the user to fit their different areas.
You will still need Context and the ability to use more than one.
The other way to handle this is to use Context for Areas of Focus along with Context for Resources. This works but I think it's simpler to have a dedicated Areas of Focus section where you could view your task and projects based on that area of focus. This to me is simpler and prevents the confusion many have with Context. This will allow you to use Context to identify your resource requirements without having to use an additional context for the area of focus. Tags come in handy to add further triggers for task.
In the example above. I would arrange it as follows.
Area of Focus = Personal/Home
Task Context = @Errand
Tag = Groceries
This allows me to have a focused environment that currently only shows my Personal task/projects. I also filtered my task by the context @Errands because I am about to leave the house and want to see what I can do while on the road. The tag further identifies this task for even easier access.
Let's say that I have not left my home yet but my wife mentions that we need Sugar. I can open Nirvana, make sure I have Personal set for my area of focus and search for the tag called "Groceries". This is much simpler than having to filter by @Errand and look over all the @Errand task to find Groceries.
So I am a firm believer of:
Tags are powerful when allowed to be used more openly as it makes sense for each individual.
4 Posted by MarcinGTD on 13 Jan, 2010 08:35 AM
Areas of focus are well explained in latest book by Allen "Making it all work"
Areas of Focus are 20.000 ft. perspective of Horizons of Focus and they are connected with life's maintenance (aka areas of responsibility).
So Area of Focus will be "JOB" and contex "Office"
where Job is being your area of responsibility (performing specific task) and focus (making a living) and "Office" being a place where said task can and should be performed (tools at hand etc.)
5 Posted by Proximo on 13 Jan, 2010 03:41 PM
MarcinGTD,
I agree with you on this. David clearly says that Context are a location (Area of Focus) or a resource in his first book. So your comment is 100% correct. Weather we call in a context or an Area of Focus is not important. What is important is that we identify our task by an Area of Focus in order to have "Mind like water".
I do exactly what you describe today. I rather have the Area of Focus as part of the Navi and separated from context because it's simpler to understand that way. At least for me it is. I have used context for both Areas of Focus and Resources as David suggested in his first book, but in the system I use today, I am able to setup Areas of Focus as a separate function from my context and I like it.
Again, it achieves the same thing and It really does not matter how you label it, but the concept of having Areas of Focus is what matters.
I would love to see Areas of Focus handled separately from context in Nirvana. I still have the ability to filter my list by an Area of Focus and a resource using either method, but I like to click on "Work" in the Navi and have the entire system switch to my Work focus or any other focus that makes sense for me.
In your example my Area of Focus is called "Work" and in this area of focus I have many context that filter out my task. @Office for things I must do in the office but it can also be @Internet. In my line of work I am not always in the office and do many things on the road using my laptop. So knowing that something can be done @Internet while in my "Work" focus is important because I can stay productive while on the move. @Call is another example of a task I can accomplish anywhere I have my cell phone.
If I need to upgrade a Server, I would use the @Office context because I must be in the office to accomplish this.
GTD is simple and I think even David himself can over complicate things with his use of words. One thing I wish David would do is use straight talk and quit sounding like some Philosopher. There is no need for this and it makes things sound harder than they really are.
You also don't need to adopt 100% of GTD but only the parts that work for you and make you productive.
6 Posted by Andrew on 13 Jun, 2010 04:51 AM
If I use Areas of Responsibility as Contexts, then in Projects I would need tasks within a project to be able to have different A of R (Contexts). My project might include phone calls, emails, errands, etc.
7 Posted by Proximo on 13 Jun, 2010 12:12 PM
This is just my opinion but AoR was not designed to be used for resource context but more for location context.
This of course is my opinion, but I think the Nirvana development team had the same thing in mind when they designed AoR. I guess you CAN make it work any way you need it too, but there may not be as much flexibility.
8 Posted by Glenn on 24 Jun, 2010 02:17 PM
I agree with Proximo that AoR isn't designed this way, and further, that attempting to do so is also mixing apples and oranges.
That said, something I'd like to be able to do is group tasks on a page (like Next or Today) by resource context, which would give me a quick snapshot of what I might tackle next.
I can't figure out how to do this. Is there a way to do this grouping, or if not, will there be?