<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Spherical Cows Don&#8217;t Suffer From Email Overload</title>
	<atom:link href="http://email-overloaded.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/feed/" rel="self" type="application/rss+xml" />
	<link>http://email-overloaded.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/</link>
	<description>Itzy Sabo on Email Productivity</description>
	<lastBuildDate>Wed, 07 Jul 2010 12:39:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: T</title>
		<link>http://email-overloaded.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/#comment-12718</link>
		<dc:creator>T</dc:creator>
		<pubDate>Mon, 18 Dec 2006 15:05:13 +0000</pubDate>
		<guid isPermaLink="false">http://itzy.wordpress.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/#comment-12718</guid>
		<description>RSS will never FULLY replace our current email system.

I also agree that more training to handle emails is needed</description>
		<content:encoded><![CDATA[<p>RSS will never FULLY replace our current email system.</p>
<p>I also agree that more training to handle emails is needed</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eBizBlog &#187; Blog Archive &#187; Info Avalanche: Email is Taking Over</title>
		<link>http://email-overloaded.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/#comment-2023</link>
		<dc:creator>eBizBlog &#187; Blog Archive &#187; Info Avalanche: Email is Taking Over</dc:creator>
		<pubDate>Mon, 21 Aug 2006 18:10:58 +0000</pubDate>
		<guid isPermaLink="false">http://itzy.wordpress.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/#comment-2023</guid>
		<description>[...] Email Overloaded, a blog by Itzy Sabo on Email Productivity has a great article on email overload called Spherical Cows Don’t Suffer From Email Overload. It’s well worth the read. [...]</description>
		<content:encoded><![CDATA[<p>[...] Email Overloaded, a blog by Itzy Sabo on Email Productivity has a great article on email overload called Spherical Cows Don’t Suffer From Email Overload. It’s well worth the read. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frederic from eBusiness Marketing Blog</title>
		<link>http://email-overloaded.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/#comment-405</link>
		<dc:creator>Frederic from eBusiness Marketing Blog</dc:creator>
		<pubDate>Thu, 01 Jun 2006 22:22:36 +0000</pubDate>
		<guid isPermaLink="false">http://itzy.wordpress.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/#comment-405</guid>
		<description>We have the same solution as Patrick...

RSS will eventually replace email

Read: Why Blogging is Essential to Your Business

http://ebusinesszoom.com/?p=82</description>
		<content:encoded><![CDATA[<p>We have the same solution as Patrick&#8230;</p>
<p>RSS will eventually replace email</p>
<p>Read: Why Blogging is Essential to Your Business</p>
<p><a href="http://ebusinesszoom.com/?p=82" rel="nofollow">http://ebusinesszoom.com/?p=82</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Cormier</title>
		<link>http://email-overloaded.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/#comment-89</link>
		<dc:creator>Patrick Cormier</dc:creator>
		<pubDate>Sun, 09 Apr 2006 13:12:55 +0000</pubDate>
		<guid isPermaLink="false">http://itzy.wordpress.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/#comment-89</guid>
		<description>Our way forward in solving alleviating the Email Overload problem, in a corporate context, is this: http://tinyurl.com/lfeo2 

In short, we will redirect all mass emails to syndicated, subject-based blogs to which end users have either mandatory or optional subscriptions.</description>
		<content:encoded><![CDATA[<p>Our way forward in solving alleviating the Email Overload problem, in a corporate context, is this: <a href="http://tinyurl.com/lfeo2" rel="nofollow">http://tinyurl.com/lfeo2</a> </p>
<p>In short, we will redirect all mass emails to syndicated, subject-based blogs to which end users have either mandatory or optional subscriptions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Wagstaff</title>
		<link>http://email-overloaded.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/#comment-73</link>
		<dc:creator>David Wagstaff</dc:creator>
		<pubDate>Fri, 31 Mar 2006 23:46:59 +0000</pubDate>
		<guid isPermaLink="false">http://itzy.wordpress.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/#comment-73</guid>
		<description>On a personal note, I complained about email misuse in an open team meeting.  To make sure everyone understood EXACTLY what I was talking about, I gave pointed examples of everyone in the room including myself.  Gentle readers, Miss Manners does NOT recommend this technique.  The result was immediate verbal defensiveness and name calling.  For the next 2 weeks, the team spam--which didn&#039;t abate one iota--contained harassing anotations such as &quot;Dear All--Oh, I&#039;m sorry, does that make this spam? ;-)&quot;  and &quot;Please forward me your suggestions--and don&#039;t forget to include Dave. ha ha&quot;  

The difficulty in email training is avoiding the appearance of calling the email abuser&#039;s baby ugly.  When you say, &quot;Jim, I&#039;d rather you didn&#039;t copy me on X.&quot;, what Jim hears is &quot;Jim, what you do is worthless, and so are you.  Please write me when you are doing something more important.&quot;

Therefore, I suggest these guidelines.
1. Use life-like examples without actually incriminating anyone in the training.
2. Give each email rule a short name such as &quot;CC expects no reply&quot;.  Particularly effective are insider nonsense names that remind everyone of a common story.  &quot;Sorry, no bananas here.&quot;  Even stupid acronyms work well.  &quot;NASGAR&quot;
3. Don&#039;t castigate violators by reminding them why their behavior is unacceptable.  Yes, you do have to be specific, but don&#039;t explain it, or you&#039;re perceived as patronizing, moralizing and insulting.  Simply state the rule, &quot;Jim, I didn&#039;t reply because &#039;Sorry, no bananas here.&#039;&quot;
4. Pick your battles. In a rush, even the most obedient peer will TO instead of CC. Officiously calling attention to every violation will only result in your unofficial--yet oft used title--Spam Nazi. And Holy [Robin explicitive]!  You don&#039;t ever want to make a mistake yourself.  You&#039;ve be hoist on your own petard.
5. Use common scripts and tools across the company.  It&#039;s one way for the tool to guide the users to correct behavior without you being the cop. &quot;Sorry, Jim, I didn&#039;t notice your urgent request at first because you TOed more than one person and my script didn&#039;t flag it as important.&quot;  Jim is more likely to understand if he has the exact same behavior for his email.
6. Have automated reports that flag potential violations.  &quot;Jim, this report shows you sent email to the entire company 13 times last month.&quot;
7. Have short, clearly written policies.  
8. Above all, do the training.  Even if you don&#039;t get it exactly right at first--who does?--it&#039;s better than assuming people will use good sense.  First, they don&#039;t have good sense, or you wouldn&#039;t be reading this.  Second, your kind assumption won&#039;t be appreciated. Third, training won&#039;t make the situation worse.  It&#039;s a small investment with a potentially huge payoff in productivity.</description>
		<content:encoded><![CDATA[<p>On a personal note, I complained about email misuse in an open team meeting.  To make sure everyone understood EXACTLY what I was talking about, I gave pointed examples of everyone in the room including myself.  Gentle readers, Miss Manners does NOT recommend this technique.  The result was immediate verbal defensiveness and name calling.  For the next 2 weeks, the team spam&#8211;which didn&#8217;t abate one iota&#8211;contained harassing anotations such as &#8220;Dear All&#8211;Oh, I&#8217;m sorry, does that make this spam? ;-)&#8221;  and &#8220;Please forward me your suggestions&#8211;and don&#8217;t forget to include Dave. ha ha&#8221;  </p>
<p>The difficulty in email training is avoiding the appearance of calling the email abuser&#8217;s baby ugly.  When you say, &#8220;Jim, I&#8217;d rather you didn&#8217;t copy me on X.&#8221;, what Jim hears is &#8220;Jim, what you do is worthless, and so are you.  Please write me when you are doing something more important.&#8221;</p>
<p>Therefore, I suggest these guidelines.<br />
1. Use life-like examples without actually incriminating anyone in the training.<br />
2. Give each email rule a short name such as &#8220;CC expects no reply&#8221;.  Particularly effective are insider nonsense names that remind everyone of a common story.  &#8220;Sorry, no bananas here.&#8221;  Even stupid acronyms work well.  &#8220;NASGAR&#8221;<br />
3. Don&#8217;t castigate violators by reminding them why their behavior is unacceptable.  Yes, you do have to be specific, but don&#8217;t explain it, or you&#8217;re perceived as patronizing, moralizing and insulting.  Simply state the rule, &#8220;Jim, I didn&#8217;t reply because &#8216;Sorry, no bananas here.&#8217;&#8221;<br />
4. Pick your battles. In a rush, even the most obedient peer will TO instead of CC. Officiously calling attention to every violation will only result in your unofficial&#8211;yet oft used title&#8211;Spam Nazi. And Holy [Robin explicitive]!  You don&#8217;t ever want to make a mistake yourself.  You&#8217;ve be hoist on your own petard.<br />
5. Use common scripts and tools across the company.  It&#8217;s one way for the tool to guide the users to correct behavior without you being the cop. &#8220;Sorry, Jim, I didn&#8217;t notice your urgent request at first because you TOed more than one person and my script didn&#8217;t flag it as important.&#8221;  Jim is more likely to understand if he has the exact same behavior for his email.<br />
6. Have automated reports that flag potential violations.  &#8220;Jim, this report shows you sent email to the entire company 13 times last month.&#8221;<br />
7. Have short, clearly written policies.<br />
8. Above all, do the training.  Even if you don&#8217;t get it exactly right at first&#8211;who does?&#8211;it&#8217;s better than assuming people will use good sense.  First, they don&#8217;t have good sense, or you wouldn&#8217;t be reading this.  Second, your kind assumption won&#8217;t be appreciated. Third, training won&#8217;t make the situation worse.  It&#8217;s a small investment with a potentially huge payoff in productivity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Wagstaff</title>
		<link>http://email-overloaded.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/#comment-72</link>
		<dc:creator>David Wagstaff</dc:creator>
		<pubDate>Fri, 31 Mar 2006 22:35:49 +0000</pubDate>
		<guid isPermaLink="false">http://itzy.wordpress.com/2006/02/02/the-cow-and-the-butterfly-conspire-against-email-overload/#comment-72</guid>
		<description>Observing behavior changes the behavior being observed.  So even if someone really and truly gets the magical algorithm that can presort your email (maybe even answer some of it for you), as soon as it&#039;s known we&#039;re going circumvent it to suit our purposes.  As soon as antibiotics were introduced, bacteria started becoming resistant.  As each web search engine, including Google, the reigning king, revealed their sorting algorithm, people used the very same algorithm to artificially boost their page ratings.  Or more to the subject at hand, why don&#039;t spam blockers work?  Well, they did for a moment.  And then the spammers circumvented the spam blockers.

One root cause is that people think what they have to say is important.  (Actually they think they are important, and what they say only reflects it, proves it.)  In short, they like to be heard (or read), and responded to.  

So even after getting rid of the easily detected Viagra spams, you still have to deal with genuine, but misguided, people.  People, who will resist your tools whenever the tool silences or even delays their messages.  And unlike bacteria that take a decade to resist a new drug, people will circumvent the tool in days.

I agree that training and discipline in handling email is needed.  I further agree that the tools used must involvethe users.  Indeed, &quot;help US make better decisions and gently steer US towards a more efficient way of communicating.&quot; [capitalization emphasis added]  To be successful, the tool (or technique or culture...) must convince people that by using it, they will be heard and responded to more.</description>
		<content:encoded><![CDATA[<p>Observing behavior changes the behavior being observed.  So even if someone really and truly gets the magical algorithm that can presort your email (maybe even answer some of it for you), as soon as it&#8217;s known we&#8217;re going circumvent it to suit our purposes.  As soon as antibiotics were introduced, bacteria started becoming resistant.  As each web search engine, including Google, the reigning king, revealed their sorting algorithm, people used the very same algorithm to artificially boost their page ratings.  Or more to the subject at hand, why don&#8217;t spam blockers work?  Well, they did for a moment.  And then the spammers circumvented the spam blockers.</p>
<p>One root cause is that people think what they have to say is important.  (Actually they think they are important, and what they say only reflects it, proves it.)  In short, they like to be heard (or read), and responded to.  </p>
<p>So even after getting rid of the easily detected Viagra spams, you still have to deal with genuine, but misguided, people.  People, who will resist your tools whenever the tool silences or even delays their messages.  And unlike bacteria that take a decade to resist a new drug, people will circumvent the tool in days.</p>
<p>I agree that training and discipline in handling email is needed.  I further agree that the tools used must involvethe users.  Indeed, &#8220;help US make better decisions and gently steer US towards a more efficient way of communicating.&#8221; [capitalization emphasis added]  To be successful, the tool (or technique or culture&#8230;) must convince people that by using it, they will be heard and responded to more.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
