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.
Tracking diffrent size projects Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Tracking diffrent size projects

    I have been unable to find a confortable system for traking diffrent sized tasks. I have large projects that can take a year or more and breaks down into discrete projects itself, for example, writing a book. I also have smaller projects that might only take a few days, say repairing the dishwasher, repairing and selling a desk, or packing for a move.

    The individual projects of the large projects can overwhelm a simple projects list and hide the smaller projects. How can I track both types of projects? I would prefer a single list.

    By the way, I use a paper based system.

    Thanks!

  • #2
    Originally posted by dr_jones View Post
    I have been unable to find a confortable system for traking diffrent sized tasks. I have large projects that can take a year or more and breaks down into discrete projects itself, for example, writing a book. I also have smaller projects that might only take a few days, say repairing the dishwasher, repairing and selling a desk, or packing for a move.

    The individual projects of the large projects can overwhelm a simple projects list and hide the smaller projects. How can I track both types of projects? I would prefer a single list.

    By the way, I use a paper based system.

    Thanks!
    I think what you are saying is that you list all the sub-projects of a larger project on the same list as smaller projects. If you have, say, a year-long project, it is unlikely that all of the sub-projects will be active at the same time. You must put the inactive sub-projects in project support materials. Those support materials, however you set them up, can be used to track the progress of a large project as you prefer.

    Comment


    • #3
      Goals

      It sounds like you're trying to combine your 30,000 ft with your 10,000 ft perspectives.

      Personally, I never use sub-projects. If I have more than ~10 related projects I tend to group them together under a single desired outcome and call it a goal. For me and my hierarchical mind, it make much more sense to call "write book" a goal than a project because "write book" is such a giant undertaking (even if it's a short book) that you'll be constantly generating new ideas and new projects and tasks related to it.

      If you really have to get this book written in 1 year, for example, then calling it a goal under which you'll organize your related projects and then reviewing that goal in your weekly review will bring you substantial more clarity. Goals are the direction projects should point.

      Comment

      Working...
      X