It took a while before I could find the time to search this old comment on Merlin Mann's 43Folders website. Yesterday I was lucky to find it again. It describes a GTD system - deemed successful by it's author - which turns out to be the same as the system described in GED. Actually it is GED plus GTD lists. Minus most features of the broader GED approach. Or something like that.
The comment is from 2006 but I remembered it all the years in the back of my head for some reason. Is this "scientific" prove that GED works? Is this somebody who read GED and is omitting due credit? What happened? The given explanation is plausible, IMHO.
Anyway, here is the comment:
Submitted by mkb (not verified) on October 2, 2006 - 8:43am. Any time somebody can combine D&D, vomit, and GTD in the same essay, I am a happy reader. Great post, Merlin. You hinted at a problem that bears emphasizing: Many of us have a tendency to fall into one of two traps. Either we go heads-down on our Priority One task to the exclusion of all else, or we get so caught up in minutia that our P1 doesn't get attention. We can't stay in either mode for very long without causing problems. Yes, I must work on the code that has to be ready for QA on Friday, but my boss asked me an unrelated question via email that only needs a two sentence reply. He's going to be pissed if I don't get back to him, but if I open up my email client I risk getting sucked in for hours and not getting my code done. After years of struggling with this, I finally seem to have it licked by combining GTD with your dash idea. I keep an index card on my desk with a list of task areas: email, branch updates (it's a programmer thing), personal tasks, straighten, check in with boss, check in with project manager, etc. When I first arrive at my desk, I give each category a dash of activity, usually starting with five minutes each. Any categories that need attention get a second, longer pass. I use a timer, since watching the clock is too easily fudged. The dashes force me to prioritize within each category and prevent me from wandering off into the weeds. Pretty quickly I have the minutia under control and can roll up my sleeves for some serious coding. Often I'll revisit the dashes again later in the day-- usually after a natural break like lunch, bathroom trip, or an interruption by a coworker --but many days I find that I don't need to revisit at all and can just follow my nose.
The comment is from 2006 but I remembered it all the years in the back of my head for some reason. Is this "scientific" prove that GED works? Is this somebody who read GED and is omitting due credit? What happened? The given explanation is plausible, IMHO.
Anyway, here is the comment:
Submitted by mkb (not verified) on October 2, 2006 - 8:43am.
Any time somebody can combine D&D, vomit, and GTD in the same essay, I am a happy reader. Great post, Merlin.
You hinted at a problem that bears emphasizing: Many of us have a tendency to fall into one of two traps. Either we go heads-down on our Priority One task to the exclusion of all else, or we get so caught up in minutia that our P1 doesn't get attention. We can't stay in either mode for very long without causing problems.
Yes, I must work on the code that has to be ready for QA on Friday, but my boss asked me an unrelated question via email that only needs a two sentence reply. He's going to be pissed if I don't get back to him, but if I open up my email client I risk getting sucked in for hours and not getting my code done.
After years of struggling with this, I finally seem to have it licked by combining GTD with your dash idea. I keep an index card on my desk with a list of task areas: email, branch updates (it's a programmer thing), personal tasks, straighten, check in with boss, check in with project manager, etc. When I first arrive at my desk, I give each category a dash of activity, usually starting with five minutes each. Any categories that need attention get a second, longer pass. I use a timer, since watching the clock is too easily fudged.
The dashes force me to prioritize within each category and prevent me from wandering off into the weeds. Pretty quickly I have the minutia under control and can roll up my sleeves for some serious coding. Often I'll revisit the dashes again later in the day-- usually after a natural break like lunch, bathroom trip, or an interruption by a coworker --but many days I find that I don't need to revisit at all and can just follow my nose.
http://www.43folders.com/node/47671/323013