T
Tetsujin
Guest
Like many others, I've found the 2-minute rule to be an enormously powerful tool when processing "IN." Gets a lot of stuff done and moving forward before it even has a chance to stall.
Has anyone had experience, positive or negative, in using the rule when doing the Weekly Review?
Here's an example of how this might come up: An action item comes up when I'm on the go. I write it down and dump it into my portable "IN" folder.
Later, I'm processing "IN" into my system, and I come upon the action item. It's not a big action, but for some reason I can't do it while processing right then and there (because I'm on a plane, or it's 2am and the action is to call someone, or whatever). So the action goes onto a context-based action list to be done later.
A few days later, I'm doing my weekly review, and while reviewing my context action lists I come upon this action item. It hasn't been done yet, and in the present time and place I could do the action in two minutes. But I'm not in processing mode -- I'm doing my weekly review!
Does it make sense to pause the review in order to knock off the action? Or better to leave the action on the list to be done later, and not leave the high-level strategic mindset of the WR by getting bogged down in a runway-level action?
Like everything else in GTD I know the real answer is "Do whatever works best for you." I'm just interested in thought or experiences anyone might be able to share.
-T.
Has anyone had experience, positive or negative, in using the rule when doing the Weekly Review?
Here's an example of how this might come up: An action item comes up when I'm on the go. I write it down and dump it into my portable "IN" folder.
Later, I'm processing "IN" into my system, and I come upon the action item. It's not a big action, but for some reason I can't do it while processing right then and there (because I'm on a plane, or it's 2am and the action is to call someone, or whatever). So the action goes onto a context-based action list to be done later.
A few days later, I'm doing my weekly review, and while reviewing my context action lists I come upon this action item. It hasn't been done yet, and in the present time and place I could do the action in two minutes. But I'm not in processing mode -- I'm doing my weekly review!
Does it make sense to pause the review in order to knock off the action? Or better to leave the action on the list to be done later, and not leave the high-level strategic mindset of the WR by getting bogged down in a runway-level action?
Like everything else in GTD I know the real answer is "Do whatever works best for you." I'm just interested in thought or experiences anyone might be able to share.
-T.