Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
hPDA Twins and Orphans
Jamie Phelps | Jul 24 2006
One of the things that used to frustrate me about GTD and particularly with using an hPDA was that I would do my project planning on a project card and then put those actions on a context card. Then I would have two separate versions of the same action (twins in kGTD terminology). Then, invariably, I would update either my project or context card when I completed the action, but never both, resulting in the orphaning of one of those twins. (To add to the madness, I would update project card for some actions and context card for other actions, which made it near impossible to keep track of it all.) This weekend (my first real "weekly review" in the several months of doing GTD), I had an epiphany. During my review, I move actions to my context cards. When the action gets moved, it is going to be finished, so I mark it off on my card even though it isn't finished yet. Perhaps an example... Project: Groom the lawn So, when I promote "Buy weed eater line" to my @Errands shopping list, I mark it off on the "Groom the lawn" project card. That way, if I look at my project card, I know that that action has moved on to greener pastures. Anyway, I hope this helps some of you out there struggling with the redundancy of some of our lofi tools. 1 Comment
POSTED IN:
 Great idea! You're right to suggest...Submitted by mdl on July 25, 2006 - 6:44am.
Great idea! You're right to suggest that once something gets added to a context list, it's going to get done--or be deferred, tossed out, etc. In the past, I've handled syncs between context and project cards in the following way: To move from projects to context: To move from contexts to projects: The project cards are thus for planning and reference, while the context cards are where the action happens. » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
