I've come to the conclusion recently that I need to reorganise my GTD system, since some of my current Projects are probably actually 'Areas of Responsibility' That way I should be able to get more of a focused project list with two main benefits; reducing the amount of time my weekly review takes, and also getting some more satisfaction from achieving more goals. Both of which will hopefully give me more incentive to actually do my weekly review every week!
However, I do have a niggling question about NA's and how they relate to the weekly review. Others have suggested in recent posts that NA's should only be those actions which you intend to complete before the next weekly review. That isn't really practical for me, purely because of the number and size of projects I have, and seems contrary to the 'capture everything' ethos of GTD. If I have an action on a project, I need to capture it - right? It may well not be appropriate to do that action within the next week, but it still needs to go on the relevant NA list - right? If not, where else does it go so I don't lose it? Also, how do people handle actions which are dependent on each other ie.
1. Call Bob re: proposal
2. If Bob says yes, draw up contract documents
3. If Bob says yes, negotiate terms and re-draft proposal
...actions 2 and 3 are dependent on the outcome of 1, yet they still need to be captured.
Sorry this is a bit rambling but I'd appreciate your thoughts on this, and particularly on your interpretation of NA's in the context of the weekly review.