Verfasst von Rolf F. Katzenberger am Fr, 2011-12-16 10:07.
My posting just sums up various types of contexts that I have encountered. I'm not using all of them myself: as Tony Garland has pointed out in the comments, you need to invest some time into figuring out what contexts apply to *your* work.
@jdog: If I understood correctly, you said you mostly work from home, using your computer and your phone. I guess you need to consider whom you can get on the phone on which days at which times, so one of the things I'd try is to set up some agenda-type contexts for specific people (@Dave, etc.) and collect issues there so you have them ready when you get the chance to talk to the respective person.
One additional approach that works for me, currently, is to have my *customers* as contexts (in addition to agenda contexts for specific people), like e.g. @ACME. I've found that my customers are sort of a context, because mentally, I'm "with them". So if my project list contains ProjA, ProjB and ProjC at ACME, all of the corresponding next actions go to the @ACME list. It felt a bit strange to me at the beginning, because I thought that I might mistake a project for a context, but now I'm sure that it's really the *customer*.
With respect to "priorities": they have been left out of GTD deliberately, and I'm thankful for that. I strive to weed out the bad stuff from my system deliberately and regularly. Using the Eisenhower Matrix (or Covey's equivalent), as mentioned in the posting that you recommended, is what I do on a regular basis, but only during the reviews of my system. Personally, I do not see added value for me in prioritizing things that survived this purging.
With respect to electronics: I've abandoned them long ago in favor of PostIts sticked to loose leaf dividers. I'm writing the contexts above the PostIts and just discard each PostIt when I've finished all items on it. I prefer that to using the whole divider for one context. So far it works.
@jdog (and Tony Garland)
My posting just sums up various types of contexts that I have encountered. I'm not using all of them myself: as Tony Garland has pointed out in the comments, you need to invest some time into figuring out what contexts apply to *your* work.
@jdog: If I understood correctly, you said you mostly work from home, using your computer and your phone. I guess you need to consider whom you can get on the phone on which days at which times, so one of the things I'd try is to set up some agenda-type contexts for specific people (@Dave, etc.) and collect issues there so you have them ready when you get the chance to talk to the respective person.
One additional approach that works for me, currently, is to have my *customers* as contexts (in addition to agenda contexts for specific people), like e.g. @ACME. I've found that my customers are sort of a context, because mentally, I'm "with them". So if my project list contains ProjA, ProjB and ProjC at ACME, all of the corresponding next actions go to the @ACME list. It felt a bit strange to me at the beginning, because I thought that I might mistake a project for a context, but now I'm sure that it's really the *customer*.
With respect to "priorities": they have been left out of GTD deliberately, and I'm thankful for that. I strive to weed out the bad stuff from my system deliberately and regularly. Using the Eisenhower Matrix (or Covey's equivalent), as mentioned in the posting that you recommended, is what I do on a regular basis, but only during the reviews of my system. Personally, I do not see added value for me in prioritizing things that survived this purging.
With respect to electronics: I've abandoned them long ago in favor of PostIts sticked to loose leaf dividers. I'm writing the contexts above the PostIts and just discard each PostIt when I've finished all items on it. I prefer that to using the whole divider for one context. So far it works.