• If you are new to these Forums, please take a moment to register using the fields above.


No announcement yet.

GTD for several works

  • Filter
  • Time
  • Show
Clear All
new posts

  • GTD for several works

    Hello everybody,

    Im learning about GTD. Id just read the book and Im trying to use the method. So, I have a question:

    Ive got three different fixed works. Part time each one.
    Should I use ONE list to set my subjects or should I organise my subjects using GTD for each one company?


  • #2
    One, only one


    If I were you, I would create one and only one list of to dos, and I would make sure to tag or categorize each and every task with what job it refers to (is a part of).

    I find it easier to pick the right next action if I have but one list to pick from, instead of plenty.

    If the three jobs are place-specific, you could create a context for each, such as @[job1] and @[job2] (replace [job1] with a name that seems natural to you).

    The Structure Blog


    • #3
      Be happy to help you, but I'm confused by your terminology. What are "fixed works"? What do you mean by "subjects"? Can you give us specific examples?


      • #4

        Thank for your answer Stiernholm. Its exactly what I was looking for.

        And Brent, Im sorry about my english. Im Brazilian. But, "fixed works" I mean: "companies" and "subjects" I mean "category".

        Best regards,


        • #5
          Separate NA context list for each company.

          Originally posted by Ricardo View Post
          Ive got three different fixed works. Part time each one.
          Should I use ONE list to set my subjects or should I organise my subjects using GTD for each one company?
          One list of all your Projects.
          One list of all your Someday/Maybe projects.
          Following Next Action lists:
          plus any additional context lists you need.


          • #6
            It depends on how many projects you have

            I tried having only one list of projects and couldn't do it - and I only have one job, just with very specifically different facets. I have hundreds of projects to track at any given time and I was losing them in the big list.

            So I do keep separate project lists (one for each specific job area plus one for all personal mixed together). I then use one set of Next Actions with a link back to the project. I have found @contexts to be somewhat limiting, because I have a computer either at home or the office and I have my Blackberry with me all the time (so access to phone, e-mail, web browsing, calendar). I just use @work, @home, @errands, @waiting for and @someday/maybe.

            Another benefit to keeping separate project lists is if you ever need to discuss your workload with your supervisor. You likely would not want your personal projects or projects from other jobs on the list you show your supervisor!

            But if you only have a few projects ongoing at any one time, then keeping one list may work for you. There is no one "right" way to implement GTD. Good luck and keep trying until you find what works for you.


            • #7
              I use three Project Lists in my system:

              Projects-Volunteer Work

              I have to give regular progress reports at work and in the volunteer position and I found it to be more labor intensive to keep one Projects list and try to cull specific projects out for it.


              • #8
                Alternatively, if you an assign more than 1 tag/category in your list, you can create addtional tag/category for your company. For example,

                @office - write report re:sales pitch [company A]
                @office - file document 543 into project ABC folder [company B]
                @office - make coffee for lady boss [company C]

                @company A- @office - write script re: the apprentice epd 956
                @company B- @office - write proposal re: project runway
                @home - cook dinner for wife

                if you can set up both context and tag/category in different column, you can sort them separately. i think that will be helpful.



                • #9
                  and for the actions or tasks --it depends

                  If you do all your work for each company while at each company's location, you will need contexts listed for that site--you will need to analyze the situation depending on whether you use their phone, their computer, supplies, etc. I would bet you would have certain days or people whom you have tasks with, so using the calendar and @adjenda would probably be crucial.

                  If you are like a lot of us, our work travels with us. It is done anywhwere that we can do it This is both good or bad, but your ability to track and manage your tasks and projects will be crucial. Also, developing a good relationship with a key person at each site might help-the day before you are due their you might contact each week or whatever pattern works for you. I had a partime job where the boss always put copies of anything I needed in my mail box and was really great. This spoiled me and in my next one, the boss was not so thoughtful, maybe even resentful rather than grateful to have me. I had to constantly be on the look out for changes in meeting times, places, policies, etc. It really was a burden. They didn't even let me know in advance that the water was going tob e off for a day or that the furniture was going to be "touched up".

                  Also allow time for any administrative business at the site such as forms, human resources stuff at each place.

                  Either way, having a reliable capture and review will be crucial. Good luck. You sound like an energetic and well-directed person, so once you think it through, it will all come together for you.

                  If you carry papers about, you should photocopy anything irreplaceable and keep a copy at the site it belongs to for safekeeping.

                  You may want to have a different colored folder for each site. Maybe a folder large enough to put smaller folders in if need be.