Here are some possible ways in which the Random Method could be improved.
The main problem with it is that the longer the list gets the longer the average time before individual tasks gets actioned.
To counteract this there needs to be either a restriction on the number of tasks entered, or some sort of prioritizing system to ensure that the tasks that need dealing with frequently get despatched quickly.
The easiest way to restrict the number of tasks on the list is to start a new list at the beginning of each day. The aim should be to finish all the tasks each day.
The alternative approach, as I’ve just said, is to allow the list to grow but to develop some sort of prioritizing system.
Here’s a possible one, which is automatic and adjusts to the nature of the random process itself:
- When you finish working on a task and there is still work left to do, re-enter the task in the normal way at the end of the list, but add another copy of the task.
- When you finish working on a task and no work is left to do, cross it out - and if it is a recurrent task re-enter it. Do not delete any extra copies added under rule 1.
- When you are directed to a task by the Randomizer and the task is “empty”, i.e. there is no work to do, delete it. If it is a recurrent task and there are no other copies of the task in the list, re-enter it. If there are other copies then don’t re-enter it.
Using these rules the speed at which the Random Method picks tasks will automatically adjust to the amount of work that is needed to keep the tasks up-to-date.
At least that’s what I hope will happen. I haven’t tested it out yet!
Anyone want to give it a try?