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.
A 'Next actions' question -GTD newbie question
akapulko2020 | May 8 2006
Hi all , Let's say that I have a project which is to mail some books to a friend of mine .So first I need to get her adress :this contains of an action of emailing her ,then waiting for her reply. What I can't figure out ,is whether I should have all those listed as next actions in their separate contexts ,for the same project ,at the same time -ort should I enter the first action,then complete it ,and only then add the next action to it's context? I mean ,in most cases there are numerous and dependent actions in a project ,which belong to different contexts,right? I'm using the "nextaction" tracking tool for managing my next actions,and there's no way of defining dependency there -but the mail question is ,how is this supposed to work,the real-GTD way? Thanks :) 24 Comments
POSTED IN:
Hi all , After reading most...Submitted by Berko on May 8, 2006 - 6:39am.
akapulko2020 wrote: Hi all , This is perhaps one of the most frustrating answers in the world, but whatever works for you. Think of it in terms of your review. Do you plan to get all of it done before your next scheduled review? (Notice I said scheduled review, not when you actually do it!) If so, then put all the actions on their respective context lists. Otherwise, decide how much you are going to do this week or however much time and put those on the lists and update at your next review. An important distinction to make in GTD is implementing the methodology and becoming a slave to dogma. The point being that there are a certain amount of rules that you can break and still "do" GTD. For instance, Emory will list entire projects that only contain a few actions on the context card rather than creating a project for it. This technically goes against GTD principles, but it works for him. Personally, I have to do a review more often than once a week or I start to load my life back into my mental RAM. Ethan Schoonover posted a great discussion of GTD orthodoxy and adaptation at the kinkless site. That might be a good read for you even if you aren't using kGTD. This post is going to be abbreviated since I still have two paper to write that are overdue and I shouldn't be writing this post at all. I hope this gives you a good start. » POSTED IN:
|
|
EXPLORE 43Folders | THE GOOD STUFF |