Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
Don't totally understand NAs
mream | Mar 14 2006
I'm new to GTD. Just read the book over the weekend, and spent today collecting and beginning to process. There is still something I don't understand about next actions. Let's say I have a list of 50 projects, and I go through each one and decide what the next physical action is... am I going to end up with a list of 50 actions, work through those, then generate 50 more? Would I be kind of spinning my wheels as I rotate through all 50 projects, rather than focusing on one, and doing more actions on that one? Or am I missing something? When I list NAs, should I list all the NAs I can do on a specific project? Thanks for the help, Matt 16 Comments
POSTED IN:
 So, what you should do...Submitted by paperandglue on March 22, 2006 - 9:27am.
So, what you should do when planning your project is list out the anticipated next actions, and have that list in your project lists. Then, put NAs in your various NA lists as appropriate (given that you want to keep your NA lists very current and not bogged down with stuff to do later, but stuff too do NOW.) And the making of the project list is key to what Allen talks about when he says planning involves more thinking than you're used to but not as much as you're afraid it will. » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
