View Single Post
I'm confused about the distinction between projects and tasks, because to me everything should be in actions, and therefore they should both be addressed as part of the same process.

Is the distinction about tasks that are of indefinite length, and those that have a clear start and end point? My strategy is to transform the first into the second, as in:

- Spend fifteen minutes brainstorming about Gadget Database design.
- Spend two hours outlining Gadget Application requirements document.
- Select one item from Whatsit Site issues list and give it two hours. If not done, Next Action the stopping point.
- Document at least ten coding tasks for Thingamajig Application, to "crankable widget" status.
- Spend four hours working on one Thingamajig "crankable widget". If not done, Next Action the stopping point.

Gardener