As I mentioned last time, don't choose a tool that doesn't fit your flow. What does that mean? Here's an example: I thought I'd be clever and create a separate flow for home and work. Since I work at home, the thinking was that I'd further separate my two worlds with two systems. In one corner I had The Hit List syncing to iCal which in turn was syncing with Todo on my iPhone. In the other corner: Toodledoo in my browser (or standalone in Fluid) and on my iPhone. Guess what happened?

I wound up preferring one system over another. In this case, Toodledo (a service I'll dissect in a later post). Todo and The Hit List and even lowly iCal are great, but since the majority of my inbox items fly at me in a work context, I simply wound up using Toodledo more often. That simple cognitive shift of changing to another system wound up enough of a barrier to me to discontinue my hacked-together system. Oh, and it didn't help that my hacked system didn't work right.

The Hit List is a very powerful tool, and iCal works great with my MobileMe account. The hack to sync the two with Todo, also a terrific piece of software, only works so well. My second piece of advice this week: avoid hacked solutions unless you can fix them easily. This goes back to truly learning your system. If you can code your own apps and craft your own workflow, more power to you. If you can't, admit that you won't be able to fix things and look for a total solution elsewhere.

Case in point: so-called Kinkless GTD. Remember this one? I loved it. Add items via QuickSilver into a special, fragile OmniOutliner Pro document and all sorts of magical things happened. Unfortunately, the system was fragile as a glass kitten. Once it blew up on me once, I never got it working again, and had to unlearn a number of methods for capturing and completing tasks. That is not the way to get things done. But the toolset was beyond my capacity to fix it. So take a lesson from Star Trek and don't become dependent upon a tool you can't fathom. Or, at the least, find something with support documentation.

Next I'll show you some questions to ask when evaluating tools.

Let me be totally honest here: I am not the world's leading expert on GTD. Nor have I completely settled on a true, universal solution -- because I don't think one really exists. Like most complex problems, there are many approaches, and very few true solutions. Plus, everyone has a different workflow and circumstance, so there's no way to prescribe something for everyone. That said, you will find patterns in GTD implementations (which is kind of the point, especially if you're adhering to a particular type of system -- Behance's Action Method or Zen to Done or whatever).

The point of GTD is pretty simple: get things accomplished effectively and efficiently. How you do that is by 1) making sure you are collecting everything you need to do, 2) managing the lists of to-do's and supporting materials, 3) acting upon the items on the lists in an efficient way. Simple in concept, and devilishly complex in action. It's that big, gray fuzzy area people have so much trouble with, since GTD is a process with a set of tools, not a paint-by-numbers exercise. Over the coming months I'll keep tweaking my workflow and reporting what I've found. We'll take a look at some popular systems, and ways to craft your own in different configurations.

As I said, everyone works a certain way, and there's no one-size-fits-all approach. I'll try to take into account the various approaches to GTD. Contexts, for example, are a variable for many people. Contexts in GTD refer to the "where" you're likely to do something. You don't need to see your "buy milk" to do at work, do you? Contexts help keep lists separate. Some people like a broad set of contexts, like @work and @home and perhaps a couple more. Other folks are meticulous with contexts and creating numerous sub-tasks with proper tags within each.

This week I'll lay out some ground rules for those of you looking to get started with GTD quickly, and what you can expect when choosing a set of tools. But most importantly, what are the things you need to do to ensure you'll actually use whatever system you choose?