Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
43F Google Group: How big is a project?
Merlin Mann | Jun 30 2005
Google Groups : 43 Folders [How big is a project?] Good thread on the Google Group about what constitutes a project, especially in terms of the GTD sense of the word (defined in the book as “a desired result that requires more than one action step”). I also used to find it confusing that there seemed to be an implication that you should only have one “next action” per project, which, gratefully, was completely a misreading on my part; you should have at least one next action per project, but you can and should have as many captured next actions as you know of. As I read it, the important part is that, if they’re on your TODO list, they need to be the next physical thing you could do to keep things moving—as opposed to stuff that can’t or shouldn’t be done yet for whatever reason (time, dependencies, waiting on other people, etc.). That deeper “back of the envelope” planning should happen in project support materials so that your TODO list is exclusively stuff that’s tee’d up and ready to go. Related posts:
Two completely off-topic observations:
6 Comments
POSTED IN:
 One thing I think needs...Submitted by Kendall Sutton (not verified) on July 1, 2005 - 3:11am.
One thing I think needs to exist is some sort of prerequisite system in a personal or group project management system. What I mean is that you should be able to create some sort of heirarchy of the project in some form, with all the actions having pre-requisites. When an action has all of it's pre-requisites completed, it becomes available and is tossed to your next action list, now that it is doable-- or something like that. » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
