When I try to stop doing this, I'm finding a lot of internal
resistance. One of the things I'm afraid of is that if I really put
down true next actions, I'll have too many of them, or I'll spend all
of my time looking at my projects list trying to decide what's next. I
realize that these are all irrational, illogical worries.
I'm sure other people encountered similar internal resistance to true
Next Actions. How did everyone else handle it?
When the monkey brain is engaged, when a really dumb NA is all you have
to do, oh productivity goes right the way up there. Give it a go,
don't hold back.
A couple of things might help. Stephen Covey's approach where you try
to identify Important and Not Urgent actions can help you prioritise
between your various projects. You can start your week looking at all
your projects and then focus on the priority ones.
You might need someone else to tell you. The Kinkless GTD approach
currently sweeping OOP lovers off their feet has a latest template that
gives you its list of your next actions. It'll go through your
projects and actions and pull a set of them out for you.
While staring at my list, I'll ask questions (often subconsiously) to
drill down to a sub-set of my actions.
For example,
Where am I... (Work)
What tools are available to me (Email, Phone)
What people are available to me (none)
What level of complexity am I able to handle right now (not much)
Now I've only got 4 or 5 things that fit all of those criteria, so I
just pick one and do it.
I stuck it here:
http://metacarpal.net/blog/archives/2005/10/05/someday-display/ because
it's just unwieldy long.
Cheers,
Josh