<?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: The Most Disastrous E-Mail Mistakes, and How to Avoid Them</title>
	<atom:link href="http://ririanproject.com/2007/10/21/the-most-disastrous-e-mail-mistakes-and-how-to-avoid-them/feed/" rel="self" type="application/rss+xml" />
	<link>http://ririanproject.com/2007/10/21/the-most-disastrous-e-mail-mistakes-and-how-to-avoid-them/</link>
	<description>A personal development blog!</description>
	<lastBuildDate>Fri, 10 Feb 2012 18:21:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Business and finance news blog &#187; The Most Disastrous E-Mail Mistakes and How to Avoid Them</title>
		<link>http://ririanproject.com/2007/10/21/the-most-disastrous-e-mail-mistakes-and-how-to-avoid-them/comment-page-1/#comment-38123</link>
		<dc:creator>Business and finance news blog &#187; The Most Disastrous E-Mail Mistakes and How to Avoid Them</dc:creator>
		<pubDate>Sat, 05 Jan 2008 23:15:35 +0000</pubDate>
		<guid isPermaLink="false">http://ririanproject.com/2007/10/21/the-most-disastrous-e-mail-mistakes-and-how-to-avoid-them/#comment-38123</guid>
		<description>[...] In our modern age of communication, it’s not just what you say that can get you into trouble, but also what you write. As an e-professional in today’s e-blissful world, the more you know now about e-mail habits, the less likely you will be to make an e-blunder down the road.read more &#124; digg story [...]</description>
		<content:encoded><![CDATA[<p>[...] In our modern age of communication, it’s not just what you say that can get you into trouble, but also what you write. As an e-professional in today’s e-blissful world, the more you know now about e-mail habits, the less likely you will be to make an e-blunder down the road.read more | digg story [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The.Hanyee</title>
		<link>http://ririanproject.com/2007/10/21/the-most-disastrous-e-mail-mistakes-and-how-to-avoid-them/comment-page-1/#comment-26711</link>
		<dc:creator>The.Hanyee</dc:creator>
		<pubDate>Mon, 22 Oct 2007 07:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://ririanproject.com/2007/10/21/the-most-disastrous-e-mail-mistakes-and-how-to-avoid-them/#comment-26711</guid>
		<description>One more: Taking too long to respond to email or even worse, not responding at all. Granted, not all emails deserve or even demand for a reply.

However, professional courtesy dictates that we respond to emails within a time-frame that is sensibly prompt. Lots of people probably pass off email as not promptly response-worthy (most commonly due to the sender and recipient having valuing the priority of the email differently). Being too busy or having too many emails to respond to is slowly becoming a lame excuse for electronic tardiness.

Fix-It: Set a sensibly short time-frame of the maximum amount of time it will take you to respond to email that you receive that need to be responded to. And stick to it.</description>
		<content:encoded><![CDATA[<p>One more: Taking too long to respond to email or even worse, not responding at all. Granted, not all emails deserve or even demand for a reply.</p>
<p>However, professional courtesy dictates that we respond to emails within a time-frame that is sensibly prompt. Lots of people probably pass off email as not promptly response-worthy (most commonly due to the sender and recipient having valuing the priority of the email differently). Being too busy or having too many emails to respond to is slowly becoming a lame excuse for electronic tardiness.</p>
<p>Fix-It: Set a sensibly short time-frame of the maximum amount of time it will take you to respond to email that you receive that need to be responded to. And stick to it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

