-
I am enchanted with the new AF. However, there is one thing I don't like, and more than that, I don't understand why it should be so: The paradigm shift from the "let dismissed items in peace for some time and reenter them only after a week or longer"-rule in AF1-3 (and in the original AF1 rule set, there was put very much emphasis on this rule!!) to the new "dismiss and decide almost immediately what to do with the dismissed items, either re-enter (reworded) or delete"-rule of AF4.
I have to admit that in the beginning (AF1-era), I felt uneasy with dismissals for a very long time. It was only when I went through my old lists after months and had a look on what was highlighted, I suddenly realized that really most of what had been dismissed had been RIGHTFULLY dismissed - tasks that appeared far more important at the time I entered them that they were with hindsight. So, I came to peace with dismissals, and I started to like the fact that AFs dismissal processing was creating a "someday/maybe"-list automatically, without any additional work besides the simple highlighting.
I know for sure that were I forced to decide about the fate of these rightfully dismissed tasks IMMEDIATELY, I would have re-entered most of them, thus creating unnecessary work for me!
So, I won't adopt this part of the new rule-set. I will simply dismiss the backlog/closed list when appropriate (on no task standing out on first pass), highlight the remaining tasks and leave it alone: This appears more natural, too.
Apart from that, AF4 "is it". A real stroke of genius.
5 September 2009 at 9:09 | AndreasE
-
Hi there
I can see where you're coming from but last night when I drew my first line for AF4 I decided to treat my existing 'dismissed', i.e. highlighted tasks, as if I was processing them in AF4 and it felt really liberating to realise that they aren't relevant at the moment, they could be crossed off and that they would come back into my head if they ever do become relevant again.
I guess there might be a fear that you lose a good idea along the way but my list didn't include any of them ;-)
Lucy
5 September 2009 at 9:29 | Lucy
-
Andreas:
I suggest you try it before rejecting it. I've found that this type of dismissal suits this system well.
As I said somewhere in the Comments on the live demo, I would probably not have dismissed so many tasks if I had not had an audience to whom I wanted to demonstrate the dismissal process. It would have been more like two or three at most.
5 September 2009 at 10:26 | Mark Forster
-
OK. I'll try it. You are right, I should not judge the system before having it used according to the word at least some time.
It was only because I had this "Wow" again I had when I came across AF1 - only that one tiny details didn't "wow" me... :-)
5 September 2009 at 11:01 | AndreasE
-
Hmm - I'm not sure whether to try this one. I'm wondering whether the idea to give a talk (which led to a very rewarding project) would have been dismissed in AF4. It took a while to germinate and grow in AF1 and I think it needed the time to inculcate. I wonder if AF4 would allow intuition as much influence as in AF1. Having said that, I have been in reverse mode most of the time of late in RAF, so the same applies there too.
I'm also not sure how the automatic planning of projects (adding ideas as they come to mind) will work in AF4, as they often require some time before actioning. Perhaps the concept is to offload them to a separate project file/list.
Hanging in there with RAF till people come in with comments.
Meanwhile I have also been considering trying an AF1 type method, but using contiguous groups of unchecked tasks in place of pages, and being able to move in either direction through the list.
5 September 2009 at 11:25 | Laurence
-
Laurence:
<< I'm wondering whether the idea to give a talk (which led to a very rewarding project) would have been dismissed in AF4 >>
What's the problem if it is dimissed? All that happens is that you have a chance to think about the idea to see if it is still a goer before re-entering it on the Active List immediately.
5 September 2009 at 11:49 | Mark Forster
-
If I understand it correctly highlighted and crossed out items are either dismissed or reentered into the list. So there is no explicit journaling in the list of dismissed items. This could create a greater hesitation to dismiss (my memory has the consistency of Emmental).
An alternative could be to cross out only the items that are reentered as the orthodox dismissal is a single pass and it is clear what the state of the list is. But then the dismissal lacks any physical action and that's probably worse.
5 September 2009 at 11:59 | Damien
-
Damien:
I'm not quite sure that I understand your post, but here's a summary of what happens with dismissal in AF4:
1) You visit the Backlog and no tasks get done: Highlight all the tasks in the Backlog and convert the existing Active List into the new Backlog.
2) Continue through the new Backlog until you reach the end of the Backlog.
3) Return to the beginning of the list.
4) Cross out all the highlighted tasks. They may be discarded or re-entered, etc.
5) Continue working through the Backlog and so on.
5 September 2009 at 14:21 | Mark Forster
-
Mark,
Here is the point I'm not clear about.
After marking items for dismissal and converting the Active List into the new Backlog, do you
A) Continue through the new backlog (multicycle) AND the active list before returning to delete the dismissed items?
Or
B) Read through the new backlog once, and count the dismissed items as part of your backlog and delete them immediately?
Your instructions (to me) seem to indicate A, but your response to Damien seems to indicate B.
5 September 2009 at 15:41 | Sabrina
-
Sabrina:
B) is correct. I've amended the instructions to make them slightly clearer on this point.
5 September 2009 at 16:16 | Mark Forster
-
Sabrina,
In another thread Seraphim wrote "Move the Line to the end of the Open List (so now, all items are on the new Closed List)."
Understanding the list after the move of the line as one closed list makes clear, at least to me, that the loop begins from the top, where the first highlighted item is.
5 September 2009 at 17:01 | Jiru
-
Thanks Mark and Jiru - makes sense to me now.
5 September 2009 at 17:10 | Sabrina
-
Amazing!
One week ago I started experimenting with AF2 ("Backward Mode") with a similar "Review Mode" policy.
When reviewing, I start browsing my dismissed tasks, and for each of them I decide between:
- Doing it
- Reenter/Rephrasing it
- Destroying it
This way, I keep using AF2's excellent management of urgent items, while promoting older tasks to the end of the list on a frequent basis (or doing them, or killing them). They can't stay idle.
This deals with AF2's shortcomings (not giving enough attention to older stuff), and proved to be very dynamic.
Now I'm going to try AF4, but I must say that this method worked really, really good for me. What a pity! :-)
5 September 2009 at 17:16 | Walter
-
As I mentioned in a blog comment, I'll definitely try this before dismissing (!) it, but it does seem to me that the threat of dismissal is greatly weakened. Earlier versions of AF always said "please take seriously the instruction to let dismissed items stand for a while..." and the reason for this, I thought, was to make dismissal something real and serious — thus making it a good way of distinguishing between tasks you're procrastinating on but really care about, vs. tasks that need weeding out of the system. With AF4, it seems likely that in a few days my brain will learn that dismissing is no big deal, eliminating this very useful filter in the system. BUT... I will try it! I promise!
5 September 2009 at 18:15 | ludlow
-
I'm a long time AF1 user. AF2 and RAF didn't appeal to me, but this new system I like: it eliminates the artificiality of the single-page sublists.
I basically use it as an AF1 list with two pages: HEAD and TAIL. The HEAD is the last, open page, never dismissed. The TAIL gets dismissed if no action is taken. I tried it and already finished my first (short) backlog. No dismissals this time.
The thing is: I always liked the AF1 dismissal rules. Dismissed items would stay around forever. That allowed me to put stuff on the list as I thought about it. Of course, I couldn't do all of it NOW. But I liked the way AF sorted out what I decided to do. The rest stayed around. It was dismissed, but nothing was really wrong with it, apart from the fact that you cannot everything at once. AF4, on the other hand, says to handle your dismissed items (almost) immediatly. So I decided to handle the dismissed items the AF1 way.
Well … so I thought. The more I think about it, the more I believe the AF4 way is right.
Why? Let me explain. Some information doesn't belong in a todo list. Some people wanted priorities, but I always thought priorities don't really belong on the list. That doesn't mean you shouldn't set priorities or think about your goals. But once on the todo list, all tasks are equal. Priorities distract from the autoFOCUS part.
Same thing with the indeterminately dismissed items. Dismissing in AF1 partially regains focus, but only partially. AF4 seems to force you to decide what to do with the TAIL, if you don't work on it. Are the tasks unclear? Are they still urgent? Or is this not the right time to do them?
Handling the AF4 TAIL is more work, because you must decide what to do with the dismissed items. On the one hand, that is a big drawback. You have to maintain an extra list with ideas and someday-items. On the other hand, the focus is clearer. We will see how this will turn out.
AF4 already made me do some tasks I wouldn't have done otherwise. I still don't really know how to feel about that.
5 September 2009 at 18:29 | Olaf B
-
I had similar concerns about the new dismissal rules, which I posted to the "AF4 in Brief" discussion. I'm re-posting the same comments here.
Assuming I am understanding the rules correctly, the one thing that has me a bit worried is the built-in automated processing of the highlighted items.
I'm not so sure I like having them deleted like that. I could always put them in my tickler system, but I kind of like the way AF1 would keep them percolating as long as I needed them to, with my periodic "review dismissed items". It was up to me to decide whether to delete, rewrite, put on the tickler, or whatever.
That was my initial reaction, at least.
Upon further thought, some additional things occurred to me.
(1) Mark's demo was in "high speed". He himself said it would normally take several days to work through a Closed List before any of the items got highlighted. And then it might still take a while before he got to the point of deleting those items. So, the percolation effect is still in play.
(2) In some ways the added discipline is really appealing: being forced to deal with highlighted items, forced to make a decision, not just letting them sit there to be reviewed occasionally.
(3) Maybe the new deletion of highlighted items changes the psychology of the system (for better, or for worse?), and maybe it will mean lots of rewriting and redispositioning of highlighted tasks. But I'll just have to give it a try and see how I like it.
5 September 2009 at 18:56 | Seraphim
-
Seraphim:
>> (2) In some ways the added discipline is really appealing: being forced to deal with highlighted items, forced to make a decision, not just letting them sit there to be reviewed occasionally. <<
Good point. This is exactly why I feel dismissal in AF4 has actually been strengthened. In previous systems, dismissing an item was just another way of not dealing with it - it could linger on your list for days. In AF4 you are forced to make a decision either way.
I started using AF4 yesterday and nothing has been dismissed yet. As soon as I felt like there was a closed list again, items I had been putting off magically got done.
5 September 2009 at 19:48 | Sabrina
-
"I started using AF4 yesterday and nothing has been dismissed yet. As soon as I felt like there was a closed list again, items I had been putting off magically got done."
Same here - I've also been tackling tasks that I've previously managed to avoid, thanks to the feeling of having a solid closed list again...not really felt that since AF1.
It has been quite eye-opening for me how just a tiny shift in intent for a list produces such dramatically different outcomes. It certainly highlights just how subtle are the energies and dynamics at work here.
5 September 2009 at 21:30 | Frank
-
Hi Olaf,
>>> I'm a long time AF1 user. AF2 and RAF didn't appeal to me, but this new system I like: it eliminates the artificiality of the single-page sublists.
I basically use it as an AF1 list with two pages: HEAD and TAIL. The HEAD is the last, open page, never dismissed. The TAIL gets dismissed if no action is taken. I tried it and already finished my first (short) backlog. No dismissals this time. <<<
Hmmm, is that a different set of processing rules? I'm asking because I'm thinking of keeping the last open page as part of the new ope list.
>>> The thing is: I always liked the AF1 dismissal rules. Dismissed items would stay around forever. That allowed me to put stuff on the list as I thought about it. Of course, I couldn't do all of it NOW. <<<
Yes, that is the grass catcher feature that is not found in traditional To Do lists.
>>> Why? Let me explain. Some information doesn't belong in a todo list. <<<
Yes, that's true.
>>> Some people wanted priorities, but I always thought priorities don't really belong on the list. <<<
Why do you say that? Priorities have always been an integral part of To Do lists. They are either placed as a tag on each item or the items are sequenced in priority order and you work from the top to the bottom in order.
>>> That doesn't mean you shouldn't set priorities or think about your goals. But once on the todo list, all tasks are equal. Priorities distract from the autoFOCUS part. <<<
As Mark envisioned, yes that is true. But priorities CAN coexist with AF in various ways that some here have invented. Personally, my priorities exist outside of AF and AF works within my priority system. Much as it seem you are saying. But that is not the only way.
>>> Same thing with the indeterminately dismissed items. Dismissing in AF1 partially regains focus, but only partially. AF4 seems to force you to decide what to do with the TAIL, if you don't work on it. Are the tasks unclear? Are they still urgent? Or is this not the right time to do them? <<<
Do you think that might depend on how you work the list? In AF1 the instruction is, IIRC, to analyze you dismissed a task and take appropriate action.
>>> AF4 already made me do some tasks I wouldn't have done otherwise. I still don't really know how to feel about that. <<<
LOL ;-)
5 September 2009 at 22:34 | Mike
-
Sabrina,
>>> Good point. This is exactly why I feel dismissal in AF4 has actually been strengthened. In previous systems, dismissing an item was just another way of not dealing with it - it could linger on your list for days. In AF4 you are forced to make a decision either way. <<<
Yeah, but you could make the decision to endlessly add them back to the list ... which is just putting off a decision.
And, as I have come to understand that the AF lists (all of them) are also grass catchers, I archive my dismissed items ... even in the new system.
5 September 2009 at 22:38 | Mike
-
Mike-
If you archive your old items in AF4, you won't be able to tell the ones that were added back from the ones that have just been left undone (dismissed). All the highlighted items get crossed off on the next pass.
I think I like the way AF1 marked dismissed items better. Highlighted, but only crossed off if you did make a conscious decision to never do it or if you had added it back to the last page. Otherwise, it remained highlighted to look at during a review. In other words, it was archived. But I do like that you are forced to review them shortly after highlighting them. It is only the marking that I think may be done differently.
6 September 2009 at 5:32 | MartyH
-
Marty,
Well, I'll only arcive the ones that are "fully" dismissed. IOW, I'll add the back what I want to and archive the rest. IIRC, Mark is working from a bound book so everything he has dismissed is basically archived. IOW, he can go back and browse at will.
6 September 2009 at 9:04 | Mike
-
I am also a bit concerned about readding dismissed tasks to the open list. Is it really how it should work?
6 September 2009 at 10:01 | Greg
-
Greg,
Yes, but only if you think you should add them back. If not, just let them go.
Step through Andreas demo to watch it all unfold.
6 September 2009 at 10:12 | Mike
-
Mike,
Can you direct us to the demo?
Thanks,
--Joseph
6 September 2009 at 12:32 | Joseph
-
6 September 2009 at 12:35 | Andreas Hofmann
-
Mike,
I have seen Andreas presentation - which is very clear to me, but anyway - for me this rule creates possibility of endless task rewriting instead of doing something with it (decision) - like you mentioned in your previous reply. I would not feel pressure that I have to do this task (or even small part) - or this it would be dismissed, I will always feel free to skip unwanted tasks, because they can be easily readded. I know it sounds stupid, but I know I will act in that manner - that's why I need so badly Mark's AF.
6 September 2009 at 13:27 | Greg
-
Greg,
I hear 'ya. But the thing is, even under AF1, you could review dismissed tasks and add them back. And, thinking about it in the widest possible context, you can "cheat" any system if you really want to.
Why not just take a moment ... a LONG moment ... over each task in the backlog that you skip over and really think about what it means to you, why you put it there in the first place, etc. I mean, it all comes down to what you want out of life, yes? No one is holding a gun to your head ... and you don't have to either. Just put tasks on there that you WILL do because you WANT to do them ... and then remind yourself that you put them there because you wanted to do them. Then just stare the task down!
Add a new rule to your AF4 system: "I will never re-add a task unless it can't be done now because of contextual constraints." That ought to do it ;-) In fact, Mark suggested (strongly, I thought) that the task be reworded when it was re-added. I.E. Chunk it Down when you re-add it. Can't bring yourself to start doing your taxes? Re-add the task as: "Buy Tax Software". Or ... "Pull Last Years Tax File Folder from Cabinet and Read it over".
You might think about shifting your focus from being controlled by your feelings about a task to being in control of it. Just a thought or two that might help.
6 September 2009 at 16:10 | Mike
-
"I would not feel pressure that I have to do this task (or even small part) - or this it would be dismissed, I will always feel free to skip unwanted tasks, because they can be easily readded."
This is a good point, and ultimately, the problem with all these systems (the real problem being ourselves). At the end of the day, you still have to:
* open your book/software
* follow the rules
* defeat your own nature
And that's why there will always be room for David Seah, David Allen, Mark Forster, and Merlin Mann to promote their next system, designed to, defeat your nature. It won't, but the hope remains.
6 September 2009 at 16:47 | Avrum
-
Mike-
If you archive by rewriting to an archive list that serves as a "someday" list, that works. I archive by just clipping old pages together so they remain, but are out of the way.
Reviewing the dismissed tasks in the archive then consists of looking at tasks that are highlighted (dismissed), but not crossed out (actioned in some way including a decision never to come back to it). If a task is ever actioned or rewritten, it is crossed off.
I guess ultimately, my way will end up with an outrageous number of pages! But I am still on my first book since January, so it's not an issue.
6 September 2009 at 17:23 | MartyH
-
Hmm, I have never felt that AF (any iteration) helps me "defeat my nature". In fact, I find the opposite -- it helps me "make the most" of my nature. The AF rules are designed to accommodate human nature and the psychology of getting things done, rather than opposing it.
Yes, I have to "make myself" pick up my book and start working through it, and sometimes I just want to start working on whatever it is I just want to do right now. But I have been learning more and more to just use the system (whichever version it happens to be at the time), because it is such a small price to pay with such a great payback.
AF has a tremendous "pull" to it -- I really don't feel myself having to force myself to use the system. Even when I do just start doing whatever I want without referring to the book, I feel it "calling" me, and I usually heed that call, because it's just so much more FUN (and productive) to use the AF list.
In the day and a half that I've been using AF4, that feeling of "fun" and "pull" is even stronger than with previous iterations.
And one nice thing about AF4 is that you really can just jump directly to whatever is on your mind, by adding it to the end of the open list, and just not having anything else "feel ready to be done". If you've just started working the Closed List, you can touch one item very quickly to avoid dismissing the whole lot, and skim through the rest (or just flip past them), then go to your Open List, skip through everything to the very end, and behold, you are now working on whatever it was that just popped into your head (or got thrown onto your desk by your boss). (*)
Maybe the fact that one is allowed to do this, will bring out the perversity in our natures and completely undermine the whole system. So far, I don't find that happening. And I am certainly the kind of person who will naturally gravitate towards doing anything I can to undermine the system. :-)
(*) The only time the rules prevent you from doing this is when you happen to be working through a bunch of highlighted items on the closed list -- the rules say you must deal with each of them somehow. If you've got 20 or 30 of them, it can really slow you down for a bit.
6 September 2009 at 17:36 | Seraphim
-
Yes renaming task of course helps, but I would like to keep system pure - and I just have a feeling that this is some kind of tweak (so instead of readd you have to rename - this is against rules, because you can readd without changing anything). But ok, I think I will work for a few days and see how it works - but unfortunate I am bit concerned about my nature :)
6 September 2009 at 20:24 | Greg
-
Greg,
No, it is NOT against the rules. It is suggested by Mark. And what is so important about the "rules"? It has to work for you. Rules are not sacred things that must not be violated. There is no "purity". Just do what works for you.
6 September 2009 at 21:47 | Mike
-
Ok Mike,
I will do it that way, thank you for your help.
7 September 2009 at 7:36 | Greg
-
Greg,
Let us know how you get on with it.
7 September 2009 at 12:25 | Mike
-
Mark:
<
<< I'm wondering whether the idea to give a talk (which led to a very rewarding project) would have been dismissed in AF4 >>
What's the problem if it is dimissed? All that happens is that you have a chance to think about the idea to see if it is still a goer before re-entering it on the Active List immediately.>
I think there is a class of ideas which - after a day or three - seem whimsical and might be dismissed under AF4 (as one might not at that time feel like copying it them to the end when the the backlog expansion time comes). But sometimes - a week or two later - when the idea might have survived still with AF1, there has been time for the idea to develop more subconsciously and one might think, when the page is facing dismissal, that maybe that it's more than whimsy after all. However whether this applies to the example I was thinking of in my post above, I do not know all these months later.
In the scientific spirit I have been trying AF4. I took the previous few days' entries as the initial backlog, and so far everything is being actioned within at most 4 days, making it the most effective AF variant so far for me. I have a repeating task to add three items from AF3.
AF3/RAF enabled me to work with one list, but AF4 is leading me to create separate lists for some projects, as sometimes when it is time to adjust the backlog, the highlighted items are more suitably addressed in a different place or context - so naturally it is leading me back to using multiple lists, which I find interesting.
For those who fear missing super-urgent tasks if the Open List be long, perhaps it is worth adjusting the rules to work both lists in reverse direction.
9 September 2009 at 10:57 | Laurence
-
Laurence,
>>> I think there is a class of ideas which - after a day or three - seem whimsical and might be dismissed under AF4 (as one might not at that time feel like copying it them to the end when the the backlog expansion time comes). But sometimes - a week or two later - when the idea might have survived still with AF1, there has been time for the idea to develop more subconsciously and one might think, when the page is facing dismissal, that maybe that it's more than whimsy after all. However whether this applies to the example I was thinking of in my post above, I do not know all these months later. <<<
But the tasks remain in AF4. All you have to do is periodically go back through your book and review the highlighted ones. Even if they were not copied, they are still there. The only change from previous AF versions is that they have a line through them. You can still read what they were.
9 September 2009 at 11:25 | Mike
-
Laurence,
In my experience those whimsical ideas generally pop back after a while - it's partly that which lets you know they're something you genuinely want to do, rather than as a result of some fad.
A time management system is not designed to replace your mind, and contrary to popular belief, it is not against the rules to actually remember something that isn't written down!
9 September 2009 at 13:04 | Ed C
-
Ed,
>>> A time management system is not designed to replace your mind, and contrary to popular belief, it is not against the rules to actually remember something that isn't written down! <<<
ROTFLMAO ;-)
9 September 2009 at 14:12 | Mike