<?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: 7 Ideas to Improve Email Communications</title>
	<atom:link href="http://myofficezilla.com/nibbles/04/7-ideas-to-improve-email-communications/feed/" rel="self" type="application/rss+xml" />
	<link>http://myofficezilla.com/nibbles/04/7-ideas-to-improve-email-communications/</link>
	<description>Helping you take a bite out of work!</description>
	<lastBuildDate>Wed, 19 May 2010 13:01:29 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://myofficezilla.com/nibbles/04/7-ideas-to-improve-email-communications/comment-page-1/#comment-28</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 14 Apr 2009 22:14:58 +0000</pubDate>
		<guid isPermaLink="false">http://myofficezilla.com/nibbles/?p=185#comment-28</guid>
		<description>Hi Jim!  My favorite from your list is the responsiveness norm.  It does drive me crazy to not hear back within at least 72 hours from most emails I send - I really love 24 though!  Thanks for your input.</description>
		<content:encoded><![CDATA[<p>Hi Jim!  My favorite from your list is the responsiveness norm.  It does drive me crazy to not hear back within at least 72 hours from most emails I send &#8211; I really love 24 though!  Thanks for your input.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: goodspkr</title>
		<link>http://myofficezilla.com/nibbles/04/7-ideas-to-improve-email-communications/comment-page-1/#comment-27</link>
		<dc:creator>goodspkr</dc:creator>
		<pubDate>Tue, 14 Apr 2009 19:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://myofficezilla.com/nibbles/?p=185#comment-27</guid>
		<description>Pretty good list.  Definitely agree with what you have.

We are a training company specializing in virtual communications.  We tell everyone they should have a communication plan that includes things like you have here.

What the team comes up with is their own business, but we do offer them a sample of communication norms for email.

Here&#039;s what we include in that sample that you don&#039;t have here.

1.  Create a responsiveness norm for the team.  We suggest one day unless the document asks for a later date.  If you don&#039;t have this it is really easy to break trust.

2.  If action is requested or required, list the individual under &quot;to.&quot;  If no action is required, that individual should be listed on &quot;cc.&quot;

3.  Action requests should come in the first paragraph (a lot of people read only this far and miss that you need them to do something).

4. We agree with you on your first point about space.  The way we say it is, &quot;Emails will be no longer than one page.  If you can&#039;t say what you need to say in that space, you haven&#039;t thought about it enough.&quot;

5. Cover only one topic per email.

6. Provide easy follow up information.


Jim Kutsko
Bridge the Distance</description>
		<content:encoded><![CDATA[<p>Pretty good list.  Definitely agree with what you have.</p>
<p>We are a training company specializing in virtual communications.  We tell everyone they should have a communication plan that includes things like you have here.</p>
<p>What the team comes up with is their own business, but we do offer them a sample of communication norms for email.</p>
<p>Here&#8217;s what we include in that sample that you don&#8217;t have here.</p>
<p>1.  Create a responsiveness norm for the team.  We suggest one day unless the document asks for a later date.  If you don&#8217;t have this it is really easy to break trust.</p>
<p>2.  If action is requested or required, list the individual under &#8220;to.&#8221;  If no action is required, that individual should be listed on &#8220;cc.&#8221;</p>
<p>3.  Action requests should come in the first paragraph (a lot of people read only this far and miss that you need them to do something).</p>
<p>4. We agree with you on your first point about space.  The way we say it is, &#8220;Emails will be no longer than one page.  If you can&#8217;t say what you need to say in that space, you haven&#8217;t thought about it enough.&#8221;</p>
<p>5. Cover only one topic per email.</p>
<p>6. Provide easy follow up information.</p>
<p>Jim Kutsko<br />
Bridge the Distance</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Mother of All Lists - 603 Lists On Anything You Can Think Of &#124; MyMarketer</title>
		<link>http://myofficezilla.com/nibbles/04/7-ideas-to-improve-email-communications/comment-page-1/#comment-26</link>
		<dc:creator>The Mother of All Lists - 603 Lists On Anything You Can Think Of &#124; MyMarketer</dc:creator>
		<pubDate>Sat, 11 Apr 2009 05:57:51 +0000</pubDate>
		<guid isPermaLink="false">http://myofficezilla.com/nibbles/?p=185#comment-26</guid>
		<description>[...]  7 ideas to improve email communications  [...]</description>
		<content:encoded><![CDATA[<p>[...]  7 ideas to improve email communications  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
