<?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: You&#8217;ve Got Etiquette: Email Ethics at the Office</title>
	<atom:link href="http://www.thestylesheet.com/featured-articles/2008/03/youve-got-etiquette-email-ethics-at-the-office/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thestylesheet.com/featured-articles/2008/03/youve-got-etiquette-email-ethics-at-the-office/</link>
	<description>For businesses that use the internet</description>
	<lastBuildDate>Fri, 27 Jan 2012 17:23:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Sarah Buser</title>
		<link>http://www.thestylesheet.com/featured-articles/2008/03/youve-got-etiquette-email-ethics-at-the-office/comment-page-1/#comment-32</link>
		<dc:creator>Sarah Buser</dc:creator>
		<pubDate>Mon, 17 Mar 2008 20:21:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.thestylesheet.com/featured-articles/2008/03/you%e2%80%99ve-got-etiquette-email-ethics-at-the-office/#comment-32</guid>
		<description>Thanks, Patti! I appreciate it. That&#039;s a really good way to put it - it&#039;s scary when you think that anything you write in a company email could be used against you like that later. Yikes!</description>
		<content:encoded><![CDATA[<p>Thanks, Patti! I appreciate it. That&#8217;s a really good way to put it &#8211; it&#8217;s scary when you think that anything you write in a company email could be used against you like that later. Yikes!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patti DeNucci</title>
		<link>http://www.thestylesheet.com/featured-articles/2008/03/youve-got-etiquette-email-ethics-at-the-office/comment-page-1/#comment-31</link>
		<dc:creator>Patti DeNucci</dc:creator>
		<pubDate>Mon, 17 Mar 2008 18:26:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.thestylesheet.com/featured-articles/2008/03/you%e2%80%99ve-got-etiquette-email-ethics-at-the-office/#comment-31</guid>
		<description>Excellent article! Lots of good common sense that is so easy to forget!
I also read in the Statesman yesterday that you should never write in an email anything that you&#039;d read out loud in a court of law. Whew! That&#039;s good advice too!</description>
		<content:encoded><![CDATA[<p>Excellent article! Lots of good common sense that is so easy to forget!<br />
I also read in the Statesman yesterday that you should never write in an email anything that you&#8217;d read out loud in a court of law. Whew! That&#8217;s good advice too!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Weynand</title>
		<link>http://www.thestylesheet.com/featured-articles/2008/03/youve-got-etiquette-email-ethics-at-the-office/comment-page-1/#comment-30</link>
		<dc:creator>Nick Weynand</dc:creator>
		<pubDate>Sat, 15 Mar 2008 16:37:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.thestylesheet.com/featured-articles/2008/03/you%e2%80%99ve-got-etiquette-email-ethics-at-the-office/#comment-30</guid>
		<description>I agree with Bob, except for chopping off the previous replies.  I think it&#039;s helpful to have a thread to refer back to.  If you chop off the previous replies then they could be lost forever. Probably just a matter of preference.

Also, one more thing: Some people&#039;s email clients reply to messages at the bottom instead of the top.  This always confuses me for a bit until I figure out what&#039;s going on.

-Nick</description>
		<content:encoded><![CDATA[<p>I agree with Bob, except for chopping off the previous replies.  I think it&#8217;s helpful to have a thread to refer back to.  If you chop off the previous replies then they could be lost forever. Probably just a matter of preference.</p>
<p>Also, one more thing: Some people&#8217;s email clients reply to messages at the bottom instead of the top.  This always confuses me for a bit until I figure out what&#8217;s going on.</p>
<p>-Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Paver</title>
		<link>http://www.thestylesheet.com/featured-articles/2008/03/youve-got-etiquette-email-ethics-at-the-office/comment-page-1/#comment-28</link>
		<dc:creator>Bob Paver</dc:creator>
		<pubDate>Fri, 14 Mar 2008 16:44:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.thestylesheet.com/featured-articles/2008/03/you%e2%80%99ve-got-etiquette-email-ethics-at-the-office/#comment-28</guid>
		<description>+ Never use sarcasm unless you are a professional comic/writer.

+ Chop off all of the previous replies, especially if the message has been replied to many time.

+ Be very careful when using e-mail to communicate about difficult situations. E-mail is easily misinterpreted.</description>
		<content:encoded><![CDATA[<p>+ Never use sarcasm unless you are a professional comic/writer.</p>
<p>+ Chop off all of the previous replies, especially if the message has been replied to many time.</p>
<p>+ Be very careful when using e-mail to communicate about difficult situations. E-mail is easily misinterpreted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Weynand</title>
		<link>http://www.thestylesheet.com/featured-articles/2008/03/youve-got-etiquette-email-ethics-at-the-office/comment-page-1/#comment-27</link>
		<dc:creator>Nick Weynand</dc:creator>
		<pubDate>Wed, 12 Mar 2008 21:31:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.thestylesheet.com/featured-articles/2008/03/you%e2%80%99ve-got-etiquette-email-ethics-at-the-office/#comment-27</guid>
		<description>Great comment Scott.  A good subject line really helps when trying to retrieve an old message.  Thanks for reading and contributing.

-Nick</description>
		<content:encoded><![CDATA[<p>Great comment Scott.  A good subject line really helps when trying to retrieve an old message.  Thanks for reading and contributing.</p>
<p>-Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Spinola</title>
		<link>http://www.thestylesheet.com/featured-articles/2008/03/youve-got-etiquette-email-ethics-at-the-office/comment-page-1/#comment-26</link>
		<dc:creator>Scott Spinola</dc:creator>
		<pubDate>Wed, 12 Mar 2008 21:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.thestylesheet.com/featured-articles/2008/03/you%e2%80%99ve-got-etiquette-email-ethics-at-the-office/#comment-26</guid>
		<description>And my pet peeve...

Include a descriptive subject!

The subject is the first filter that readers use to determine the importance of the email TO THEM. You waste your reader&#039;s time and impose yourself on them by not giving a clue to the contents of the email in the subject. If your subject is annoyingly generic like &quot;need help&quot; or &quot;question for you&quot; then I have no idea what the content of your email is and I am less likely to read it. You may as well leave the Subject line blank since that would provide the same information.

This problem also plagues discuss boards. There is nothing more useless on a discussion board than the subject &quot;need help&quot;. Well doesn&#039;t everybody?</description>
		<content:encoded><![CDATA[<p>And my pet peeve&#8230;</p>
<p>Include a descriptive subject!</p>
<p>The subject is the first filter that readers use to determine the importance of the email TO THEM. You waste your reader&#8217;s time and impose yourself on them by not giving a clue to the contents of the email in the subject. If your subject is annoyingly generic like &#8220;need help&#8221; or &#8220;question for you&#8221; then I have no idea what the content of your email is and I am less likely to read it. You may as well leave the Subject line blank since that would provide the same information.</p>
<p>This problem also plagues discuss boards. There is nothing more useless on a discussion board than the subject &#8220;need help&#8221;. Well doesn&#8217;t everybody?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

