Forum

  • If you are new to these Forums, please take a moment to register using the fields above.
Announcement Announcement Module
Collapse
No announcement yet.
Multiple contexts question from a GTD rookie Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Multiple contexts question from a GTD rookie

    Can a next action falls into multiple context ? I use to have next action related to people that can be completed meeting people face to face or on phone call. So I put person related action into @agendas as well into @calls context. Does it make sense ?
    Last edited by fabio.baiocco; 11-22-2009, 01:41 PM.

  • #2
    Originally posted by fabio.baiocco View Post
    Can a next action falls into multiple context ? I use to have next action related to people that can be completed meeting people face to face or on phone call. So I put person related action into @agendas as well into @calls context. Does it make sense ?
    I'd say no because:
    • The context list has to be direct. Are you calling? Let see the list
    • You need to trust in your system. So if you have the same action in two contexts could create some confusion
    • And could also cause doubt decide to write here or there a certain action

    However how it worked for you your habit?

    Comment


    • #3
      i have multiple context on my next actions.

      i might assign @call, @agenda to the person i wanted to corespond to.

      the reason is i have something i wanted to talk to him. i can call him later in appropriate time and i might also bump into him later in the evening (if we are working at the same place/campus)

      so, if i happen to see him, i will peek at my @agenda list. if not, i might decide to call him and peek at my @call list.

      ---------
      in other case, i have multiple context for places too. example:-

      i work in a college where they have 2 seperate campus(building), the old wing and the new wing. so i have these 3 contexts,
      @COLLEGE, @COLLEGE-NEW WING, @COLLEGE-OLD WING

      usually, i would assign @COLLEGE together with @COLLEGE-NEW WING or @COLLEGE-OLD WING.

      in the end, it all depends on individual preference. As long as you feel comfortable and are productive (cranking the widges) either way is fine.


      regards,

      MATSURU
      www.matsuru.net

      ps. my @CALL also includes SMS (just in case you are wondering) :P

      Comment


      • #4
        Originally posted by clango View Post
        I'd say no because:
        • And could also cause doubt decide to write here or there a certain action
        When in doubt, i assign both or more contexts. so, I wont worry that i'll miss out an action.

        Of course, both contexts have to be appropriate.

        -----------------
        if there are any bugs, most of the time a weekly review will catch it.
        I am still working on sticking the weekly review habit. for now, my results are review whenever there is doubt.

        Comment


        • #5
          paper or LCD ?

          I am also a GTD rookie, so that I can be wrong :

          If you are using a paper based system, that depends on how much you are willing to write. Anyway I think that, to write it down twice it is consistent with the system.

          Case of you are using a computer based system with tags, IMO yours this is the logical option.

          .
          Attached Files
          Last edited by Juls550; 11-23-2009, 12:53 AM.

          Comment


          • #6
            I would create a context just for that person. If you have something to tell Mike, create an @Mike context.

            Failing that, just choose a context. That way, the information will get to the person at some point, even if you happen to see the person before you get to the context.

            Comment


            • #7
              Originally posted by Brent View Post
              I would create a context just for that person. If you have something to tell Mike, create an @Mike context.

              Failing that, just choose a context. That way, the information will get to the person at some point, even if you happen to see the person before you get to the context.
              I agree. i wanted to add that only create @person context for those key people that you interact with all the time. like your boss, colleague, wife...etc. this is to prevent people specific context from flooding your context list.

              some software such as OUTLOOK doesnt enable easy add/delete contexts (especially for me, maybe i am not a power-user yet :/ ) I find clicking and scrolling through long list of contexts and select is a burden to me.

              for non-key people, i will stick to @agenda context. i will assign my next action like this:

              @agenda- ALEX- confirm actions on project xyz.

              ----------------

              same goes to my @BUY list. example:-

              @BUY- BOOKSTORE- BOOK: GETTING THINGS DONE, DAVID ALLEN.
              @BUY- BOOKSTORE- STATIONERY: 3X PEN REFILLS
              @BUY- HYPERMARKET- EGGS- 1 DOZEN

              Comment

              Working...
              X