Wednesday, May 27, 2009

Avoiding sounding like a jerk in emails

Below is the full text from a blog written by David Silverman (not David Silver) about helping with tone in email. I know this is something I've struggled with in the past, so I thought it might be useful to others as well.

A reader writes with the following query:

"I manage 15 staff who are scattered about. I email them since it's the easiest way for me to communicate with all of them at the same time. Often my emails are very short and to the point. It's business. Two staff see that as my being harsh and have no problem letting me know that. Example: "Would you please update these primary care providers in the database, including addresses and phone numbers?"
Six days later, I sent the following email as follow up to my initial request: "I would like this taken care of by Thursday this week. If you are having trouble getting this done, please let me know."

In return, my employee sent me a lengthy 4 paragraph response on how insulted she was by my follow up email. I would like your opinion."

One the one hand, the employee's response was out of line. What was he or she hoping to achieve? It didn't get the project done and it almost certainly didn't improve your relationship. I'd go as far as to say it's justified for you to reprimand someone for aggressive behavior like that.

But that's me speaking as a boss (or customer) who's sent similar emails to yours. I've also been the recipient — and felt rising anger every time one of my bosses sent an email beginnging with, "Please provide the revised presentation..."

Perhaps unexpectedly, it was the "please" that drove me over the edge. And while I didn't fire off a petulant four-paragraph response, I did seethe quietly. And, more importantly, I didn't feel very much like "providing the revised presentation."

Anyone whose ever been part of an online "flame war" has had the experience of a tiny "e-mole" becoming a mountain. (And yes, I am also shocked that I would attempt such a terrible pun.) Studies have shown that readers add (or invent) emotional bias that is often counter to your intent as the sender.

In this case, all of the niceties you thought you were writing ended up sounding very different in the mind of your employee.

In the echo chamber of the employee's mind, and the absence of other cues from you, "I would like" was probably heard as a passive-aggressive demand, if not a derisive sneer. "If you are having trouble," was meant as "I'm here to help," but interpreted as "I think you're a dolt for taking 6 days to do a minor task." The length of your email also compounded the emotional dissonance. You thought of it as just a quick note on a task, but your brevity came across as curt.

Lastly, the form of communication itself (email) could be interpreted as, "Just so you know, I'm documenting your incompetence."

Ouch, right?

Here are some suggestions for preventing this next time:

1. You could call. Your goal is to check the progress of the task and give the employee a chance to respond with questions — a call could accomplish this while allowing both of you to hear each other's tone of voice. Since you say at least two of your staff find your emails harsh, this could be the easiest solution.

2. Include deadlines when you first make a request. If you don't have time to call, or if time zones make calling a hassle, email can still work if you revise your initial request to include a due date, or, for a bigger project, a due date for an status update. By giving a date, your follow-up won't feel as aggressive and your employee will be less likely to take it personally. Deadlines will also help your staff prioritize — perhaps rendering follow-ups unnecessary.

3. Be conversational. Even if the first email was unchanged, the second email could be written to avoid a blow up. You don't need lots of smiley faces or exclamation points. You just need to write the way you might actually talk. For example, your second email could read: "Hi Cindy, just following up on the email below — can you let me know how far along the task is? I was hoping we could have this by the meeting on Thursday, is that a possibility?"

4. Use the passive voice. It doesn't make for great writing, but it can help you avoid sounding accusatory — and it sounds like your employee felt accused.

To handle the situation as it is now, call. Let your employee know you meant no disrespect, and that your goal, and theirs, was and is to get the job done. And let them know that the I'm-an-emotional-person-and-you-hurt me email has no place at work.

Lastly, I'd like to use this as an opportunity to repeat why I think even the "simplest" emails need to be revised with care. It takes time and thought to ensure you don't give the wrong emotional cues.

Let's open this up to my readers and get you some more opinions. Does anyone have other advice? Do you disagree with the recommendations I've proposed?

No comments: