Quote Originally Posted by AGrzes View Post
I find few problems in this approach.

First I think the main benefit of maintaining a list of nearest next physical action by context is that If you are in that context you can pick it up and do it straight away. The way you described one could put "Work on project XYZ (details in project support materials)" and have the same situation.

Second, If there are multiple approaches at problem the one devised in the past may not feel right when finally getting to work at it. And if it does not feel right it is hard to expect to follow it with great energy.

Third, In many cases thinking about how to do the task is most of the work, so when I would have time for detailed planning I could do the task right away.
First objection: Try something like "Do concrete next action on Project XYZ." If you want to keep going on Project XYZ, do so. When you stop work on XYZ, determine a next action for it. A next action is like a book mark: It tells you where and how to start working on the project again.

Second: Your hypothetical next action is then not something you are committed to doing. Your next action is then to find the real next action. Or just do whatever feels right and move on from there.

Third: I'm not sure what you mean here. GTD does not particularly embrace detailed project planning. All you need for a project is a desired outcome and at least one next action. That's it. If you need more planning, that's a next action. If you don't need more planning, don't do it.