For those not familiar with GTD, David Allen’s highly successful personal productivity approach, get this book (please note this is my affiliate link, you can of course log onto Amazon yourself), and read the first three chapters. It’s worth it, if only for the different way you’ll be looking at your work and your life.
GTD refers to contexts, areas or situations in which you execute certain work. Context are one of three elements that help determine what you can best do next. The methodology suggests to try and remain in a context as long as possible to work optimally.
Why contexts matter
The idea of contexts is based on money concept of our modern production oriented society: working in a production line, executing a comparable task over and over again. The reason for this is simple, and still applies today: changes in tooling, sets of tools used in the execution of a task, cost time. This is non-productive time since you are not actually producing during the time allotted for the tool change. To optimize the production time, you minimize the need for tooling changes as well as the time required to change the tool. To put it simply, if you’re at your desk behind the computer in your word processor, stay there as long as possible.
The production belt or production chain is the ultimate tooling change optimization: you never change the tools, but the product, solution or whatever you’re working on in its different stages of completion moves through a set of tools.
Tool changes and sequential execution
Often contexts are related to tools or their modern day equivalents. Certain activities can only be executed in a certain environment, or requiring a certain tool, system, software or person only available at a certain place.
Imagine I’m working on a project. I have a task list with a certain sequence and dependencies. I first need to write this paper, then have it read by that person, then present it to that meeting, then have it signed of by that person … If I sequentially run through those activities, I will likely execute a good project. But, I will have a lot of non-productive time and idle time as well. After all, there’s a lot of tool set changes involved and a lot of waiting as well. I have to give the reviewer the time to review, I need to prepare the presentation, I need to see someone for his or her signature. Not really very productive at all.
In all of this, I’ve lost a lot of time. If I have more than one project, it pays to remain in a context to execute as many as possible the tasks I need to perform in that context prior to jumping to the next context. For example, it seems wise to first write all the papers you need to write prior to starting the development of your presentations. The tool switch cost from writing app to presentation app is minimized.
why contexts don’t always make sense
But this doesn’t always make sense. Certainly not in creative work.
Think about the following situation and its associated cost. I’m working on a project which requires me to write both a report and a supporting presentation. I’m also working on another, unrelated project with another presentation due. Which of the following would cost me most?
The tool switch or the mind switch? A mind switch requires me to abandon a train of thought in favor of another, while a tool switch requires me to abandon a set of tools in favor of another. I’m convinced that in certain cases the productivity impact of the mind switch is more significant than the productivity impact of the tool switch.
An illustration of the difference between mind and tool
Let me clarify: imagine you are asked to write a number of proposals. Part of this may be retrieving proposal templates or prior written proposals from a repository. The context here may be for example “online - proposal database” and for this activity a tool change is not appropriate. You get out of the proposal database what you need for the different proposals.
Once you have the templates, you start developing and writing. An important “meta-context” for me is mind mapping, but this is a meta context in that it often requires me to go through multiple tool switches during the activity. I do the mind mapping in Mindnode Pro, but I will frequently be switching back and forth between my browser, my notes (which I keep in text files in Dropbox) and the mindmapping software. For me, the frequent tool switches I make are actually part of the creative work. I can do this because the tools all together form the creative analysis and development context for me.
In essence, my context is no longer a unique context of one tool, one activity or one environment, but rather a set of complementary tools which together allow me to work towards a certain result.
UPDATE - A number of better GTD experts than me pointed out that there is no explicit mention of remaining in a context for as long as you can. I stand corrected, they are right. However, switching context too frequently often carries too high a tool switching cost, unless you have all your tools arranged in order to optimize efficient and effective use. Therefore, while it may not be explicitly mentioned, I do feel remaining in context is an important aspect to the entire productivity concept.