Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
Vox Pop: Managing actions from list emails?
Merlin Mann | Jul 30 2007
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. I do know about the pain of being on multiple email lists, and it's why I've spent the last ten years trying desperately to stay off of them. I also know and dread the poorly-worded action request that requires vivisection with a magnifying glass and tweezers. But I suppose I never really thought about the cumulative effects that distribution lists can have across a company -- especially given the geometric nature of their influence, and especially if some 500 emails a day must be monitored and processed for potential action items. That's just stunning to me. So: open thread for you email veterans to chime in... How does your team handle these sorts of distributed requests? How are you personally managing possible actions that stem from email distributions? Are there success stories for the distributed email approach? Anyone found better media than email for managing this stuff? Do we all just need to make our peace with getting 2,000 interoffice emails a week, and move on? What's the solution? 39 Comments
POSTED IN:
 My team that works as...Submitted by Charles (not verified) on July 30, 2007 - 10:37am.
My team that works as production support for several applications does what many others have written about. The on-call person for the week has the responsability for answering all emails that are sent to our group. If the email is for a problem or a request for service, they are sent back a email telling team to open a problem ticket or request ticket to our team. General information emails are answered by the on-call person, topics that a specific person is the best to handle are sent to that person. The important thing is that problems and requests for services are sent into tools that are better at tracking status and generating metrics than email. If a SLA is missed because the problem was reported only in a email it is on the sender. If it is missed and it was in the problem tracking tool it is on us. This doesn't happen often or at all because of the tracking features in the tool. » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
