Putting it Context
Contexts are incredibly useful as is, but they are somewhat cumbersome to create and manage.
1) Some of my contexts are permanent fixtures relevant to all future tasks but there does not seem to be a segregated interface/page for creating contexts apart from the tasks they are related to. Because contexts only seem to persist on the interface as long as there are tasks tied to them, I have to continually retype the contexts whenever connected tasks are not found in current categories and Area of Focus.
Example:
I use a system of "ires" to divide the types of actions (in addition to typical GTD contexts.) My 'ire' contexts are Perspire (to do), Inquire (to educate myself on something prior to further action), Acquire (obtain or purchase something), Conspire (meeting or social interaction), and Require (delegate). I then use Area of Focus to appropriately divide these tasks into Home, Work, etc. Unless a context is tied to a particular task in my current area of focus, I have to create a new task, edit it, and type in the context manually instead of just selecting the context at the top of the interface and creating a new task.
I read in another thread that Nirvana might be switching to a database driven context system instead of free form. It sounds to me that would be a good start.
2) Having to edit tasks in order to add contexts is a bit inconvenient. My suggestion is to allow addition of tags via the 'create a new task' field, command line style.
Example: "Drill to center of earth #masterplan"
Would create a new task "Drill to center of earth" with context 'masterplan'.
I really like the idea of expanding this functionality to due dates and Areas of Focus as well, but contexts would be the most useful.
Comments are currently closed for this discussion. You can start a new one.
2 Posted by Proximo on 08 Sep, 2010 02:21 PM
@isolation42,
Nirvana mentioned that they will improve Tag Management. I have asked for a tag management area where I can rename tags/context and have all the task associated with them update automatically.
With a Tag Management area, you will not loose the tags/context you created just because there is no current task associated with it.
So I agree with you on this and it is something Nirvana is going to improve.
On a different note, I wanted to mention something about your context.
I like your "ire" concept but I think these are Tags and not Context. Context in GTD are based on the resource required for the task to be completed. Nirvana uses tags to create context which can be confusing but it does allow you the freedom of creating things outside the GTD context.
The context you described are not what GTD considers context as far as GTD is concerned, but the tag method Nirvana uses gives you the flexibility to do what you described.
I also noticed that you use "Require" (delegate) to identify some of your task, but in GTD there is a list dedicated to these task called "Waiting for"
The "Perspire" was another one I noticed that seems redundant. In GTD all the task in your Next List are actionable and therefore require you to do them.
Based on this, it seems the Require and Perspire tags/context are not needed.
Don't get me wrong, you can use tags to represent just about anything that would make you more productive. For this reason, I think it's a good idea Nirvana calls them tags because it gives you the flexibility to use them for context or any other identifier that you need.
From a GTD perspective it seems that every single task in your Next list would have the "Perspire" tag and every task in your Waiting for list would have the "Require" tag. Not sure why you would label them this way and not just put them in the correct GTD list.
What list do these task live in?
Just curious
3 Posted by isolation42 on 08 Sep, 2010 11:46 PM
Proximo,
Thanks for your thorough and thoughtful response! You are correct about my 'ire' categories. They are not, from a strictly GTD compliant POV, contexts. But in a non-strict way, they are.
story time:
I am a GTD evangelist. This week, I had a good friend who is engrossed in a start-up venture rebuff my attempts to convert him with a simple and effective statement. "GTD," he said, "is for well-adjusted balanced people. It helps people with compartmentalized lives and multiple objectives process a large number of diverse tasks and provides a framework for simplifying workloads. I am not a well-adjusted, balanced person. I have one objective, one context, and no home life or alternative considerations. What I need is a project management system." He went with SCRUM.
I was amused and saddened by (and a little jealous) of his narrow, intense ambition. But what I realized is that I am also not a well-adjusted, balanced person. Call it ADD or Aspergers or whatever, but anything requiring social interaction is automatically a high energy endeavor for me. Staying on budget by avoiding impulsive purchases requires 24/7 self-control. Alternatively, doing research, looking up reference materials or information retrieval is low energy and exhilarating for me.
What I've done is internalize the GTD process to take into account my idiosyncrasies. My internal resources ARE resources, and if I have a series of 'Next Actions" with different demands on my emotional reserves, attentiveness , self-control, or physical fortitude, these tags really do serve as a sort of context that allows me to switch hats and get a lot done because of whatever mode I find myself in. They are also a self-diagnostic, telling me when I really need to switch hats. (Well, I see I've been avoiding all of my projects requiring me to actually talk to people- guess I need to come out of my cave.)
By putting things I need to obtain in their own category- Acquire- it actually slows down my impulsive purchasing tendencies. It forces me to prioritize my tasks/projects by cost, even if I have not formally done so. I end up buying things WHILE my budget is in front of me, which is the best time to do so.
By separating out what I need to know for a task from the actual task- Inquire- I can better use time spent online or in meetings productively instead of meandering about websites or topics. It also means that I often find I am not the best person for a task early on as opposed to later, and can delegate more efficiently.
...and so on.
In response to a couple of your points:
"I also noticed that you use "Require" (delegate) to identify some of your task, but in GTD there is a list dedicated to these task called "Waiting for" "
Most of the time that is correct. Usually I need follow up on delegated items.But not always, and I just need the reminder to do the actual delegating. Also, items I need to obtain (Acquire) can be a 'waiting for' . Other triggers like "'Zombie outbreak." could be a "Waiting for" as well.
"The "Perspire" was another one I noticed that seems redundant. In GTD all the task in your Next List are actionable and therefore require you to do them."
All of the 'ire' tags are actionable, but it's the type of action required that interests me. I reserve Perspire for distinct endeavors that require physical effort or transportation.
tl:dr - You're totally right, but I have a subtle interpretation of GTD contexts suited to my own neurosis. I do not do this instead of GTD contexts, but as an added filter.
shalom
4 Posted by isolation42 on 08 Sep, 2010 11:52 PM
ALSO....
What did you think of my 2nd idea?
Allowing addition of tags command line style?
5 Posted by Proximo on 09 Sep, 2010 01:39 AM
@isolation42,
Thank you for sharing your though process on this. You may not consider yourself a balanced person but you sure sound brilliant to me. :-)
Great example of using what works from GTD while making the adjustments you require for productive work.
Tags command line = Love it.
David McLaughlin closed this discussion on 09 Feb, 2011 09:47 PM.