Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
writing a book and have too many next actions
chadgr | Oct 14 2006
Hi. I'm just getting started on GTD while part way into writing a book. I've gone through the collection process and most of the things I wrote as tasks on my mind (and now in my inbox) relate to the book. Perhaps I don't understand how to process the inbox correctly, but I'm wondering whether the whole book should be my one project (with a ton of action items) or if I should break it into subprojects in KGTD (e.g., gather information on issue A, collect photographs for Chapter 5). If I keep it as a single project, it seems I have an unmanageable number of actions each of which could be eligible for a "next action." I hope I'm making sense. Any suggestions would be appreciated. 11 Comments
POSTED IN:
 I think the key thinking is organizing Next ActionsSubmitted by duus on October 14, 2006 - 4:19pm.
They are specific actions, and certainly they are bundled into things with singular goals, right? I would think of each singularish goal as a project. I think it's perfectly fine to have projects and subprojects etc. Don't spend too much time on that kind of organization, though. on my ktgd i have projects and subprojects. the nice things about omnioutliner is that it's trivial to layer those things. I've also taken advantage of GTD's "area of responsibility" thing, which are kinda ongoing bins. So I have an area of responsibility of a class I'm teaching. Projects are like "write midterm exam." Next actions are specific places to look for quesitons, etc. GTD is the most powerful when you break things down into useful ways, not too big. "Write a book" is way, way too big for a project. Identify subgoals. Collect next actions around those subgoals. those are my thoughts. » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
