Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
Linked next actions?
juman | Feb 21 2006
Say I have a small project like replacing the tires of my car which could look like this in a mission statement... Mission (should you choose to accept it) : replace tires Steps : Breaking this down to actions: Several of these I can begin with at once, the collecting information parts as get number, get tire type etc. But I can't call anyone until I got their numbers. But still all this work can be done in a day if I just pass the diffrent containers during the day. So should I add all these things to my contextlists even if they are not do-able right now? Or should I keep the undo-able things and add them at the daily review for the next day? Such a thing can drag a little project like this for days. How do you keep track of these things? I mainly use paperbased contextlists but any idea is welcome :) 8 Comments
POSTED IN:
 I've found that this method...Submitted by Lachia on March 26, 2006 - 2:49pm.
I've found that this method works well for me: Every night when I prepare for the next day (determining which TODO's to accomplish and being sure I have the correct references for each...i.e. making sure the info is in the correct file and that I have it in the correct place) I will make a notation, follwing the NA on the TODO list that denotes subsequent and related NA's. This way, I know that as I cross an action off my list I should also check the related project file... this way I can PROCESS the following NA and determine when it should be completed. Did that make sense? » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
