TesTeq;65456 said:Taking the above calculation into account I still do not believe that more than 200 personal Next Actions is a realistic approach to life. In my opinion it is just wishful thinking.
But if a person's goals are truly that complicated, surely they'd have an even greater need to have a system to manage those goals than someone with a simpler set of life goals?
It seems to me that we usually discuss what I'd call a "few projects - many next actions per time" mindset. A relatively small number of projects, each of which can go through several next actions in a short period of time. So a relatively small number of projects means a relatively small number of Next Actions.
But here we're talking about a "many projects - few next actions per time" workload. There's nothing to say that a person with a very large number of projects, each of which requires a very long time for each next action, can't use GTD.
An example: Imagine that I want to breed a tomato with particular characteristics. I want it to be orange, medium-sized, firm, low acid, resistant to SomethingVirus, suitable for chilly climates, and indeterminate.
I have access to seeds for a couple of dozen different open-pollinated patent-free tomatoes, each of which has one or more of the characteristics that I want. I will cross those tomatoes until I get a single tomato with all of the characteristics that I want - or until i give up.
I will have to make many, many crosses to get what I want. Each cross, from choosing the parents to evauating the characteristics of the chlidren, will take a _full three years_, because with a cross of a true-breeding plant, the second year is an F1 hybrid and the differing characteristics only show up in the third year, so that's when you can really _start_.
(If I'm wrong about F1 hybrids, feel free to tell me, but I don't think that it changes the example. It would just take the cycle time to two years instead of three.)
So the project, "Evaluate the progeny of the cross of Tomato A with Tomato B", has a quite small number of next actions that may take no more than a few minutes of actual labor, but will stretch across three years before you even start on the interesting part.
And I'm not going to _just_ cross two tomatoes and wait around three years for the result. I'm going to cross dozens and dozens of pairs of tomatoes. And I might also be working with peppers. And zinnias. And so on.
So if I'm breeding plants, even at a hobby level, I not only could, but _will_ have dozens or hundreds of projects, each of which go through only a few Next Actions per year.
It sounds like this is Oogiem's situation, except that hers is much, much more complicated, because she's working in _many_ areas of long-term and short-term and mid-term projects.
So someone could tell me that in my scenario, I should get a plant breeding database and take the complexity out of GTD. This might change two hundred "Cross A with B" actions to a single "Print 2009 cross list and perform crosses" action. But I don't think that this is so easy with Oogiem's workload, becuase I don't think that her workload has the same patterns of many near-identical actions.
So hundreds of projects, each with a next action that may not happen until months or years from now? Seems perfectly reasonable to me.