Multiple context to one task

aspirin85

12/18/2013 16:43

I would think it is possible to do a task in multiple context. since most handphone have internet function. hence it make sense to add the ability for one take to take multiple context. this also allow flexibility to user own discretion to use this functionality.

It would also be good to be able to run through the context in the main sidebar since usually what take we decide to do for that particular moment is decided upon by what context we are in. For example, if I'm on my phone and have 5 mins, i would like to scroll through the context of phone and see if there is any action within the phone context that can be actionable. hence it make sense to be able to select the context right at the most convenient area, i.e. the sidebars

Report

•   (积分：70)04/03/2014 21:19
  1 floor

  That's usually a sign that your contexts are to specific. You would need to make a more specific use case that this would address.
  Report
• ike9898  (积分：170)04/07/2014 20:03
  2 floor

  I would find multiple contexts useful. There are some things in my life that I can do from the office or from home. Many people wouldn't use this functionality, but it would be nice to have the flexibility.
  Report
• paulogazola  (积分：170)05/02/2014 17:44
  3 floor

  I undestand the multiple context way of thinking, but i think a hardcore GTD view of contexts is more "correct".
  
  I have the following contexts: atHOME, atWORK, atHOME.COMPUTER, CONTACT.
  
  The interpretation is: "when I am in the context named I can do any task of the following tasklist..."
  
  In my example, atHOME is offline, and atHOME.COMPUTER is online (desktop/mobile/etc), but for personal things. Context atWORK is always in computer, but I separate from atHOME.COMPUTER, beacause it represents professional stuff (=sitted in the office).
  
  The great app Things calls contexts "Responsabilities", but I think context is really a CONTEXT: you transits from one to another (never 2 at the same time). For the rest, I think TAGS are great (keeping them simple, of course). I miss some improved TAG funcionality on DOIT. :(
  Report
•   (积分：140)02/22/2015 22:56
  4 floor

  +1
  Yes I am hampered by the fact that DoIt does not allow multiple Contexts. I have a Task 'Find best graphic card for John'. Ideally, I would like this under Contexts: 'Work Office', 'Home Office', 'Online' and 'Errands' because any of those places are suitable for pursuing this Task. I have it in 'Work Office' which means that I might forget to ask about it when I am in the city visiting my favorite computer parts store.
  Report
• Folke  (积分：2425)02/24/2015 01:07
  5 floor

  Doit actually has multiple contexts - they are called Tags, but unfortunately they are quite useless (hard to trust) as they are invisible unless you open the task to check. Also, they are in no way coordinated with Doit's main context feature, called Context.
  
  As for the usefulness and GTD correctness of using multiple contexts I can agree with @paulogazola that single contexts is what david Allen describes - but this is no great wonder, considering the fact that GTD was designed in a way that allows it to be implemented on regular paper. You cannot put a task on more than one list (unless you are prepared to manage duplicates), hence single contexts is the only possible form when using paper. However, the spirit of GTD is to make the most of the present situation. By considering context, energy, time, priority etc (which needs to take place mainly in your gut, especially if you use paper) you decide what to do. I see no violation of GTD being made if some of this is implemented in a more structured way in a computer app.
  
  As for the possible uses of multiple contexts we have heard above of the use case where alternative contexts could be indicated by separate contexts. Personally I would not do that. I would rather have (and do have) a special last resort context for "anywhere, anytime, with anybody/nobody, and with no unusual tools" (I call this @Info)
  
  For me, the more attractive use case for multiple contexts is to identify all the situational REQUIREMENTS tidily and exhaustively. For example, I have a context called @Person, meaning that I need to do this task with some special person (face to face or by phone etc). I have another context called @Out (i.e. errand). Obviously some tasks require me to be @Out with a @Person, but this cannot be managed with single contexts. Some people then invent new "combo" contexts like "Out with a Person" etc. I have seen people give horrendous examples of mile-long lists of contexts, including super-combos like "In the Park with Anne and the Dog", "In Town with Anne and the Dog", "In Town with Anne without the Dog" etc. It would be much simpler and neater to have a Tag/Context for Dog, another for Anne etc and apply whichever things are REQUIRED in order for you to be able to do the task. If the Dog is needed, tag it with Dog, otherwise leave the tag out. Just because it is possible to do the task with the dog present is not reason enough to tag it Dog. Most tasks can be done with a dog present, a phone present, a desk present etc. More economical to just tag for the REQUIREMENTS.
  
  A very neat and useful complementary feature to multiple context tagging would be elimination filtering (i.e. NOT filtering) - be able to hide tasks that REQUIRE some contextual factor that is presently unavailable. Why show things on your Next actions list that are not actionable at this particular moment?
  Report

Only the group member can speak, Join