Can't start using project list

[mcogilvie]

I do that too. All you need is the context lists: when finishing one
action you think up what the next action will be in that project
and write it on an appropriate context list. Others on this forum
have also mentioned doing that, and see also
the Pigpog method: http://pigpog.com/2006/07/11/gtd-the-pigpog-method/
I am starting to use project lists too, though.

Each person needs to find the methods that work well for them.

One way is to just keep one next action for each project of the form

recruit army > conquer albania

and to keep future steps in the note. Forked projects can be annotated as

hang army deserters >> conquer albania

or similar. Or if your software supports it, you can duplicate tasks as you go.

[vic_lh]

Then I need to add a new project and check if I had it on the list before.

It quite surprises me that you doubt if you have registered a project already or not. I don't think I could ever have that doubt; once I decide, for example, 'man, I want to go to Greece on holiday this summer', I am positive about having written it in my project list or not -even if maybe later I'm quite inefficient about taking the required steps, etc-.

The first 2 steps in any of my projects are usually these: 1) Figure out a desired outcome and write it in the project lists. 2) Create a new action: "(keyword for project) - NPM" (i.e. Natural Planning Model). If I'm on a rush, 1) can be a single keyword, and the phrasing will be better decided during the NPM session, where I can decide a SMART goal, etc... But in any case, I don't see the duplicity you talk of; do you have a lot of those single actions that grow into projects? Could it be that you are overplanning? Can you give an example of this kind of actions?

Just my two cents. Like Kelly puts it,

Projects are not something "GTD" tells you you have, they are commitments you've made to achieve outcomes. The Next Actions tell you how to get there.

An analogy that I found very handy is that list items are like bookmarks; you put them when you stop working at something, so you can resume it easily later: "where was I? Oh, yes... Now I have to..." On a different level, I think it also applies to project list items, and to all the different K's.

Hope something helps

[kelstarrising]

I asked David to respond to this question on the purpose of the Projects list. Really rich discussion. One of those awesome DA responses about the power of the Projects list and how it ties to the Weekly Review in particular. You can hear it in the February Up Close podcast on GTD Connect. Starts at 6:52.

(If you're not GTD Connect member, the free guest pass will give you access to listen to this podcast online.)