<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Solution to a common e-mail problem</title>
	<atom:link href="http://www.hrmorning.com/solution-to-a-common-e-mail-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hrmorning.com/solution-to-a-common-e-mail-problem/</link>
	<description>Your daily dose of HR</description>
	<lastBuildDate>Wed, 17 Mar 2010 21:49:46 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bob</title>
		<link>http://www.hrmorning.com/solution-to-a-common-e-mail-problem/comment-page-1/#comment-26604</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Tue, 22 Sep 2009 19:59:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrmorning.com/?p=4466#comment-26604</guid>
		<description>Always do the following before clicking send on ANY e-mail:

1.  Spell Check.  Most e-mail programs today have built-in spell check.  SPELL CHECK.  Making a simple spelling error makes you look stupid.  Outlook can be configured to spell check automatically under advanced options.

2.  Proof Read.  Read what you are about to send, making sure you said what you INTENDED to say.  Look for areas of your e-mail that could be misinterpreted.  &quot;One-liners&quot; should get a &quot;once-over&quot;, but longer e-mails should be read 2 to 3 times to make sure you&#039;re not making an a$$ out of yourself.

3.  Attach files.  How many times have you fired off an e-mail without attachments?  It happens to all of us.  Sending it to your boss&#039;s boss can make you look incompetent.

4.  Attach THE RIGHT files.  See #2 --- Don&#039;t send &quot;Customer A&quot; a document for &quot;Customer B&quot; or vice-versa.  Don&#039;t send employee reviews to the wrong employee.

5.  Review the thread.  In long-threaded e-mails, sometimes there can be something buried two or three replies ago, that could be derogatory or condescending, or something brief that could be misinterpreted as harsh.  Best policy:  Trim off what is not needed.  In long-threaded e-mails, scan for areas where people are mentioned by name, or deficiencies are called out by name or instance.

6.  Check your signature.  If you use an automated signature, make sure the job title, company, and contact information are correct, and that you are using the correct formality - informal for &quot;one-liners&quot; and to those that know you, and formal for those that don&#039;t know you or don&#039;t interact with you frequently.  Don&#039;t send &quot;one-liners&quot; to people who don&#039;t know you.

DO THESE THINGS EVERY TIME YOU SEND AN E-MAIL.

Do not send in haste.... take a few seconds to review your thoughts before you send them out.  Eventually, taking a quick second look becomes a good habit, and takes little time or effort.</description>
		<content:encoded><![CDATA[<p>Always do the following before clicking send on ANY e-mail:</p>
<p>1.  Spell Check.  Most e-mail programs today have built-in spell check.  SPELL CHECK.  Making a simple spelling error makes you look stupid.  Outlook can be configured to spell check automatically under advanced options.</p>
<p>2.  Proof Read.  Read what you are about to send, making sure you said what you INTENDED to say.  Look for areas of your e-mail that could be misinterpreted.  &#8220;One-liners&#8221; should get a &#8220;once-over&#8221;, but longer e-mails should be read 2 to 3 times to make sure you&#8217;re not making an a$$ out of yourself.</p>
<p>3.  Attach files.  How many times have you fired off an e-mail without attachments?  It happens to all of us.  Sending it to your boss&#8217;s boss can make you look incompetent.</p>
<p>4.  Attach THE RIGHT files.  See #2 &#8212; Don&#8217;t send &#8220;Customer A&#8221; a document for &#8220;Customer B&#8221; or vice-versa.  Don&#8217;t send employee reviews to the wrong employee.</p>
<p>5.  Review the thread.  In long-threaded e-mails, sometimes there can be something buried two or three replies ago, that could be derogatory or condescending, or something brief that could be misinterpreted as harsh.  Best policy:  Trim off what is not needed.  In long-threaded e-mails, scan for areas where people are mentioned by name, or deficiencies are called out by name or instance.</p>
<p>6.  Check your signature.  If you use an automated signature, make sure the job title, company, and contact information are correct, and that you are using the correct formality &#8211; informal for &#8220;one-liners&#8221; and to those that know you, and formal for those that don&#8217;t know you or don&#8217;t interact with you frequently.  Don&#8217;t send &#8220;one-liners&#8221; to people who don&#8217;t know you.</p>
<p>DO THESE THINGS EVERY TIME YOU SEND AN E-MAIL.</p>
<p>Do not send in haste&#8230;. take a few seconds to review your thoughts before you send them out.  Eventually, taking a quick second look becomes a good habit, and takes little time or effort.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- This site's performance optimized by W3 Total Cache. Dramatically improve the speed and reliability of your blog!

Learn more about our WordPress Plugins: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (user agent is rejected)
Database Caching 6/13 queries in 0.012 seconds using disk

Served from: lamp02.pbp.com @ 2010-03-17 17:58:12 -->