Structuring events in a project
From what I understand structuring events in a project is discouraged in GTD. This means no automatic sequencing of tasks and not dependent tasks. The idea is that you find your next actions on your weekly review or you think of checking for the next task after completing one.
This seems like a counter-productive approach. One of the goals of GTD is to make things automatic so you don't have to think about what you might be missing. On this basis I have used Life Balance in the past and currently Omnifocus to manage my GTD. I use their ability to set up dependent and sequence tasks to set up my project and then let the tasks flow automatically. I still do a weekly review but it is not necessary to keep the project moving along. This way I avoid a problem if I complete my task on a Monday but don't do my review until Friday.
Why is treating projects like a project manager would frowned upon in GTD?
Tags for this Thread