43 Folders

Back to Work

Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.

Join us via RSS, iTunes, or at 5by5.tv.

”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

Hi all ,
After reading most of the "getting things done " book , there is one thing that I don't really understand as far as Next actions are concerned.

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.
Then there's the action of packing the books [@home ] and then there's an "errands" type of action of going to the post office and mailing it.

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 :)

a11en's picture

Hey Kenzi and Solidsnot! Yup, that's...

Hey Kenzi and Solidsnot!

Yup, that's exactly how I use the system as well. With one exception. For me, in general, most of the items in the project are actually steps that are not dependent on each other, and almost all of them are next-actions. Some of them are related to each other, and therefore do require a next-action/not-next-action type of situation. So, it tends to make things a bit difficult to use the purple-color. Often I'm working somewhere down the list, due to resources, or what-have-you (whim and fancy on what to work on next)- all of them needing to get done of course. So, none of them are really and truly the next-action in the project list... all of them could be. Then, to confuse the mix, a few brothers-sisters that are dependent on another one... However, I see I should probably be using sub-projects and sub-sub-projects much more than I do. This might help solve the dependency issues I'm having.

Not sure if that makes sense or not.

BTW, kGTD is awesome, I don't meant to belittle it here at all, I just mean to point out that the NA listing is pretty useless to me without some way to make more than 1 task in a project an NA. For me, just because they all fall under main project A, doesn't mean there isn't more than 1 thing to get done with equal weight.




An Oblique Strategy:
Honor thy error as a hidden intention


Subscribe with Google Reader

Subscribe on Netvibes

Add to Technorati Favorites

Subscribe on Pageflakes

Add RSS feed

The Podcast Feed


Merlin used to crank. He’s not cranking any more.

This is an essay about family, priorities, and Shakey’s Pizza, and it’s probably the best thing he’s written. »

Scared Shitless

Merlin’s scared. You’re scared. Everybody is scared.

This is the video of Merlin’s keynote at Webstock 2011. The one where he cried. You should watch it. »