Interesting experiment - Number of active projects

[fooddude]

@fooddude An app limitation? Or a specific setup that does not allow parallel Next Actions?

No I just don't do it for simplicity. Only one action can be the very next action.

 

[TesTeq]

I do it for simplicity. My system is very simple. Have I ever had concurrent next actions? Yes. But during my weekly review, I eliminate all but the next action.

@fooddude Let's assume you have a project: "My family history described". Your grandparents are divorced and you want to interview both of them. You've got two obviously independent Next Actions: "Call Grandmother to schedule an interview!" and "Call Grandfather to schedule an interview!". Which one will you eliminate from your @phone Next Actions list?

 

[fooddude]

@fooddude Let's assume you have a project: "My family history described". Your grandparents are divorced and you want to interview both of them. You've got two obviously independent Next Actions: "Call Grandmother to schedule an interview!" and "Call Grandfather to schedule an interview!". Which one will you eliminate from your @phone Next Actions list?

Either one. I can only do one next. I would probably Call grandma first. When I'm done I might immediately call grandpa. If I don't it would go on my @phone list for when I come back to it. I don't have a list of all next actions for a project either. That way when I stop I can just put the very next action on my context list. If I don't, I will pick it up during my next weekly review.

 

[Tom_Hagen]

I do it for simplicity. My system is very simple. Have I ever had concurrent next actions? Yes. But during my weekly review, I eliminate all but the next action. I can stay laser focused on the project that way. I know the system allows for multiple next actions but I won't do that. I also have just a project list. When I enter a project I don't make a list of all next actions to finish that project. It is a waste of time. [...]

In my opinion, a common misunderstanding is what we mean by the definition of a "next action list." According to GTD, these are activities in a project that, given the given constraints: context, time, energy, and priority, can be completed asap. A project might have one such activity, but not necessarily. Sometimes, parallel work is possible.

However, a list of activities understood as an algorithm is something else entirely. And I don't believe that projects where the entire cycle of activities can be planned should not be planned at once. For example, due to my profession, I have to work through many IT books, which I divide into chapters, topics, or even portions of pages. Clearly, it's more efficient to write them down immediately in the project and then, by checking off the completed step, "pull" the next one off the list. This saves time; in some implementations (e.g., Evernote), you can see the project's progress, etc.

I've never been convinced by the idea of completing a task in a project and only then, during the weekly review, wondering what's next for the project. What a waste of potential during the week.

 

[bobusa]

In my opinion, a common misunderstanding is what we mean by the definition of a "next action list." According to GTD, these are activities in a project that, given the given constraints: context, time, energy, and priority, can be completed asap. A project might have one such activity, but not necessarily. Sometimes, parallel work is possible.

However, a list of activities understood as an algorithm is something else entirely. And I don't believe that projects where the entire cycle of activities can be planned should not be planned at once. For example, due to my profession, I have to work through many IT books, which I divide into chapters, topics, or even portions of pages. Clearly, it's more efficient to write them down immediately in the project and then, by checking off the completed step, "pull" the next one off the list. This saves time; in some implementations (e.g., Evernote), you can see the project's progress, etc.

I've never been convinced by the idea of completing a task in a project and only then, during the weekly review, wondering what's next for the project. What a waste of potential during the week.

Surely there can be some middle ground here. The GTD goal is to have space and free time, not to complete as many next actions as possible. I agree that waiting for the next weekly review might not be very productive, depending on the type of role you have and the nature of the area or project. I don’t think @fooddude is working at that extreme. One does review their next actions during daily reviews as well, which helps find a better balance and leaves room for unplanned activities.

 

[Tom_Hagen]

The GTD goal is to have space and free time, not to complete as many next actions as possible.

I don't agree with the statement as above.

Whether someone wants to have free time or accomplish as many tasks as possible is an individual matter, and GTD doesn't define it at all.

The goal of GTD is to be properly engaged and focused on all the issues and obligations / commitments (external/internal) we choose to accept. In this sense, GTD allows for both extremes: striving for laziness and being a workaholic.

 

[bobusa]

I don't agree with the statement as above.

Whether someone wants to have free time or accomplish as many tasks as possible is an individual matter, and GTD doesn't define it at all.

The goal of GTD is to be properly engaged and focused on all the issues and obligations / commitments (external/internal) we choose to accept. In this sense, GTD allows for both extremes: striving for laziness and being a workaholic.

That’s a better way to explain it. However, the goal is to have a clear mind and create the necessary space. Of course, the great thing about GTD is that you can adapt it to your own perspective on life.

 

[fooddude]

I've never been convinced by the idea of completing a task in a project and only then, during the weekly review, wondering what's next for the project. What a waste of potential during the week.

That is not exactly what I meant. I don't do one next action and wait for the review to record the next action. I do the very next action and then might or might not do several next actions as I work on the project. When I stop I record the very next action to pick it up from where I left off. If I miss that opportunity I will pick it up during my weekly review of scanning my project list.

 

[fooddude]

One does review their next actions during daily reviews as well, which helps find a better balance and leaves room for unplanned activities.

Yes since the next actions are in context, I would look at them when I was in that context. ie: @Home. I can only do an at home next action at home.

 

[fooddude]

Clearly, it's more efficient to write them down immediately in the project and then, by checking off the completed step, "pull" the next one off the list. This saves time; in some implementations (e.g., Evernote), you can see the project's progress, etc.

Again my system is simple. My project list is a list of projects in a simple statement of what done looks like. I don't have project planning lists unless it is very complicated. I may break a complicated project into smaller chunks to distill it to it's simplest form. These photos are not from the same time so next actions don't match projects. They are example screenshots. I also am not too interested in tracking progress. (I know some people just fainted). I just take the steps needed to completion. One step after the other.

 

[Peter Van Harmelen]

I think you need to do whatever you need to do to get the project off your mind. If that means list all the next possible actions, go for it. However, there is some wisdom in only having 'one' next action. In the example above about interviewing grandma and then grandpa - yeah they can both be next actions, yet you will pick one first. And after you talk to grandma, well, the thing might change and you may not want to talk to grandpa right now. One next action will automatically lead to the next. I tend to subscribe to the "only one" next action method: Area->Project->1 next action. After the next action is done, it leads the next one.

 

[gtd solo-studente]

In my opinion, a common misunderstanding is what we mean by the definition of a "next action list." According to GTD, these are activities in a project that, given the given constraints: context, time, energy, and priority, can be completed asap. A project might have one such activity, but not necessarily. Sometimes, parallel work is possible.

However, a list of activities understood as an algorithm is something else entirely. And I don't believe that projects where the entire cycle of activities can be planned should not be planned at once. For example, due to my profession, I have to work through many IT books, which I divide into chapters, topics, or even portions of pages. Clearly, it's more efficient to write them down immediately in the project and then, by checking off the completed step, "pull" the next one off the list. This saves time; in some implementations (e.g., Evernote), you can see the project's progress, etc.

I've never been convinced by the idea of completing a task in a project and only then, during the weekly review, wondering what's next for the project. What a waste of potential during the week.

Is it also being suggested a one-&-done Next Action is possible while being independent of any Project and perhaps somehow productively serving an Area-of-Focus ?

 

[fooddude]

Is it also being suggested a one-&-done Next Action is possible while being independent of any Project and perhaps somehow productively serving an Area-of-Focus ?

I do this often. I have a next action that is not a project (two or more next actions) but am not in the context to do it. I might put it in the context and do it then.

 

[cfoley]

I also prefer one next action per project.

I find that most projects have multiple possible pathways, and multiple independent threads that could be followed concurrently. My logical conclusion was that I should populate my action lists with as many as I could think of. However, this led me to procrastination. When in my calls list, I would put off the call. The call would be better after I had run the errand. Then while running errands, I would hold off on a purchase because it would be better to talk to a collaborator first. This sort of procrastination held me back on many projects.

Now, I realise what I was doing was avoiding making a choice. Because of this, when making a next action decision, I look for the single next action that will progress the project. If there are multiple possibilities, then I make a choice.

Importantly, when I look at my lists and see actions, I know that those actions are required (not optional) to progress a project.

This works well for me for most of my projects. I do have one or two that have large independent strands that have a next action each.