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:
 You can have as many...Submitted by stevecooper on March 16, 2006 - 2:03am.
You can have as many NAs as you want for any project. If you don't have a NA for a project, though, you either need to choose one, or be happy that your project isn't going to progress. If that's the case, you could move it onto your someday/maybe list. So your projects relate to NAs like this;
Active Projects
Project 1
NA 1.1 @WORK
NA 1.2 @HOME
Project 2
NA 2.1 @WORK
Someday/maybe
Project 3
<no NAs>
That generates you two context lists; @WORK NA 1.1 NA 2.1 @HOME NA 1.2 One idea is this; if there's something you know you need to do, don't be afraid of writing it down. So if you know an action you need to take, write it down so you don't lose it or worry about it. Don't worry about adding too much to your system; it doesn't forget, and you do, so let it do all the remembering. » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
