@anywhere and @calls contexts
I always carry my phone with me, I therefore figure I could put all my call actions in my @anywhere context and get rid of the @calls context.
Has anyone else done this?
Iv read similar debates on this site before. One common reply is that its useful to bunch together actions of a similar type because you kind of get in a groove doing a certain type of action. So if you have to make calls, get a drink put your best foot forward and run off 10 calls in a row, then theyre done.
Since I have email and phone and word processing at home, work and on the move with my smartphone + laptop, 90% of my work should be @anywhere. But since its not helpful to have one list with 200 actions on it I break it down a little more.
@anywhere means @anywhere.
@anywhere = @boss OR @meeting-with-client OR @errands OR @lunch-with-my-wife OR @home OR ...
Originally Posted by iamjud
I don't think I should make calls in any of the above mentioned contexts.
Maybe you shouldn't, but (if like me you have your mobile with you most of the time) you COULD. Even if you have a calls context you would be in this situation anyway. You could be @meeting-with-client and @calls because you've got you phone in your pocket.
Originally Posted by TesTeq
I see how it might be useful to have a calls context if you have to regularly make 10+ phone calls a day (I don't have to myself).
Personally I like to keep them seperate because my lists are long enough that I might miss something otherwise. That being said, I think that as long as you are not @romantic dinner you should be alright.
Focusing on the client needs to provide him the best solution.
When I'm at the meeting with my client I'm turning off my mobile phone because the purpose of the meeting is to focus on the client needs to provide him the best solution. For me it would be inappropriate to make calls during the time reserved for my boss, client, wife etc.
Originally Posted by iamjud
I understand your issue and often feel the same as I have my iPhone with me so can make calls anywhere. Same applies for email these days, and I do a lot of text messaging.
I've been toying with the idea of changing my @calls context to @contact which would mean contacting a person via any method, leaving me to choose how I do it given current circumstances, e.g. phone, email, text, even face-to-face if I happen to be close by (say with internal office colleagues).
Might give this a try.
I wouldn't recommend this because thinking would be required each time you look at the list. You should be doing your thinking when you decide your next action, not while you in the war zone. There you have no time to think; you need to have already thought.
Originally Posted by PeterW
Even if you carry around your phone 99% of the time I still think you should have an @Calls context. This context means I need a phone--any phone--to complete actions on that list. If you don't have your phone or if you're on a plane and can't use that function of your phone you put that list away.
@Calls is not @Anywhere
You cannot use your phone (to make a call) in flight on a commercial airline. If your phone is broken, or the battery is drained, you cannot make a call and would be restricted by the context.
I find @Calls to be a helpful context regardless. I switched to an iPhone a while back and toyed with an @iPhone context instead of @Calls. I found I missed the breakout of phone calls as a separate list.
I'd agree with you in principle and in my last job, I flew somewhere every week so having @calls would make sense. In my current role, I don't fly and aside from a brief weekly meeting, am mostly at my desk, in my car driving to/from work, or at home and always have my iPhone with me. So for me, @contact would probably work. I have not needed to filter my tasks for @calls in the past 12 months since taking up GTD workflow.