View Single Post
Just to recap my position. Priority and energy are just too in flux to capture in a program and are better suited to your current state and mind.

Priority: If you tried to capture priority on every task, project, context it would become a very complex system. If you changed the priority of one task or priority, how would that effect the other projects and tasks. If your lists are small (under 20) priority can be determined in seconds by a quick glance, much faster than capturing, plus the priority of any of those tasks could change in a second.

Energy: Energy is another amorphious thing. On Friday afternoon you might think that sending that email to your boss is a high energy task because you have low energy, but on Monday morning when you actually talked to your boss via phone or have the answer from someone else, that task is now a quick reply and low energy. In fact, if you were looking at the Low Energy list in the morning before coffee, it woudn't be there.

Again, I am not saying that energy and priority aren't important, they are, but the actual capture and manipulation of those fields is way too time consuming to make them useful for a good GTD system.

BZ