Projects & Next Actions
I find it helpful to limit next actions to only the literal next physical, visible action. With other sequential or future actions there is a risk they could change and it would be a pain to rework my next actions lists.
In most cases projects are simple enough to not have to worry about "forgetting" the sequential items. But another alternative is creating Action Support materials to manage that data separate from projects & actions lists.
How I would organize:
"Car is fixed"
"Call (Friend) to get name of mechanic, ###-###-####
I'd probably start a page so that when I call my friend I could note the name and number of the mechanic. That page becomes Action Support. And when I get done with the call to my friend I either put "Call mechanic ..." on my Calls list right away or make the call if the situation warrants.
I do this in a paper-based system (Time/Design) and it works a lot more smoothly than I probably make it sound.
How did you capture that thought?