In my experience..
Originally Posted by Kornet
Some have already said it, but I definitely go with the rule of not creating a project unless more than one action is involved. I have many single actions on my list that do not need a project. Projects are useful to me because I can look at them during my weekly review and identify the next action that needs to be taken, or mark it off if it is complete. Examples of a non-project actions I have on my list are: a Waiting For to hear back on a coffee date with a colleague; an Errand to pick up my tailoring, or a reminder to schedule a meeting. When I cross them off my list, I am done.
Some examples of actions that are tied to projects are: Reading over a spreadsheet to finalize numbers for Q4 (that is part of a larger project called Quarterly reconciliation, which requires a few steps); Set up a tour meeting with co-worker (part of a larger project to familiarize a new staff member with our site).
I hope that helps you distinguish a little. Keep up the great work- these are good questions! If you have a chance to go on our GTD Connect site, we have a webinar called 'Projects and Actions' that really gets into the differences of these lists. You can register for a free trial on our site here: https://secure.davidco.com/connect/free/14days if you would like to view that webinar.