Understanding projects and their actions

T

tj-startup

0
I just finished reading GTD for the first time and most if it makes a great deal of sense to me. However, I'm having some difficulties dealing with the projects part of the system. Is my understanding below correct?

1. Anything which requires more than one action is a project (e.g. Get new auto insurance, New marketing campaign).

2. Have a master list of projects and have a separate page for each project listing all of the actions necessary to complete the project.

3. Additional information that is not an "action" is project support information

4. Whichever action is next for a project should *also* be on the "Next Actions" list. When that action is completed copy the following actions from the project page to the "Next Actions" list.

5. During Weekly Review, review master list of projects and the page for each project.

Any input is welcome. Thanks!
 
tj-startup;55543 said:
I just finished reading GTD for the first time and most if it makes a great deal of sense to me. However, I'm having some difficulties dealing with the projects part of the system. Is my understanding below correct?

1. Anything which requires more than one action is a project (e.g. Get new auto insurance, New marketing campaign).

2. Have a master list of projects and have a separate page for each project listing all of the actions necessary to complete the project.

3. Additional information that is not an "action" is project support information

4. Whichever action is next for a project should *also* be on the "Next Actions" list. When that action is completed copy the following actions from the project page to the "Next Actions" list.

5. During Weekly Review, review master list of projects and the page for each project.

Any input is welcome. Thanks!
Click to expand...

Yep. You've got it.

The only comment I have is that (in #2) the separate page for each project listing all of the actions to complete it is entirely optional. David Allen suggests that you only do as much planning ahead as required to keep the project moving.
 
jknecht;55544 said:
Yep. You've got it.

The only comment I have is that (in #2) the separate page for each project listing all of the actions to complete it is entirely optional. David Allen suggests that you only do as much planning ahead as required to keep the project moving.
Click to expand...

In my understanding DA recommends to do so much planning as needed to finish thinking on the project/ empty head/ mind like water.
 
tj-startup;55543 said:
2. [...] separate page for each project listing all of the actions necessary to complete the project.

3. Additional information that is not an "action" is project support information
Click to expand...

Project support material, yes. As much as needed to be cool with your project.
 
Thanks for the responses. I see what you mean about the amount to put down for the projects. As written, it's probably overdoing it -- since planning every future action for a project is not necessary to get to the right state (and may be opposed to it) in some cases.

Thanks again. I'll try sticking with this for a while and see how I do.
 
You must log in or register to reply here.
Top