next »

[Jamie Phelps]

In light of this thread about post-GTD productivity, I'd like to mention something that I have been doing for a while. I don't really keep context lists. If I have a ton of phone calls to make or errands to run, I might make an ad hoc list of those so I don't forget one. I work mainly from my projects list. (I think Scott mentioned a similar workflow.) Each day, I look at my projects list and decide what I'm going to focus on for the day. Then, if I feel the need, I make a today list (a la Patrick) containing a mixture of projects that I'm going to work on and specific granular tasks I'm going to do. So, I might make a list like

* Check PO Box mail
* Call Bob
* Web Design Project X
* Programming Project Y
* Take out recycling
* Deposit checks in bank.

My today list is always less than ten items long and always fits on an index card or a quick list in my iPhone's Notes app or Backpack. The reason this works for me is that programming and web design projects are pretty easy for me to intuit what the next action is. If it's not immediately obvious to me, then I break it down into something smaller.

[Brad Blackman]

It's funny, for me it's almost the opposite. I don't really do things based on project but group things by context. How I actually *do* everything, I don't really know. I guess I've gotten sloppy in my productivity, not really thinking about it closely anymore. This is why I think sometimes GTD can make you work harder instead of more efficiently: you can get so bogged down in assigning things into neat little contexts (or a billion of them, if you go nuts like I have) instead of just doingthem.

I'm starting to think I need to overhaul my system. That, or just forget it and just get all that crap done that needs to get done. GSD anybody?

Oh and as far as contextualizing your projects? You could do this:

@ ERRANDS
* Check PO Box mail
* Deposit checks in bank.

@ HOME
* Take out recycling

@ CALLS
* Call Bob

@ MAC
* Web Design Project X
* Programming Project Y

That's just grouping together like tasks, which ties in with what Tim Ferriss is all about. If you're in a spot to make phone calls and that's it, then pull out your list of calls you need to make. If you're out running errands, better keep that Errands list handy, so you can batch them together and save gas.

Are you thinking the contexts are too anal and nitpicky or something?

[Bookworm]

I think contexts might be more critical for people who don't spend most of their workday at their desk.  If you're a frequent business traveler or spend most of your day in meetings, it might be helpful to have actions tagged with @Email or @Phone context. 

I've tried using contexts in the past, but seemed to always have too few or too many; never found the sweet spot.

[Jason Echols]

I am more like Jamie...My projects list is my key.  Biggest reason is that I work out of the same machine at both work and home.  It is just easier to work that way with one "command center", if you will.

[James Mallinson]

Never used contexts, though that may have something to do with the amount of tasks I have. There is no point splitting up my list and, for instance, having a @phonecalls context when I might only have one or two calls to make. I can really see how invaluable it would be if you have an extensive list however.

Nowadays, if I ever need to group stuff it's dependent on the relevant role/responsibility. For instance, grouping all the cleaning and de-cluttering tasks under the role of home-owner.

[Jason Echols]

For me, as technology advances, contexts become more and more irrelevant.  Since must of us who are interested in productivity carry smartphones with internet service these days, @computer a @phone are pretty much everywhere.

So I really no longer need contexts for things I can do at my phone or computer.  Today I think more in terms of @home or @office.

[SteveC]

Like, I suspect, many of us, I've played with my contexts list too much over the years.  I have sort of settled down on the following (note that my work and personal systems are totally separated -- partly through choice -- don't want to think about work when I'm not there -- and partly due to security and confidentiality issues)

At work --

• Desk -- for most things.  Includes emails
• Walkabout -- effectively 'not Desk'
• Waiting for -- obvious

At home --

• Phone -- see explanation below
• Garden -- includes things I have to do in the garage such as bike maintenance
• Indoors -- anything indoors not computer based
• Computer -- obvious

The reason for keeping a separate Phone list is that there is a particular class of phone call I don't like making.  Mostly to people I don't know well.  However, if I have several such calls to make, I only have to get over that issue once!

S

[spoothed]

I love your context "Walkabout" vs. "Desk!"  I can definitely apply these to my situation in a retail environment.  It'll make it easier for me to class these in RTM.  I frequently use their location field as my context, but this may be helpful in GTD for retail.