Review Frequency is Key - using which kind of software features?
This thread contains a lot that I agree with wholeheartedly! And I would like to continue with some observations and questions. Varying the review frequency really is a key factor to having peace of mind.
I stumbled into this forum only yesterday, into a thread (GTD 2.0) where I did not feel at all feel comfortable with the overall tendency to partly reintroduce classical time planning elements and classical priorities. Not having seen this present thread yet, I responded over there, trying to advocate a differentiation in review frequencies instead: http://www.davidco.com/forum/showthr...891#post109891
But here in this thread it seems that almost everyone is already into this type of differentiation in one form or another, and I would like to follow up with some questions and thoughts. We are all probably using different software, and similar things can have different names, so please bear with me.
I get the impression that many of you use "review timers" individually set up for each project. Does your software have special review timers, or are you using the regular Tickler functionality (usually called Start date or Scheduled date in most apps)?
It would seem to me that some of the things being referred to in this thread, e.g. reviewing certain things annually before the harvesting season, actually ARE regular Tickler items, or am I missing something? I mean, these particular kinds of reviews are actually triggered by a certain external condition that is expected to be present on that date.
As for the regular "interval reviews", those that are not brought about by any particular factor at any particular time, but which we do at certain intervals just to keep our lists up to date and make sure we do not miss anything, do you use individual timers for each project there as well? I get the impression that many here do, and maybe that is good, but I am not quite sure why.
I am curious whether anyone does it like I do it, and can help me compare the benefits of the two methods.
My method is to "mark" different projects (and single actions) for different review frequencies. I have a High, Normal and Low level for each type of list. Depending in what features the particular software has, I would use its Tags, Labels, Contexts, Priority or some similar mechanism to do this review frequency marking.
Then at certain intervals I have Tickler items popping up to do a review of type X, and then I know exactly where to look. I even do spontaneous reviews whenever I feel like it, in those cases usually looking only at the things marked for "High" review frequency.
For example, in Someday/Maybe, I usually have some very tempting things, but which I feel may be too risky (that's why they are not in Next), that I want to contemplate as often as possible. Having these marked as "High" allows me to find them very quickly. Similarly, in Next, the High items in there I look at every single time that I even look at the list, much more than just once a day.
The Normal frequency items I review at the standard GTD intervals. The Low frequency items I review only more seldom, which saves me a lot of time.
I have found that my choice of a frequency setting correlates very much with the fuzzy general definition of priority as "important, urgent or whatever makes you feel excited or anxious about this thing". So I prefer to use the Priority field in those apps that have one, especially if it is in color.
Tags for this Thread