+6
Under review
Anonymous 7 years ago • updated by Kevin Erath 6 years ago 3
Currently, it seems any tasks moved to a project folder is automatically also contained in the "next actions" folder.

This is not really reflecting the strict GTD concept of a project and next actions. It should be possible to mark only one or several of the tasks in the project as "next actions", while the others are simply sitting there and do not show up in the "next actions" list because they are not relevant now.

Answer

Answer
Under review
I'm not sure about this, but i think that all actions of a project should be put on the next list. But i see the point, that maybe an action depends on another one and thus can only be done when the dependend action has been done already.
Answer
Under review
I'm not sure about this, but i think that all actions of a project should be put on the next list. But i see the point, that maybe an action depends on another one and thus can only be done when the dependend action has been done already.
Kevin, for small projects with few actions you are right.
But if you think of a bigger project and apply David's five steps of natural planning you will result in a large list of what needs to happen to make the whole thing happen. In the next step you have to decide what should be done next, and who will do it. So generally "next action" is only a part of that list.
Yes, I agree with Winfried. I utilize projects a lot and often add tasks to be done later as a reminder. But I cannot 'deactivate' such tasks in a proper manner to avoid having them on the Next list until it is time to do them. There shall only be one next action for each project if you use GTD properly I believe.
Perhaps Next Actions can function as a Focus View showing upcoming tasks for the week or your chosen time frame? While ideally there would be one task per project, people are usually more informal in implementation