Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
”What’s 43 Folders?”
43Folders.com is Merlin Mann’s website about finding the time and attention to do your best creative work.
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:
Project ActionsSubmitted by mark_g on February 14, 2006 - 10:48am.
What I try and do is tag the action. For instance "Phone Fred to ask for price ". I then know it is a project action so when complete I should go back to the project record to look for another. From the action and context I know which project to go back to... i.e. "Get Car Fixed". » POSTED IN:
|
|
EXPLORE 43Folders | THE GOOD STUFF |