I received an interesting request last week from one of my colleagues:<\/p>\n
“Please provide an\u00a0update on the [gene name] ozone OCD”.<\/p><\/blockquote>\n
The email in question was sent to me, several other colleagues, and some of our external collaborators. The tell-tale “sent from my iPhone” text at the bottom pointed to an\u00a0autocorrect<\/a> error, but none of us had any idea what the original request might have been. This was therefore a clear-cut case of having to draw the sender’s attention to the error in order to fulfill the request; the PI replied with “how isogenic lines was changed to ozone OCD is a mystery to me<\/em>“, and the problem was solved with much hilarity all around.<\/p>\n
A more ambiguous situation arose a few hours later. As often happens, I needed to reply to a mass email – again, sent to external collaborators as well as\u00a0internal staff – that included a glaring typo in the subject heading. As much as I loathe<\/em> to send anything out in my name with an error in it, I decided (after much deliberation) not to correct it, thinking that a correction might draw extra attention to my colleague’s mistake.<\/p>\n
As I said, this happens quite often: I work with a lot of busy, multi-tasking people who send hasty emails from iPhones and Blackberries – or just in a rush from their desk while simultaneously on a teleconference call, eating lunch, and\/or reading a draft manuscript. If I’m the only recipient I just ignore the mistake, but if there’s a big group involved – especially if it includes external contacts or other big-wigs – and\/or if the conversation looks likely to run and run, with multiple people sending replies, I find it very hard not to correct the typo.<\/p>\n
Now, I’m paid to be anal about typos. It’s a big part of my job to clean up manuscripts, grants, progress reports, press releases, websites, and other pieces before they’re sent out into the wild to fend for themselves. However, it’s a big part of my personality to not be rude to people, especially my superiors at work. I’m also a chronic over-thinker<\/a>. So I decided to seek input from the home of lots of other over-thinking editor types – Twitter!<\/p>\n
I sent out the following tweet:<\/p>\n
Etiquette question: do you correct typos in email subject lines when you reply to them, or is that a passive-aggressive douchebag move?<\/p><\/blockquote>\n
and received quite the response!<\/p>\n
(NB: any typos in quoted text are from the original tweets :D)<\/p>\n
On the pro-correction side, people said:<\/strong><\/p>\n
\n
- “Yes. Chances are they won’t notice, but it’ll make you feel better.”<\/li>\n
- “That’s the kind of decision that would keep me up at night. I think correcting the typo is ok though… :s”<\/li>\n
- “I correct typos\/mistakes in subject lines of emails all the time — just because I’m obsessive like that.” followed by “If the email is going out to a whole group, I figure I’m doing the original sender a favor ….”<\/li>\n
- “passive aggressive – maybe, bad etiquette\/douchebaggy – no.”<\/li>\n
- “I don’t see that as an “or” question. My answers are “yes” and “yes.” :)” (tweeter subsequently admitted that the answer to the question “and do you care?” is “no!”)<\/li>\n
- “I’d rather be perceived as passive-aggressive, thus I’d correct subject line”<\/li>\n
- “I would correct it. The other person may not even notice that it got corrected if they let such an egregious error pass.”<\/li>\n
- “I even correct tweets I RT. I dunno about “passive aggressive”. I think of it as being “kind and helpful” ;)”<\/li>\n<\/ul>\n
On the “OMG, what is WRONG with you?!” side, people said:<\/strong><\/p>\n
\n
- “I’m not sure if this is the right answer but I would let it go.” followed by “I suppose if it is being circulated, it wouldn’t have been too douchey.”<\/li>\n
- “no, because it breaks gmail’s conversation feature if the subject changes. I think. I would change it before fwd though” (NB: I would never, ever, correct a typo in a friend’s email subject heading – and I only use Gmail for friends’ emails! I’m talking about work emails, in Outlook).<\/em><\/li>\n
- “The real questions are, of course, would they notice? & more importantly would you want them to notice?#ThinkingTooMuch<\/a>“<\/li>\n
- “I pretend I didn’t notice\/read the title”<\/li>\n
- “passive aggressive and retentive my dear.” followed by “i\u00a0know but its an email and i don’t know, it just seems anal…mind you I have people proof read important emails.”<\/li>\n<\/ul>\n
<\/a><\/div>\nMany thanks to everyone who provided input!<\/p>\n
So, Oh Wise Occam’s Readers… what do you think?!<\/p>\n
(p.s. I’ve checked this post for typos several times, but I just KNOW there’s going to be one in there that I’ve missed!)<\/p>\n","protected":false},"excerpt":{"rendered":"
I received an interesting request last week from one of my colleagues: “Please provide an\u00a0update on the [gene name] ozone OCD”. The email in question was sent to me, several other colleagues, and some of our external collaborators. The tell-tale … Continue reading