Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
How many next actions of a project on your next actions list?
Tmpx | Apr 7 2007
How many next actions of a single project, do you put on your next actions list? 11 Comments
POSTED IN:
 This is one of my...Submitted by bengoshisan on April 10, 2007 - 10:20am.
Berko;8874 wrote:
This is one of my problems with the concept of the weekly review. I can't see how having one NA per project and reviewing weekly can get anything done at all. Depending on how granular a NA is for a project and how many steps a project is, it could take months to get a project done at this rate. This really made me think. Shouldn't you (well, I) be doing a daily mini-review of all NAs and projects? Otherwise, really, if you have a NA completed, how else would you add a new NA for a particular project, so that it is going forward, unless you review your projects list? Of course, if the project is nagging you in some way, because it is urgent, etc, then you'll remember that you need a new NA -- but that is basically the same as keeping it in mind, which is heretic to GTD. Berko;8874 wrote:
I think this is one of the most important things I have heard about NA's. No sense putting a phone call on your list for which you would have to look up the number first. Maybe the definition of a NA should be adjusted to be, "Any physical action that you can take to move the project forward" rather than "The very next physical action..." so that the definition leaves some lattitude for operation. Maybe the definition of a project should be refined a little. If you can choose two next actions for a project, then you (may) actually have two small projects. So a project in this sense would be a sequence of NAs that are linearly dependent on each other (ie. you can do them only in a particular sequence, and it does not depend on anything else). » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
