I must first admit that I have not read David Allen's book yet; I'm learning these methods vicariously thus far.
The current iteration appears to disallow nesting projects, and/or nesting tasks. Is this by design, and if so, why? (or does it/will it support this)
The folders more or less cover the need for nested projects, but what about instances where it makes sense to, say, break down a task into a sequential set of subtasks.
For instance:
Repair the Shop (parallel project):
If we were restricted to just folders, that seems a bit clunky to me (they're just larger tasks)
Is there a better, more GTD-centric way of accomplishing this?
Edit: after rereading this post, I'm arguing more for nested tasks than projects
The current iteration appears to disallow nesting projects, and/or nesting tasks. Is this by design, and if so, why? (or does it/will it support this)
The folders more or less cover the need for nested projects, but what about instances where it makes sense to, say, break down a task into a sequential set of subtasks.
For instance:
Repair the Shop (parallel project):
- Buy Tablesaw
- Build Shelving (sequential sub-project, or sub-task):
- Buy two-by-fours (should break down into another parallel project/task)
- Buy painting supplies
- Assemble shelving
- Paint shelving
- Replace window
If we were restricted to just folders, that seems a bit clunky to me (they're just larger tasks)
Is there a better, more GTD-centric way of accomplishing this?
Edit: after rereading this post, I'm arguing more for nested tasks than projects
Last edited by Nevir; 2007-04-30 at 07:28 PM..