I am new to GTD and to this message board. I have read the GTD book (very inspiring read BTW) and I hold it that I have understood most of the methodology presented. Now, there are some things for which I do not fully comprehend how to fit into my world, and would appreciate some clarification/guidance from the more experienced. I apologize for the lengthy post, but I felt I needed to write it that way in order to make the points. Basically, there are 3 issues:
1) Where do I track projects that I cannot start right now, nor ASAP, but rather in the future when certain circumstances are met, such as when I have enough money or other resources, or when I am sure I can have enough time to embark on a very time-consuming project, or if the project is season-specific rather than day or month-specific? I must point out that "Someday/Maybe" kind of stuff doesn't feel right for such projects, as the projects are mandatory rather than "maybe" (surely I am aware that realities change, but I can say with much certainty now that I will/have to be doing certain projects in the foreseeable future). And I also need to be able to store some support material in advance for such projects regardless of their being inactive, such support material being plans, ideas or whatever project-related info I come along.
2) This is somewhat related to 1), but where do I track projects that are dependent upon completion of another project? I am talking about simple dependencies along the lines of "I'll start X as soon as I have completed Y", simple enough to not warrant complex vertical project planning, but that still need to be tracked somewhere outside of my mind. As in 1), "Someday/Maybe" doesn't feel right and there's also the support material issue.
3) I understand that I can have as many or as few next actions defined for a project as I feel comfortable with. Sometimes, however, I need to define a whole sequence of actions in advance. I suppose that writing a traditional enumerated to-do list can be a heresy to GTD, nevertheless I could write such a list and put it into the support material, no? Then again, frequent copying from the support material to relevant next action lists can be tedious, and this is particularly true for those actions listed that don't require much time. So am I missing something there?
Thank you for your responses,