Nex Actions List

09-11-2010, 11:46 AM

I am a novice. I understand the projects list and I think I understand the next actions concept. At this time, I am using word files on my computer for the various lists. I have done my projects list. Simple. Now my "next actions" list is puzzling for me. Do I have a separate next actions list completely or one that is tied to my projects list?

By way of example, let's say I have one project on my projects list which is "Get a credit report." Do the next actions (find out how to get a credit report, apply for credit report, etc, go on the Next Actions list or on a list tied to this one project on my projects list.

As I read this, I am not sure that this is even a question that can be understood but I am stating it the best way I can.

Do I have a separate next actions list completely or one that is tied to my projects list?

As I read this, I am not sure that this is even a question that can be understood but I am stating it the best way I can.

Thanks

GN

hi there,

don't worry about the question being understandable, it is one that came up more than once (I haven't been up to GTD for that long, but I have been surfing the old posts in this forum a LOT )...

The answer is yes... and no... let me explain:
- yes, it is okay to have both types of lists:
* one list that is part of your project support material and that contains everything you can think of that could at some point be an action during that specific project: you could call this a brainstorm about the project or a project plan
* another list that contains all of your next actions (= the really next physical step) for all of your active projects: this is a list of everything that you could/might want to do at any given moment to move your projects forward
- no, that first type of list is not a NA-list. Only the second list is a genuine NA-list

Comment

Do I have a separate next actions list completely or one that is tied to my projects list?

By way of example, let's say I have one project on my projects list which is "Get a credit report." Do the next actions (find out how to get a credit report, apply for credit report, etc, go on the Next Actions list or on a list tied to this one project on my projects list.

DA recommends organizing next actions by context. Let's suppose one such context was an @Computer list. You might put "R&D how to get credit report" on that list. Because you have no idea what is entailed in applying for a credit report and you can't do it until you find out, you can safely leave it off of any list. When you do find out how to apply (specifically what to do), you can cross off the first next action, and add "Go to web site XXX and apply for credit report" to the appropriate list, probably @computer in this case. Perhaps two thirds of all projects can be handled this way. For the other third, you may need some project support material, which you can keep wherever works for you. GTD really does not encourage the kind of detailed project planning which may part ways with reality before the project is completed.

Note that lots of people want to connect next actions to projects in some way, and there are various ways to do it. If you don't have a lot of projects at any one time (I have about 90 right now, which feels like it is getting to be a lot), you may not find the work required to keep this connection worth the trouble.

Comment

By way of example, let's say I have one project on my projects list which is "Get a credit report." Do the next actions (find out how to get a credit report, apply for credit report, etc, go on the Next Actions list or on a list tied to this one project on my projects list.

Can you "apply for credit report" before you've "found out how to get a credit report"?