Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
projects & next actions
direwolf | Apr 25 2006
Good morning - confused again :) When I've identified a project, should *all* actions for that project be captured on a separate 'project' card [in the order that they need doing] as well as listing the main project on a master list/index. What about the next action for any particular project - if the above is true, then does that get transferred over to a NA list, presumably with a note about what it relates to ? Then the individual project card gets reviewed/updated in the weekly review ? I'm getting there but this bit about managing projects with respect to next actions & where/when to put NAs relating to projects is twisting my mind somewhat. Thanks. 6 Comments
POSTED IN:
 One of the main purposes...Submitted by sonia_simone on April 26, 2006 - 2:38pm.
One of the main purposes of your weekly review is simply to make sure that you have a defined NA for every open project. But there is nothing in the world to keep you from popping NAs onto your list as you think of them, or slapping another one on the list as you complete the last, or having several NAs on the list for the same project, if you could do any of them now. The point of your NA list is that as you are sitting in your context, say at your work computer, you have a handy reminder that yes, I could push that project forward right now, and you know precisely what to do to make that happen. How much project planning you need is open in GTD--you can run through a project and try to figure out every NA in order, or you can just figure out the next one once you've done this one, or something in between. Support materials, including a master list of NAs for a given project if you created one, can go in a "In Progress" box, a reference folder, or some other useful system. » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
