batkins said:
Do I simply put all of these NA's onto the right context list (in this case, @Computer), or do I pick just one and leave the rest with my project material? If there are Next Actions that depend on other Next Actions, should I only track the gatekeeper actions and leave the rest with my project information?
Anything that really is a Next Action -- an action that does not depend on something else happening first, something you could do right now with the appropriate contect/time/energy -- should go right on your next action list for that context. Each active project should have at least one next action, but can certainly have more than one.
An action that depends on another Next Action happening first isn't really a Next Action. Keep your planning for that kind of action in your project notes, and move it to a next Action list when it becomes a Next Action you can really take.
(I make this a little easier on myself by using the "notes" area that my Zaurus to-do list software gives me for each Next Action on my list. If a current Next Action will naturally lead to another Next Action, I add a note:
THEN: [follow-up action]
When the first action is completed, I can just cut-and-paste to create an entry for the new NA.)
The goal with Next Action lists is to minimize how much re-thinking you have to do when you're ready for action and you look at the lists. If you look at your NA list and have to decide "Can I really do this now, or does something have to happen first?" you're forcing yourself to re-think things you've already thought.
-T.