I was blown away by GTD when I read it, and I eagerly started reading 43folders and other related blogs and google groups…but then it dawned on me (I’d like to say “slowly dawned on me”, but it’s not true) that there isn’t a huge amount more to say on the topic…or at least, most of what was getting said NEAR the topic wasn’t all that bottom-line useful.

GTD appealed to me because it embraced a few notions I already had in protean form: always empty your email box, maintain a to-do list, keep the workbench clear so that you can do projects (metaphorically speaking), etc., but it systemized them and extended them to some areas that I still had problems with.

I was a bit het up on GTD and was tempted to go off and code up an linux app (maybe an emacs mode?) to help me implement the system…but I decided to just try - at least for a while - the “next item, by context” lists AND the tickler file AND my list of projects, all in one big text file. I carry a cheap moleskine and a space pen (like every other GTD geek on the planet…at least those who aren’t using Hipster PDAs). I note to-do items in the moleskine when I’m away from the computer. When I get back to the computer, I transfer everything into my Big Text File (tm).

…and you know what?

It works pretty darned well.

Having forced myself into a period of just-use-a-text-file, I’ve (a) stuck with it for 9 months; (b) watched with suprise (and a bit of alarm) as a lot of the folks who are in to GTD spiral down into their own navels (at least, that’s how it looks from the outside).

I think you’ve hit the nail on the head: a lot of GTD folks are trying to complicate what’s a pretty simple idea. Websites full of patterns to print on index cards? Special printers to dump the patterns onto hardcopy? Application this, scriptable tool that…it all has the feel of someone who used to obsess about her relationship with her parents, went into therapy to get over it…and now obsesses about her relationship with her therapist!

May I suggest that folks try not removing merely one part from their big machines (as you suggest), but instead try to fall all the way back to a few folders, one in basket, a notebook, and a pen? (Btw, the Metroplis scene you mention is a great analogy!)

Literally just-this-morning, bumbed that 43F had spiralled into it’s navel, I unsubscribed from the RSS feed…then changed my mind, hoping that something clarifying, as opposed to complexifying and obscuring would come down the pike.

I think your post above is a step back towards clarifying and simplifying…go for it!

TJIC wrote:

“I think you’ve hit the nail on the head: a lot of GTD folks are trying to complicate what’s a pretty simple idea. Websites full of patterns to print on index cards?”

Wake up, Watson: there’s irony afoot! ;-)

yours truly, Doug “Beginner’s Mind” “DIY Planner” Johnston

great points TJIC, one of the most interesting things I’ve read about GTD is that David Allen implements the system using nothing but the out of the box software on a palm pilot.

I get a sad pang in my gut when I think of all the hours I’ve spent trying to achieve “mind-like-water.”

Merlin, earlier you said (to losely paraphrase): One hallmark of a geek is that they’re willing to spend 11-1/2 hours coding a script to do something that would take 12 hours to do by hand? But thru the pursuit of something like GTD methodology, I’m taking hours in the hundreds in the hope of saving a few dozen. he ratio has somehow gotten inverted: it takes 20 hours to accomplish thru a system what I could do in 11-1/2 if I just broke down and started stuffing the damned envelopes (metaphorically speaking).

I would rather be bored/boring and get my obligations out of the way so I have time to relax … I would rather be frustrated/anxious but be struggling with procrastination face-to-face, rather than by channeling that energy into creating a system that will supposedly help me in the long term … I would rather spend a HUNDRED hours learning to relax, let go, and be OK with making decisions that allow me to relax and enjoy my life NOW, rather than once all the “first things first” have been accomplished … than I would spend any more time trying to get my system up and running.

Of course, this isn’t to say I won’t be back on your blog tomorrow morning — you’ve got a zillion great “tricks,” many of which I keep around (like an assortment of rachets) to get me unstuck.

But I am going to have to say goodbye to all this GTD stuff.

I remember spending HOURS at the kitchen table with my index cards trying to figure out what my NHA would be for this and that, how to keep my Someday/Maybes straight, how this fed into that and what to do when “xyz” could be listed on 2 different cards. It didn’t last long. Time to revisit this and start off SMALL… Thanks for the article and taking it back to where it belongs

What Brian describes is common to geeks — that script doesn’t even need to save half an hour, it can even take longer than the original task, if writing the script is more fun than the task itself. But that’s not the point of all of this. I’ve commented before that, as a novice woodworker, I’ve noticed that a lot of woodworkers seem to use the hobby mostly as an excuse to fiddle with their workshop. If that’s what floats your boat, great, but again, that’s not the point of this stuff.

On a slightly different note, my current ‘system’ really fell into place when I abandoned the computer altogether. It’s all paper (most of it in my day-timer).

As a OCD programmer, I too was enamored by the GTD system. The Hipster PDA was great, but it was hard to carry a lot of info. I tried so many different programs and books, but I’ve come back to a simpler place. Two things helped me see the light:

1. That David Allen only uses out-of-the-box Palm software (as noted above).
2. Merlin’s comment (somewhere) that “GTD is about action, not playing with lists”. That comment was so important to me that I noted it on my Treo, though I reworded it: “GTD is about getting things done, not playing with lists.”

Here are my simplifications:

1. I just use the out-of-the-box Palm software: Calendar and Tasks.
2. I reduced the number of my @contexts to just: @Work, @Home, @Weekend (a catch-all for random errands, weekend adventures, and free time, though it overlaps with @Home), @Laptop (which overlaps with @Home and @Weekend), and @Vacation. I would add @Phone, but I usually call people @Work, @Home, or @Weekend.
3. I ensure ALL my tasks include an action verb. This is pedantic, but it helps me focus on ACTION!
4. I don’t keep a separate Someday/Maybe list. Everything must be in a @Context. For Someday/Maybes, I create a task without a Due Date.
5. I don’t keep a separate Waiting-For list. As Merlin has pointed out before, Waiting-For is just another action. I turn Waiting-Fors into actionable tasks such as “Ping Joe re trip report” (with or without Due Dates).
6. I don’t keep a separate Projects List. Everything is an action in a @Context. If the Palm allowed tasks to have multiple categories, I would tag tasks with @Context and +Project. Fortunately, this is not a big problem because each project action must be done SOMEWHERE, so I just dump actions into the appropriate @Contexts.

With my new Less Is More system, I hope to finally stop gazing at my navel and start getting things done <;)

I just posted this on Bert Webb’s GTD blog and it seems germane here, too:

And now that I think about it, the way that I write down and annotate projects and next actions really doesn’t matter. (As long as I’m doing all that writing and annotating in one single system, rather than several systems scattered around.) What matters is that after I’ve written it down, I will come back to it the next week, reread it, reconsider it, and rewrite it if necessary. Clever methods of annotation and filing will not save me if I do not do a weekly review, every week. They are only useful if they make it easier to do the weekly review.

And now that I think about this, I think I’m really just paraphrasing something that I’ve seen Merlin write here previously. And I’m also probably paraphrasing a key point that from the GTD book or seminar recording. But it’s something I need to keep reminding myself of.

I appreciate the sentiments found here. I’ve settled on a few pages in Backpack to keep my list on, and a small note-book I carry with me when I go out.

I find 43 folders really good reading, and I come here nearly every day.

However, the very fact of having a blog about this kind of stuff means that Merlin has to keep introducing us to new methods and hacks. So, there is a contradiction of sorts: A system that works is stable and invisible, whereas a blog is all about the new and untried.

I think there is something to be said for system experimentation. I know I did a lot of that before I settled on the system I’m using now, which itself is the product of several iterations around the core components. And I may update it yet.

The system that works best for Merlin will not necessarily be the best for someone else. So even if Merlin has a system that works for him, I appreciate his efforts to expose people to new ideas-for-system-parts, so that other people can try them out and find what works for them.