Eugene,
Way back with AF1, Mark stressed the importance of rewriting the item on the bottom of the list if you are going to need to do it again or if it's an ongoing project.
If you "forget" to add the item again to the list, you won't trust your list, and the system is no longer a system. It fails.
So, I err on the side of rewriting items on the bottom of the list. If I didn't really need to, no harm done. I can always cross it off. If I needed to, but didn't. That good be a big problem.
Conclusion: I learned early on that AF only works if I develop the habit of rewriting items that recur, or are ongoing projects, at the bottom of the list, even as I am still working on them in the middle of the list.
What I do when I've selected a line on my AF list to work on, is to put a dot next to the item that I am currently working on. That way, if I get interrupted and lose my place, I just glance at my list and I am reminded to return to the current item.
If I have an item that recurs or is part of an ongoing project, IMMEDIATELY AFTER WRITING THE DOT, I rewrite the item or project name at the bottom of my list.
Regarding project lists, what I have found, and I think many here have had similar experiences, is that I do not need to maintain a project list for most of the stuff that is on my AF list. A lot of stuff is self-evident.
But I do have a fair number of multi-item projects that I do anticipate will stretch out over many weeks, or longer. I tend to create project plans for the kinds of projects that have many items that stretch out over longer periods of time. Here, the tasks required are often self-evident, but I tend to lose track of what I have done when I am only doing small tasks spaced out over long periods of time.
I always write either the project name or the next task at the bottom of my AF list. I might not need or be able to work the next task for 2 more weeks, but this serves as a reminder that the project is still ongoing.
17 January 2010 at 14:10 | moises