How to Revise an Email So That People Will Read It
4:35 PM Tuesday April 14, 2009
Tags:Communication
"People think that the first draft is the big event and that revision is cleaning up afterward. But the first draft is really setting up the chairs, tables, and cups, and revision isn't cleaning up after the party, it is the party."
"All first drafts are terrible. I don't care if you're Hemingway."
"What comes out unfiltered from anyone's mind is mud."
The first two quotations come from writing professors whose names I've since forgotten (and they were quoting other people whom they'd forgotten). The last one is one I just made up myself. But regardless of the source, the advice is sound: no email should be clicked-to-send without revision.
I've found that for your average email, the number of revisions largely depends on the number of recipients. Here's my experience:
1 to 5 recipients = 2 to 4 revisions
5 to 10 recipients = 8 to 12 revisions
Company-wide or to Executive Committee = 30 to 50 revisions
Even the simplest missive to one person benefits from a couple of extra passes, and if it's going to the management committee, expect everyone to have changes (and changes to those changes).
Here's a checklist to consider when revising:
1. Delete redundancies. Say it once. That's enough. If you're repetitive, the reader will stop reading and start skimming. (Like you probably just did.)
2. Use numbers and specifics instead of adverbs and adjectives. "The project is currently way behind schedule on major tasks," is not as clear as "The project is 3 weeks late delivering hamburger buns to Des Moines." (If you don't have numbers, still get rid of the adverbs and adjectives.)
3. Add missing context. Does your reader know that hamburger buns in Iowa are required for the company to collect $37 million? If you're not sure, remind them.
4. Focus on the strongest argument. Should those hamburger buns get shipped because the delay is embarrassing for the company, because it's costing children their lunch, or because it's costing the company tens of millions of dollars? Maybe all three, but one of those reasons (and it depends on your reader) will be enough to get buns on the road.
5. Delete off-topic material. The best emails say one thing and say it clearly. One-subject emails also make it easier for the recipient to file the message once they've taken action, something anyone who uses Outlook to manage tasks appreciates.
6. Seek out equivocation and remove it. "It was the best of times, it was the worst of times" works for Dickens, not status reports.
7. Kill your favorites. Is something in your text particularly pithy, amusing, or clever? Chances are, it's not. If it sticks out, it's probably a tap-dancing gorilla in boxer shorts — hilarious when you thought of it, embarrassing when it gets in your manager's inbox.
8. Delete anything written in the heat of emotion. Will this sentence show them who's been right about the hamburger buns since the beginning? Yes? Cut it.
9. Shorten. Remember the reader struggling to digest your message on the run — a BlackBerry or an iPhone gets about 40 words per screen. What looks short on your desktop monitor is an epic epistle on their mobile device.
10. Give it a day. With time, what seemed so urgent may no longer need to be said. And one less email is something everyone will thank you for.
Do you agree that even late-night emails sent from the bar should be revised before sending? (Have you ever seen one the next day?) Have you bravely sent something unrevised only to have it come flying back at you? What's your best advice for revising?
Apr 18, 2009
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2009
(49)
-
▼
April
(13)
- 人生失败的31种原因 - mentat的专栏 - CSDNBlog
- CodeProject: Multi Remote Desktop Client .NET. Fre...
- 6 Cool Websites To Unleash The Mad Scientist Withi...
- 10 Business Words to Ban - David Silverman - Harva...
- How to Revise an Email So That People Will Read It...
- 15 Firefox add-ons for Web developers | Webware - ...
- Six Ways to Ruin Your Resume
- InfoQ: .NET平台下Web测试工具横向比较
- 科技公司nasdaq上市商业计划书
- Networking on the Network
- 25 highly anticipated open-source releases coming ...
- 成为Java高手的25个学习目标 - 湘潭论坛 - 华声论坛
- 长沙特色餐馆推荐 - 混在长沙 - 华声论坛
-
▼
April
(13)
No comments:
Post a Comment