On an average day, I receive about 50 emails an hour exclusive of any spam and any comments on any of the Weblogs, Inc blogs. Now, if I’ve been posting regularly on various blogs, then you can easily go anywhere from double that number to quadruple that number. I barely even ever glance at my spam folder any longer to check and see if there are any issues. Also, due to the international status of the Internet, while the regular email of about 50 emails an hour trickles to 1 to 2 emails an hour during what are the nighttime hours in America, the comments keep on accumulating over night. The point is, I get a lot of email.

Now, fortunately, years of graduate studies and grading student papers have made me a very fast and accurate reader. I can skim for important bits better than most, so it’s easy to separate the wheat from the chaff in those numerous reader comments. I mean it is nice to hear “Cool! Thanks!” and funny (at times) to read “You’re an idiot. You suck!”, but neither of these comments are anything that adds real value to the conversation on the blogs, so I can more or less skip through them easily. What is useful, helpful, and warrants more attention from me are comments like “You could do it this way much quicker” or “This cool program does it better and it’s free” or “You’re wrong in step 5.” So I mark them as flagged and keep on parsing through the emails, then go revisit them and see what’s what.

These skills are part of what make me a good blogger. I’m subscribed to a very long list of RSS feeds and can fire up Bloglines and skim through them for important bits in an amazingly short amount of time. I don’t mean to brag, but I’m a veritable RSS-reading ninja, as I can usually multitask and skim through while I am talking to someone on the phone or having a conversation with someone face to face. I know what I am looking for and I simply click, launch in new tab to review later, and keep on skimming while I talk on about whatever issue I am dealing with on the phone. Thanks to Saft, there are no worries with this method, because if Safari crashes, I can relaunch and it will remember all those tabs I had open.

In addition to all this, i usually have iChat running and am involved in about 5-10 IM conversations at any given moment from 7am to 11pm with a few gaps for commuting and eating and such. Only about 2-3 of these conversations ever tend to be like a normal conversation, where both myself and the other person are chatting regularly and then end the conversation. The rest of them are more like conversations in spurts where both parties are discussing something important and then right when one party asks some important question, the other party goes missing for a good 5-10 minutes due to a phone call or something else and pops back up with the answer to the question later, out of context, and when neither the question nor the answer are relevant any longer.

Now, I think I manage pretty well with all these paradigms. There is rarely a time when I personally overlook some important tidbit that has been exchanged via email, IM, or RSS (When it does happen it is an email, and it is a low priority email that I put in my back-burner file and then forget about for one day too long). However, all of these paradigms are more or less broken depending upon the capabilities and workloads of the other people involved in these conversations. I know several people that get so much email that they only promptly read the ones that HAVE ALL CAPS YOU MUST READ THIS NOW FOR THIS REASON subject lines, and even then, there is a substantial lag in response time. So, usually with these people I instant message them.

The problem with instant messaging is the reverse. Everything is too much a conversation of the instant. Most of the people I know who do not have the time or capacity to read through all their numerous emails are necessarily very busy people and therefore are only available for IM conversations for a few moments each day and you have to hit the window just right to exchange the information you need. Often the results will be: “Send me that in an email,” and then I have to follow up with another chat reminding of the email, etc. Or, the problem is that everything is solved in the chat, but down the road something goes a little awry and due to the flitting nature of chat the short convo we had has been forgotten and there is no readily available documentation to support that the answer to question n was given as x and that’s why such and such was done.

So, in any case, it seems to me that both email and chat are broken as communication forms. Blogging offers some hope. Jason Calacanis, for example, recently blogged that he was going to be out of the office[archived] and added the following note:

(Note: It’s interesting, these days the best way for me to get information out to my team and peeps is with the blog–not email. Blogs are the new email!)

Now, this is great for a general broadcast out of office message with an easy to spot headline, but the assumption here is that his peeps are reading his blog. Or that those peeps while reading his blog didn’t for whatever reason skim over this particular post. Even with blogs there is missed information and skipped bits.

So what’s the solution to these problems? Is it just a side-effect of information overload and unavoidable? Is better parsing of information needed? These issues effect me in all my endeavors in our new Internet age on a daily basis and I would imagine that they are starting to effect more and more people, not just those that are bloggers working simultaneously for a blogging group and in a regular 9-5 technical administrative position in education.

Leave a Reply

Trending