Quote Originally Posted by mcogilvie
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.
I think it is good of thinking next action as a bookmark.
I have digital system where each action is linked to the project so I do not have to put the relation in name for action. But I think my objection still hold:
What is the point of identifying next action in advance when you will nevertheless have to spend consulting project materials when you pick it up and you may come up with better fresh next action?

Quote Originally Posted by mcogilvie
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.
Yes but that action often tends to lay on my list at least until next weekly review and in the meantime nothing gets done on that particular project. Maybe this is a different problem.

Third: This was response to suggestion to spend more time planning.

Quote Originally Posted by mcogilvie
Those are not project planning steps. In debugging, you may at any time stumble upon the answer you are looking for, and not need to proceed further in your diagnosis. What you have given are the results of brainstorming steps to determine the problem. This is classic project support material. Same with determining your approach to your RPG.
This was a list of actions I have taken. I didn't put it in anywhere in writing (before this post) because I was doing it one step after another. But now I think it was not a good example.

Going back to RPG my problem was that I did not have much time to work on it so often I had put action to elaborate on some element then ran out of time, worked on something else and in the end improvised that element or omitted it entirely.
Summing up my action was chosen thinking I will put for example 6 hours in preparation but when I finally get only 2 it was not adequate.
--

And one new question.
How to handle actions with different size?
I find that some activities only make sense If I put at least 30 minutes - one hour in them, and they tend to be starved by actions that can be done in 5 minutes that are also on my list. And I find that often bigger actions provide more value but they are omitted because they are not that easy to cross out.