Another thing that concerns me is the process of generating next actions from projects: if I review my projects once a week, does that mean that I will generate at most one next action per week for each project? That might slow down the completion of projects but, on the other hand, taking on the burden of reviewing projects every morning might be too much.

As a first stab at solving this, I am dividing my projects up by status rather than by context or anything else. By status I mean "active", "deferred", "delegated" and such, as opposed to contexts like "@Work" or "@Home" (that are more to do with physical locations where projects can be worked on).

http://static.flickr.com/51/135244917_fb57051427_m.jpg[/img">

As you can see, I have also created a status called "priority". My plan is to review priority projects on a daily basis, to ensure that I keep an eye on them and generate next actions as quickly as possible.

I suppose one other thing to note on this subject is that completed next actions can generate new next actions if I review them on a daily basis. For example, if I have a action to "review hardware maintenance agreements" that I complete, then the next morning I should see that and immediately think of a followup action, "send changes to procurement department", without having to refer to a project at all. Perhaps this will work in the vast majority of cases? I have not used my system for long enough to trust that it well (and trusting the system is the important thing here).

David