![]() | |
| |||||||
| Home | Register | Blogs | FAQ | Members List | Calendar | Downloads | Arcade | Mark Forums Read |
| TWARM Technical Writers Armenia. Interact with Technical Writers in Armenia. |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 |
| ★★★★★★★★★★★★★ Join Date: Aug 2004 Location: ★★★★★★★★★★★★★
Posts: 16,586
Rep Power: 8 Reputation:
432 | 12 Dec 2000; Jessica Bauer (UWEC student) 23 Jan 2001; edited and expanded by Prof. Jerz ------------------------------------------------------------------ This document offers 10 tips to help you write effective professional e-mails. The informal e-mails you exchange with your friends don't have to meet any particular standards, of course, but if you want to be taken seriously by professionals, you should know e-mail etiquette.
Recipients often scan the subject line first in order to decide which messages to open and which to trash. If you want your message to be read immediately, highlight its importance with a subject headline that piques curiosity (Nucifora) or actually states the substance of your message. -------------------------------------------------------- Subject: "Important! Read Immediately!" -------------------------------------------------------- What is important to you may not be important to your reader. [I have my e-mail filter set to trash e-mail messages with more than one exclamation mark in the subject line. Anyone who shouts at me is being abusive, trying to sell me something, or both. --DGJ] ----------------------------------------------------- Subject: "Meeting" ----------------------------------------------------- The content of this message could be anything from a request for a meeting, the announcement of a cancellation or a rescheduling, or the minutes of a meeting that is already over. ----------------------------------------------------- Subject: "Questions about Meeting" ---------------------------------------------------- Fractionally better. If the recipient recognizes your name, and remembers what the two of you last discussed, then the subject line might be somewhat meaningful. -------------------------------------------------- Subject: "Quarterly report: how do I write the intro?" -------------------------------------------------- Details like this will encourage the recipient to read and respond quickly. 2. Keep the message focused and readable. Stick to two or three short paragraphs. Often recipients only read partway through, hit "reply" as soon as they have something to contribute, and forget to read the rest of the message. If you have multiple subjects, and you really need to address each one, don't be afraid to send multiple messages. Focused:
Avoid attachments unless they are essential, because they
4. Identify yourself clearly. When contacting someone (especially someone you do not know), always include your name, occupation, and any other important identification information in the first few sentences. Identifying yourself will also help the reader decide the context of your message ("E-Mail Ettiquette"). Remember: Your message is not the only one in your receiver's inbox. 5. Be kind. Don't flame. To "flame" someone is to write an abusive personal attack. If you find yourself writing an angry message in the heat of the moment, walk away and cool off before you hit "send". Once you hit send, you cannot take back what you wrote. The "flame" is a long-established Internet tradition. When groups of people gather physically together, they signal status by who gets the comfy chairs, by who gets served and who has to serve, by who can talk and who must listen, etc. Online communities don't provide their members with these signals. Internet communities often use flaming in order to uphold hierarchy, define membership, and forge allegiances -- at the expense of somebody who (intentionally or intentionally) threatens the cohesion of the group. In some ways, social flaming is a rite of passage, like hazing, boot-camp, and ritual cattiness at cocktail parties. But if an employee flames a supervisor, or vice versa, the power differential complicates the situation. No matter how personally intimate the two parties are, the relationship between boss and hireling (or professor and student) is not primarily social. The stakes are different, and so are the rules of etiquette. If you flame your boss or your professor, that message will probably surface someday when you're up for promotion or you want a letter of recommendation. If you flame an underling or student (especially in public), then you damage that person's trust in your leadership, and you probably won't get that person's best work in the future. 6. Proofread. Always run a spell check before hitting send. Studies have shown that messages full of grammatical errors are often sent straight to the trash. Remember: It only takes a few extra seconds to run a spell checker, and it may influence whether your message is read or trashed. While spelling checkers won't catch every mistake, they will certainly help cut down on the number of typographical errors. 7. Don't assume privacy. Don't send anything over e-mail that you wouldn't want posted -- with your name attached -- on a public bulletin board. E-mail is not secure. Just as random pedestrians could easily reach into your mailbox and intercept the envelopes that you send and receive through the post office, a curious hacker, a malicious criminal, or the FBI can easily intercept your e-mail. In some companies, the e-mail administrator has the ability to read any and all e-mail messages (and may fire you if you write anything inappropriate). 8. Distinguish between formal and informal situations. When you are writing to a friend or a close colleague, it is OK to use "smilies" :-) , abbreviations (IIRC for "if I recall correctly", LOL for "laughing out loud," etc.) and nonstandard punctuation and spelling (like that found in instant messaging or chat rooms). These linguistic shortcuts are generally signs of friendly intimacy, like sharing cold pizza with a family friend. If you tried to share that same cold pizza with a first date, or a visiting dignitary, you would give off the impression that you did not really care about the meeting. By the same token, don't use informal language when your reader expects a more formal approach. Always know the situation, and write accordingly. 9. Check your inbox regularly. If you want to appear professional and courteous, make yourself available to your online correspondents. If you do not check your inbox and reply promptly, someone may think you are ignoring his or her message. Remember: Checking your inbox is just like checking your answering machine. [I once had a technical writing intern whose answering machine usually had about 15 or 20 stored messages on it. I didn't hear from her after several tries, and the number of beeps kept getting longer. Then, after the number of beeps got shorter again, I knew that she was working on some of her messages, but that mine were not a priority for her. --DGJ] 10. Always reply promptly. A reply lets senders know that you got their messages. Even if all you can manage is a brief acknowledgement, you are still letting the senders know that you received their messages. Remember: e-mail systems are not flawless, and messages can be lost -- so always reply.
References & Further Reading
__________________ Мадмазель, Медам, Месье! "Глория" меняет курс и направляется в Кейптаун! Кому это не нравится будет расстрелян на месте. (с) http://texneg.livejournal.com |
| | |
| | #2 |
| Ребе - коп! Join Date: Mar 2003 Location: sfba
Posts: 4,196
Rep Power: 6 Reputation:
32 | polezno |
| | |
| | #3 |
| ★★★★★★★★★★★★★ Join Date: Aug 2004 Location: ★★★★★★★★★★★★★
Posts: 16,586
Rep Power: 8 Reputation:
432 | I found the stuff on the web. ![]()
__________________ Мадмазель, Медам, Месье! "Глория" меняет курс и направляется в Кейптаун! Кому это не нравится будет расстрелян на месте. (с) http://texneg.livejournal.com |
| | |
![]() |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Technical Writing for Newbies | Hrach_Techie | TWARM | 2 | Oct 21, 2004 12:46 |
| A course on writing technical reports | Hrach_Techie | TWARM | 0 | Sep 27, 2004 09:34 |
| Spec Writing | Hrach_Techie | TWARM | 1 | Aug 14, 2004 12:20 |
| Certification in Technical Writing | Hrach_Techie | TWARM | 0 | Aug 14, 2004 08:36 |
| Writing skills | neMarina | Jobs | 0 | Mar 27, 2004 07:54 |