Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
Relating next actions to projects
Borganizer | Feb 14 2006
Because I am a rule-obeying control freak who's obsessed to do things by the book, I'm wondering about this. I read the book and am preparing to implement this system, but one thing I'm not clear about is how to handle projects. The book says that the "Projects" list is a reminder for my open loops - OK. But - if my project to "Fix car windows" starts with "Call Earl re that mechanic he recommended", which goes on the "Calls" list, when I have called Earl, how do I know it's related to the "Fix car windows" project (which now needs a new next action)? If it were just a handful of projects I could probably keep it in my head, but that approach seems counter to what GTD is about. I guess I could just put some kind of indicator next to "Call Earl about...", like "Car windows: Call Earl...", but first I'd like to know how this should be handled according to the book. I haven't managed to figure it out yet. I have a feeling I'll have a hard time tweaking GTD to fit me if I'm going to be like this all the time... Oh well ;) 7 Comments
POSTED IN:
 If you want/need Palm synchronisation...Submitted by andyc on February 15, 2006 - 8:29am.
StuGib wrote:
If you want/need Palm synchronisation (or even if you don't because it can work standalone), Bonsai v4 also has the 'complete subtasks in order' next action feature like MLO. The advantage of this kind of feature is that you can use a 'define next action' action to automatically remind you to look again at your project once you complete the next 'next action' (if that makes sense?!). I'm another MLO fan. For me, GTD would be unworkable with out some kind of hierarchical manager. » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
