Iím experiencing a series of issues around organizing tasks versus projects properly. I would appreciate any feedback or advice. Not that it matters too much, but to give you an idea of my system Iím using a Moleskine large ruled notebook (the one with the hardback cover).
1. As we know, many projects require only two or three tasks to complete. It seems wasteful to use an entire page in a Moleskine notebook (or any other notebook for that matter) to track such projects. Some options Iíve considered:
2. I find that projects -- not just next actions -- belong in many context-based lists. This presents a problem because it seems that GTD calls for restricting each list to tracking either a project or next action (not both)Ŗ. For example, I created a context-based list called @Lamborghini to track anything to do with my car (a Pinto). One of my list items is ďget car serviced,Ē which requires more than one task and thus constitutes a project (I have to call the dealer/local repair guy to compare quotes, work it out with my carpooling partner, etc.). But I also have tasks, such as ďget car washed.Ē Questions:
- Track more than one project on a single page... but the problem is I would need more space in case the scope of the project changes.
- Use Post-It notes and stick Ďem into my notebook.
- Any additional ideas that you may have.
3. When Iím capturing stuff to my system, I find that I tend to get bogged down in thoughts of ďnow where should I put this?Ē instead of focusing just on capturing. Any advice here?
- Would I perhaps gain more efficiency by creating a separate list called ď@Car serviceĒ? If so, I would definitely run into the problem described in item #1 above: having to document a project with only two or three next actions.
- Might it be better to create two context-based lists with the same name -- one for projects, the other for next actions?
- Okay, I was kidding about the Lamboghini/Pinto thing. (I have a RAV4 (and my list is so named.)
Once again, Iím grateful for any feedback.
- One option I thought of is to create a ďbrainstormĒ list that I can use as a draft of ideas and then transfer items as necessary to my system.
- Another thing I had considered was that as I get more seriously into using my system (Iím relatively new to this), I find that I will be creating lists on an as-needed basis -- in other words, perhaps over time, my needs will help create the system.