Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
Question about projects and lengthy Next Actions
inkedmn | Nov 11 2006
Pardon the rather ambiguous thread title, I just wasn't sure how to phrase it exactly. Anyway, my question... I'm a software developer, but I think many people in IT-related fields will be able to identify with projects like this: I have a list of items that need to be researched. This is the whole scope of the project, in a nutshell. For each item in the list, give some sort of status/resolution. That's pretty much it. Now, this list is pretty long, and will take upwards of a week to complete. How would this project be organized using GTD? Would the Next Action just be "Keep Working Through List"? I'm pretty new to GTD, so I'm trying to feel my way through some of the finer implementation points. Thanks in advance for your feedback! 2 Comments
POSTED IN:
 Now, this list is pretty...Submitted by jason.mcbrayer on November 12, 2006 - 5:41am.
inkedmn;6615 wrote:
The issue is what works for you, not what is orthodox GTD. In my opinion, the best way to handle this would be to make each item on the list a Next Action. If some of them are dependent on others, I'd make those Waiting (in orthodox GTD, Waiting is for responses on things you have delegated, but I also use it for actions with dependencies that haven't been met yet). This way, you can complete and check off individual actions with some frequency, rather than slogging through a single action that never seems to end. » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
