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:
 Ideally, at least the way...Submitted by emuelle1 on March 14, 2006 - 5:31am.
Ideally, at least the way I see it, you should generate NA's only for the projects that need to be carried forward this week. If you have a project listed like "Winterize House", you would probably be safe waiting until October to generate an NA, while a project that has to be completed in 2 weeks needs NA's generated right now. One of the points of GTD that really stands out to me is "feel good about what you're not doing". You obviously can't do everything at once, only what's on the runway. When you do your weekly review (which I admit, I may have done twice since I started GTD last year), review all of your projects, someday/maybes, and make NA's for what you can do in the next week or two. I've been trying to think only of the next week, and the next weekly review will give me the week after that. » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
