If you're like me, you probably have a series of potential "sub-contexts" that are nested within your umbrella @computer context. These sub-contexts could be things like @code, @email, @web, @writing, and so on.

Even though you *do* all these things at the computer, it's likely that you have different mental contexts for each--especially for highly focused activities like writing or programming. It'd be way unproductive to keep jumping between writing code and writing emails. Your brain has to make a context switch every time you move from a @code NA to an @email NA, and you're losing valuable cycles.

If you've got a separate context for each mental context, you can sit down and say "okay, I'm writing this email to Sam... what other emails can I write?" or "I'm writing this article... what other articles do I need to be writing?"

The side effect, of course, is that you have that many more @context buckets that may contain a Next Action you'll be able to do at your computer. But by deciding on a sub-context: "I'm going to work on @code tasks for a few hours," you can filter that giant @computer NA list down to a much more bearable sub-list.

Also, if you've got a laptop, you've got two built-in subcontexts already: @online and @computer-anywhere. It's useful to have a separate list of things you can do at your computer when you're stuck on a plane with no web connection.

Here's a really good thread on contexts:
http://board.43folders.com/showthread.php?t=445

Mine are on the 2nd page. They've evolved somewhat since then, and I've grouped them into five meta-contexts now, but it's still pretty much the same thing.

I think when you look at the way other people have done it, you'll get ideas for how to do it yourself.

Okay, I think I understand. Here's my context list now after a bit of brainstorming

@School
@Homework
@Home
@Errands
@Work
@Calls
@Design
@Computer (General)
@Writing
@Programming
@Meta (System Maintance, basically, like checking my tickler, and stuff.)
@Nocontext (Anything I can just do at any time.)

So, now that I have this, I can take my next actions and contextualize them into little sublists so I know what to do next for whichever project I feel like doing.

I think I get it, but I'm not sure. I've got to replace my copy of The Book today (left it in my bag and my cat whizzed on it,) so I'll re-read it and see what David has to say about where to go from here.

Black Belt Productivity recently finished up a series where they summarized each chapter. You might give that a quick look.

The Dr. Contextlove post might help, too. It helped me a ton.

I've been trying to figure out the same thing, that is, what context I should be using for my upcoming return to school.

The problem I've found is that contexts seem to be two different things.

1) Physical locations that have available actions (Like my @Errands)

2) Types of actions.

The problem with this is that as a student with a laptop and a Teaching Assistantship, virtually everything that will have to do (other than class meetings and office hours) can be done ANYWHERE at ANYTIME.

I also am of the opinion that we geeks (who love to classify more than anything) can end up making the context problem into a time-wasting situation, which means the whole system is broken. So it's vital to only have as many context as is needed to quickly and intitutively break down your tasks. Less is more, in my opinion.

My current mock-up, not tested at all because it's summer break and I'm washing dishes, has nine contexts divided into to meta-groups

Move:
-Call
-Email
-Errand
-Household

Think:
-Ponder (decisions, brainstorming)
-Research (from library to google)
-Read
-Outline (planning stage for ALL projects)
-Write (the "doing" or "finishing" stage for most projects)

In theory, most projects will have actions that move from Ponder to Research to Read to Outline to Write. I also know that this is the way that my mind works so, the hope is, I won't spend to much time contextualizing. Actions will naturally have a flavor to them.

I'm considering the possiblity that I will also need a "Grade" context as I'm going to be teaching assistant and predict that a great deal of my time will be used grading. An action that is quite "Write" or "Read" Fellow TAs, what do you think?

Who knows what's going to happen when I hit the ground though.

I tend to (mis?) quote David on contexts and other GTD aspects. "Have as many as you need, and as few as you can get by with."

Yours seem reasonable to me, if they work for you. You can definitely read, research, outline, write, or ponder in the same places, but if those diverse activities each require a different mindset, then they make sense to be different contexts.

The only concern I'd have is that you'll find yourself with a block of time, in, say, the library (where you can do any of these), and you'll have several lists to go through to choose the next action.

Not necessarily a big deal, though. One of the hallmarks of GTD is that it lets you use your brain to choose the best action, not some arbitrary priority schema.

The @Grade contect might be a good one since it's (hopefully for your students) somewhat timebound, and requires you to be with the stuff that you're grading. Although for all I know that's all on your laptop too.

I think you can definitely get a nice start with the contexts you've chosen. Once you're at it a while you'll start to see if some should get the axe, and if there are new ones to add. I think the key to contexts is to try not to overthink it.

I'm kind of a minimalist in this regard, at least right now. I've got @work (which means the office or my work PC wherever), @home, and @ errands. WHen I have a lot of calls to make that don't require me to be at a computer, I'll add @calls.

Good luck and let us know how it goes!

I'm new to GTD. Working on creating contexts, getting ready for initial physical & mental gathering. I shall ponder the dynamic possibilities of @Meta context.

cfthrifty