June 15, 2011

Email's Not for Skimming

Communication is a funny thing.

Some say that this electronic era makes it difficult to connect with people, because things like texts and emails don't allow for tone-of-voice or body language. It's a compelling argument.

I think, though, that people make it hard to connect with people.

Case in point:
   I emailed the Associated Press to ask for information about licensing an image we wanted to use for a show, and I sent it from my school account to make sure it was official (it's a .uk address). After I signed my name I also listed out the full name of the school, and added a comma London. The response I got (in a fairly timely manner, so the AP has that going for it) stated that they couldn't give out information until they knew the location of the licensee, when they would forward the email to the correct office.

   I was a little befuddled. I looked back through my email - and yes, I included both the facts that the show was through my school and the name of the school comma London. As I scrolled down further I discovered that emails sent from my school have footers attached to them, which include terms like "London", "England", and "Wales", just in case you were unsure which side of the globe to point at.

   It seems to me that, particularly in a business setting, it's a good idea to ACTUALLY READ THE EMAIL all the way through before asking a question that is answered in that original email. It could be just me, though.

Case 2:
   In setting up a meeting with a tutor we went back and forth on days and times, and finally settled on Wednesday at 4:30. I responded again with "Where? In the school? Or at the Hampstead?" (a next-door theatre where the lobby is a cafe where people often meet.) His answer - "In the lobby."

   Now see, that's a tricky one, answering a question where the 'conclusion' applies to both suggestions... Keeps things exciting, I suppose.

* * * * *

Apropos of nothing, I'd like us all to pull out our best American Redneck voices and chorus along:

No comments: