An older iteration of Mark's work on the final version (perhaps completely different, for all I know) had something to do with "1-to-7", which he abandoned before completing the final version in its final form. I'm curious whether Mark has shared -- or Mark, whether you'd be willing to share -- the rules of that old iteration, or one of them if there were multiple. I'm just curious what it entailed.
It sounded really interesting at the time! My curiosity is still piqued.
In any case, though, thank you for creating the final version, as well as the others. I use FV often and find it very helpful. I'm a graduate student in electrical engineering, and at the end of the semester now I'm finding myself wishing I had used FV more consistently instead of slacking off. I'm going to use it to get a lot of reading done over the winter break, anyway.
The system consisted of having seven pages as follows:
Page 0 Last chance Page 1 Urgent Page 2 Incomplete Page 3 Recurring more than once a day Page 4 Recurring daily Page 5 New stuff Page 6 Recurring less than once a day
The idea was that each day, the pages were renumbered so that Page 0 was deleted - hopefully with nothing on it - and the remaining pages were renumbered so Page 1 became Page 0, Page 2 became Page 1 and so on.
I tried lots of different versions. Some using Page 0 and some not using it. Some changing the pages daily and some changing when there were no further tasks on whatever the first page was. I also tried various methods of going through the pages, e.g. doing the tasks in the order they were written, variations on AF1 and AF2 etc.
Although it showed immense promise to start off with I never solved the problems associated with it.
Very interesting. Thank you for sharing. Let me see if I have this right: Did you re-categorize everything daily, or simply change the order of the categories? I understand how you renumbered them, but I'm not sure whether the number associated with each category changes accordingly, or whether you're essentially pushing things into new categories. The latter seems to make sense for the first few categories, but then how would "new stuff" become "recurring daily"?
If you put something which recurs less than once per day on p. 6 then the following day it is renumbered to p. 5 where it is joined by new stuff coming in that day. The following day it is renumbered to p. 4 where it is joined by daily recurring stuff.
I say "day" but with some versions it would have happened faster than that.
Ah, I see. So it's a conveyor belt toward expiration (like DWM) but with 6 or 7 different kinds of incoming tasks added at different points on the conveyor belt. Fascinating.
The basic problem is that the pages you want to be quick-moving (urgent, incomplete, more than once a day) end up with too many tasks from the slower pages. So they stop being quick-moving. I couldn't find any way of stopping this happening.
Thank you again for sharing this with us. Ever since this thread, I have been brainstorming possible ways to make something like this work. One thing that occurred to me early is that you have too many pages, and therefore too many new items before they start getting weeded out. But decreasing the pages, by itself, is not enough. So I've kept thinking.
An idea has come to mind lately that might be heresy, but let me bounce it off you. Suppose we put "new stuff" on page two. This would mean that incoming new stuff gets filtered out rapidly unless you "touch" it. If something new comes in, you have to do *something* on it tomorrow (even just brainstorming) in order to toss it into play, or it gets eliminated. The best part is, you can always put it back in later if you *really* want or need to, because the system will handle new stuff quickly and keep them from piling up over days.
It occurs to me that Vegheadjones' system (described at http://markforster.squarespace.com/forum/post/2302540 ) handles the problem that Mark describes (non-urgent things clogging up the urgent list), by making the creation of a Hotlist a conscious process, not an automatic one.
Vegheadjones' system seems like a workbench adjacent to a conveyor belt. The workbench is the hotlist, and the conveyor belt is the action book. The conveyor belt is taking things AWAY from the work table. New stuff goes onto the conveyor belt, at the end closer to the workbench. The daily work focuses on the work table, but you can also reach over and grab anything close by from the conveyor belt. Once a week, you look over the whole conveyor belt and see if anything should be moved to the workbench, or thrown away, or redefined.
But there's no dismissal or deletion (other than voluntary), no separate points of incoming work, and it lacks the simplicity and algorithmic nature of Mark's systems, so it's not really comparable to this one. I'm not saying there's anything wrong with it - It looks workable and it clearly works for him. But it isn't really comparable to this one, I don't think.
Austin, I like your thinking. I've been letting your recent idea 'cook' in my head: 1. Urgent 2. New stuff 3. Incomplete 4. Recurring I think there could be something of worth here. Of course, how would this work in a conveyor belt type way? We can't really re-number the previous day's page as that would completely change the catagory and associated items (IE: we don't want "reocurring" to become "Incomplete"...
It works the same way as in the system(s) Mark Forster described above. The categories don't label all the tasks on the page - they only label what sort of tasks get put into the page on a given day. So on your first day of working the system, you might do a recurring task and re-write it on page 4. The next day it will be on page 3, where it will be joined by incoming Incomplete tasks. The recurring task doesn't "become" incomplete; it just sits on the page where incomplete tasks are now being entered. If you do it that day, you re-write it on the new page 4. If you don't, then the next day it's on page 2, where it is joined by incoming "New Stuff." Make sense?
I'm going to have to try to reconstruct it from the hints I gave on the Forum.
In any case, though, thank you for creating the final version, as well as the others. I use FV often and find it very helpful. I'm a graduate student in electrical engineering, and at the end of the semester now I'm finding myself wishing I had used FV more consistently instead of slacking off. I'm going to use it to get a lot of reading done over the winter break, anyway.
The system consisted of having seven pages as follows:
Page 0 Last chance
Page 1 Urgent
Page 2 Incomplete
Page 3 Recurring more than once a day
Page 4 Recurring daily
Page 5 New stuff
Page 6 Recurring less than once a day
The idea was that each day, the pages were renumbered so that Page 0 was deleted - hopefully with nothing on it - and the remaining pages were renumbered so Page 1 became Page 0, Page 2 became Page 1 and so on.
I tried lots of different versions. Some using Page 0 and some not using it. Some changing the pages daily and some changing when there were no further tasks on whatever the first page was. I also tried various methods of going through the pages, e.g. doing the tasks in the order they were written, variations on AF1 and AF2 etc.
Although it showed immense promise to start off with I never solved the problems associated with it.
If you put something which recurs less than once per day on p. 6 then the following day it is renumbered to p. 5 where it is joined by new stuff coming in that day. The following day it is renumbered to p. 4 where it is joined by daily recurring stuff.
I say "day" but with some versions it would have happened faster than that.
The basic problem is that the pages you want to be quick-moving (urgent, incomplete, more than once a day) end up with too many tasks from the slower pages. So they stop being quick-moving. I couldn't find any way of stopping this happening.
Thank you again for sharing this with us. Ever since this thread, I have been brainstorming possible ways to make something like this work. One thing that occurred to me early is that you have too many pages, and therefore too many new items before they start getting weeded out. But decreasing the pages, by itself, is not enough. So I've kept thinking.
An idea has come to mind lately that might be heresy, but let me bounce it off you. Suppose we put "new stuff" on page two. This would mean that incoming new stuff gets filtered out rapidly unless you "touch" it. If something new comes in, you have to do *something* on it tomorrow (even just brainstorming) in order to toss it into play, or it gets eliminated. The best part is, you can always put it back in later if you *really* want or need to, because the system will handle new stuff quickly and keep them from piling up over days.
I'm thinking something like this:
1. Urgent
2. New stuff
3. Incomplete
4. Recurring
What are your thoughts?
Vegheadjones' system seems like a workbench adjacent to a conveyor belt. The workbench is the hotlist, and the conveyor belt is the action book. The conveyor belt is taking things AWAY from the work table. New stuff goes onto the conveyor belt, at the end closer to the workbench. The daily work focuses on the work table, but you can also reach over and grab anything close by from the conveyor belt. Once a week, you look over the whole conveyor belt and see if anything should be moved to the workbench, or thrown away, or redefined.
Here is a picture:
http://www.dropbox.com/s/25td1mkd5a05q7m/hotlist%20conveyor%20belt.png
I like your thinking.
I've been letting your recent idea 'cook' in my head:
1. Urgent
2. New stuff
3. Incomplete
4. Recurring
I think there could be something of worth here. Of course, how would this work in a conveyor belt type way? We can't really re-number the previous day's page as that would completely change the catagory and associated items (IE: we don't want "reocurring" to become "Incomplete"...
It works the same way as in the system(s) Mark Forster described above. The categories don't label all the tasks on the page - they only label what sort of tasks get put into the page on a given day. So on your first day of working the system, you might do a recurring task and re-write it on page 4. The next day it will be on page 3, where it will be joined by incoming Incomplete tasks. The recurring task doesn't "become" incomplete; it just sits on the page where incomplete tasks are now being entered. If you do it that day, you re-write it on the new page 4. If you don't, then the next day it's on page 2, where it is joined by incoming "New Stuff." Make sense?