I’m Ryan, and you can usually find me in the midst of my workday by following the trail of naked yaks. I fear that I’m drawn to arcane tasks not in spite of the fact that they are tangential to my ultimate goals, but precisely because they give me an excuse to avoid them. I don’t need to grapple with the big anxiety-evoking issues of how to make a new one of my companies make more money, for example, if I can instead focus on creating an elaborate triply-redundant, auto-rotating archival filing system for our Apache server logs (which we never look at.)

However, I recently encountered a weirdly tantalizing idea in Tim Ferriss’s The 4-Hour Workweek, which would ultimately disrupt my addiction to the extraneous. The book advocates farming out the more mundane tasks of your existence to outside firms and consultants, which Ferriss calls “outsourcing your life.” Probably because it would give me an excuse not to do something else more pressing, I decided to give this a go a few months ago. While I did learn quite a lot about outsourcing in the process, my experiments led me to a far grander epiphany about the way I approach life and work generally and helped me form a new set of habits that have utterly rocked my workaday world. I’m about to introduce you to the theory and practice of what I believe to be the forgotten Prime Minister of All Productivity Hacks: asking for help.

The Problem

GTD is all about rapid, intuitive selection of what you need to be working on now. Whip out your context list appropriate for the time-place-opportunity-space you are in now. Scan through it, then do.

For the longest time I was having a problem with this. I'd scan through my context lists and I'd see things like:

Inbox Zero Tech Talk
7/23/2007
00:58:38

During the Q&A portion of my Inbox Zero presentation at Google the other day, an audience member stumped me with a question about how to manage action around mailing list distributions (the question starts at about 48:22).

He said he frequently receives email requests and questions that are also distributed to the other 20 people on his team. He describes a "waiting game" in which team members hang back to see if other people will respond first -- at least partly out of not wanting to duplicate effort or flood the sender. I thought it was a really intriguing question, although I said (and still believe) that distributed email would not personally be my first choice to handle this kind of communication.

Well, based on the reaction in the room that day, I gathered that this is a common dilemma for Googlers. Funny thing is that, since the video went up, I've received a lot of email from people outside the Googleplex who share the same problem -- a few of whom were aghast that I wasn't aware what a huge pain this is for knowledge workers. And to an extent, I'll admit those folks were mostly right.