Why list the only next physical action? Why not list a number of action steps for the required outcome? What is the thinking behind this?
Agreed. The way I tend to work is that in the brainstorming phase of a new project, a bunch of next actions will come to mind, and I will put them down on all my lists. Later, perhaps during the weekly review, if too many of these are still undone and I'm unhappy with the apparent lack of progress, I might back things down so that only one next action for the project appears in my lists (it's a single checkbox in Life Balance). Or I might think harder about dependencies that have appeared since I started working on the project, and rearrange the NAs to match reality.The difference is really how long your lists are.
Here's one thing I do with clients who have a LOT of ideas (ie: next, next actions) on larger projects:dano77 said:Why list the only next physical action? Why not list a number of action steps for the required outcome? What is the thinking behind this?
It's not so much a form as a discipline. When I find myself "petering out" after a burst of work on an incomplete project, I want to take the few minutes to record exactly what needs to happen in order to complete it (which is often more than one NA, although not always), while this knowledge is still in my head and hasn't fallen out!A good point, very relevant to my own situation. Can you say a little more about the form of the "bookmark"?Ambar said: The other thing I make a point of doing with my NAs is leaving myself a "bookmark" when I'm winding down a session of working on a particular project.