I am just starting on adopting GTD and while this might be a very naive question, I did not see it get answered on the forum.
The question essentially is, how frequently would you create projects to track sub-tasks. While I started collecting actionable items for my open-loops, I could see that nearly every open-loop required two or more actions to be performed before it could be completed. I therefore started to wonder if it was really possible to have atomic actions that need not also figure in one of the projects?
As an example, if I intended to set up a face-to-face meeting with a colleague, this would essentially translate to
- Email XYZ to schedule a meeting
- Book the conference room to meet with XYZ
- Discuss the meeting's agenda with XYZ
Even simpler things like preparing a status report (which lets assume I myself prepare) will have to be done in multiple steps
- Write the project weekly report
- Email project weekly report to XYZ
For now I am defining a project to track each of the above two open loops. My concern though is that my next actions start to appear both in the next action context list and in the project list.
My questions [x] Would you broadly agree with my approach above? [x] Would you review the project lists only during weekly or with whatever frequency you review your next action list? [x] Would you also define projects to track each of the two open-loops mentioned above?