All you need is one next action - and, technically, there is only one "next" action; as I see it, the others are just actions.
I've found that having more than two or three actions for the same product is counterproductive, because the project usually diverges from that plan and then those actions clutter up the list. More than once, I've had a next action for a project that reads something like "Clean up stale actions for this project." That's not good.
Now, if the project is really big and has several avenues, each of which can logically have a next action, then IMO it's several projects, each of which should then have one action. Even if they all have the same final goal, they involve a different series of tasks, so they're different projects
I do often have thoughts about a project that aren't a "next" action, so I maintain what I call "agenda" lists for each major project or group of projects. It would make more sense to call them "thoughts" lists, but, well, there it is. When I have a thought regarding a project and it's not actionable either now or at some predictable time, I usually tuck it into that list. But I consider that list to be project support material, not actions.
Tags for this Thread