By definition, only 1 is a next action, 2 and 3 are future actions. So your next actions list should only include action 1, not 2 and 3. If you are going to add in future actions, your system needs to be able to filter so you can look at only the next ones excluding future. Otherwise you'll see actions you can't do anything on.
Originally Posted by robs23
The whole point about having a next actions list rather than an actions list is that things change and you can't always anticipate the next action, it is often different to what you planned, so you can end up having to delete a lot of actions you don't need or are irrelvant.
Thanks for the example! Just to add to Suelin23's comments, if a project is simple and linear, it's usually best to not go too far into the future. Furthermore, your project steps are probably not next actions. Buying a car involves what you need, what you would like, what you can afford, and what's available. Most people are going to bounce back and forth between these things for at least a little bit before settling on a strategy. In terms of budget, "estimate funds on hand available for down payment." is a next action. So is "Thing about how much monthly payment do I want to take on". Later on, you might want to "look at car section of Craigslist." "Buy a car" is not a next action unless you are walking out the door with a checkbook knowing what you're going to buy where. If I were doing this project, I might want to put in the note section of the project, something like:
Originally Posted by robs23
- what I must have: dependable, seats 4 comfortably,....
- what I would like: great stereo, mpg > 30, ...
- where to shop: Craigslist, local dealer, ...
- what's needed to buy: title, certified check, ...
- follow-up after buy: insurance,...
Notice that this stuff is really project support material, not next actions.
FWIW, I struggled for a long time in various ways against the simple practices David Allan advocates. Once I had the basics down, I was able to add just a bit more customization. Good luck!
Well, many thanks for all replies.. Regarding provided example.. it's simplified on purpose, to make it clearer. I realise that those 3 actions are really not actions because they can easily be splitted into more basic actions... I provided that example not to discuss it (though thanks for that!) but to point that dependencies are helpful at planning a project. And yes, I won't be able to set dependencies for every project because sometimes to many things are changing during project. But sometimes, for me quite often, they may be very useful.
So if there is any other software, other way to get them implemented into my GTD system, i would appreciate posting that.