"Evaluate the status of projects, goals and outcomes one by one,
ensuring that least one current kick-start action for each is in your
Ready for Anything contains a virtually identical sentence on page 164.
Listing multiple [potential] next actions per project can be
distracting, but I'm sure it's the right way forward - it translates to
better flexibility during those short windows of 'weird time' during
the week, because you don't have to go looking at your project plans in
order to nail some small but essential element of a big task.
An example from my own life. I'm trying to launch a seminar in China.
As part of that I have several things I can do in parallel:
-outline the the agenda
-email several different people who might be able to help me
-make a list of potential locations
In my org structure, these are all part of the same project, but these
next actions don't have to happen serially. Whenever I get an idea for
something I can or should do for this project (and distill it down to
something concrete), I put it on the list for this project.
I agree that "next action" can be a misnomer, and for this reason I
usually use the term "action" or "to-do," always taking care to keep
my actions/to-dos concrete and unambiguous.
- move current automatic payments to other card @next
- check paperwork for cancellation proceedures @next
- wait for statement to make sure balance = 0 @wating
- call customer service
I find the concurrency works for me. I do try to keep it limited to 2
or 3 per project.
@Tidy the house
..............Do this and that.
..............Oh yeah, that too.
..............Don't touch that or it will breake.
..............Move that and that
..............Call him to ask where put that
..............Trow that away (who need that anyway?!)
and so on. I'm trying to manage all my projeccts on my HPDA, but when i
read this group i see too many different opinions that i'm getting lost
on the way.
I'm getting things right here or i'm complitly lost!?