<?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: The Well-Structured Email</title>
	<atom:link href="http://blog.greenonions.com/2010/04/21/the-well-structured-email/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.greenonions.com/2010/04/21/the-well-structured-email/</link>
	<description>This is not a cooking blog</description>
	<lastBuildDate>Thu, 18 Aug 2011 20:04:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Jamie Bresner</title>
		<link>http://blog.greenonions.com/2010/04/21/the-well-structured-email/#comment-73</link>
		<dc:creator><![CDATA[Jamie Bresner]]></dc:creator>
		<pubDate>Sun, 25 Apr 2010 03:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.greenonions.com/?p=153#comment-73</guid>
		<description><![CDATA[At my previous job, we had a lot of projects and a lot of clients. To help deal with the flood of emails sent around daily, our email Subject lines were used to convey as much info as possible.

In most cases, the Subject would contain the client code (usually a 3-letter abbreviation), then a project code (each code&#039;s first two digits corresponded with the year of the project), then finally what the message was about, which normally was conveyed with as few words as possible.

The client/project code made it very easy to find past emails without anyone having to file/organize emails in folders.

With the volume of emails I receive at my current job, I&#039;m surprised nobody tries to implement a similar system.]]></description>
		<content:encoded><![CDATA[<p>At my previous job, we had a lot of projects and a lot of clients. To help deal with the flood of emails sent around daily, our email Subject lines were used to convey as much info as possible.</p>
<p>In most cases, the Subject would contain the client code (usually a 3-letter abbreviation), then a project code (each code&#8217;s first two digits corresponded with the year of the project), then finally what the message was about, which normally was conveyed with as few words as possible.</p>
<p>The client/project code made it very easy to find past emails without anyone having to file/organize emails in folders.</p>
<p>With the volume of emails I receive at my current job, I&#8217;m surprised nobody tries to implement a similar system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Osborne</title>
		<link>http://blog.greenonions.com/2010/04/21/the-well-structured-email/#comment-72</link>
		<dc:creator><![CDATA[Tom Osborne]]></dc:creator>
		<pubDate>Thu, 22 Apr 2010 02:27:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.greenonions.com/?p=153#comment-72</guid>
		<description><![CDATA[Thanks for sharing your thought process here – lots to take away. I&#039;m curious. Do you follow a similar format for site mail like Basecamp messages?]]></description>
		<content:encoded><![CDATA[<p>Thanks for sharing your thought process here – lots to take away. I&#8217;m curious. Do you follow a similar format for site mail like Basecamp messages?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan</title>
		<link>http://blog.greenonions.com/2010/04/21/the-well-structured-email/#comment-71</link>
		<dc:creator><![CDATA[Nathan]]></dc:creator>
		<pubDate>Wed, 21 Apr 2010 22:20:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.greenonions.com/?p=153#comment-71</guid>
		<description><![CDATA[I don&#039;t like the colors. The language according to some arbitrary color palette is too hard to discern. Bold is enough.]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t like the colors. The language according to some arbitrary color palette is too hard to discern. Bold is enough.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hobbie</title>
		<link>http://blog.greenonions.com/2010/04/21/the-well-structured-email/#comment-70</link>
		<dc:creator><![CDATA[David Hobbie]]></dc:creator>
		<pubDate>Wed, 21 Apr 2010 17:13:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.greenonions.com/?p=153#comment-70</guid>
		<description><![CDATA[I agree with John&#039;s comment re: bolding and color.  I work for a large law firm, where much of the email ends up being read and replied on mobile devices (mostly Blackberries).  Your well-structured emails ought to read well on a blackberry or iPhone as text is broken down into smaller chunks with context and one-line section headers.

How do you enumerate the attachments?]]></description>
		<content:encoded><![CDATA[<p>I agree with John&#8217;s comment re: bolding and color.  I work for a large law firm, where much of the email ends up being read and replied on mobile devices (mostly Blackberries).  Your well-structured emails ought to read well on a blackberry or iPhone as text is broken down into smaller chunks with context and one-line section headers.</p>
<p>How do you enumerate the attachments?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan</title>
		<link>http://blog.greenonions.com/2010/04/21/the-well-structured-email/#comment-69</link>
		<dc:creator><![CDATA[Ivan]]></dc:creator>
		<pubDate>Wed, 21 Apr 2010 15:59:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.greenonions.com/?p=153#comment-69</guid>
		<description><![CDATA[I like these recommendations.  Longer email threads get too complicated, with each email requiring an understanding of the previous message&#039;s context.  I have to agree with John though, I think bold keywords and excessive use of colour makes email harder to read.  

Bottom line is that by clearly stating action items and issues I think you can save people time and avoid miscommunication.  If people followed most of the items on your list and avoided using Reply All, the world would be a better place.  

Thanks for sharing.]]></description>
		<content:encoded><![CDATA[<p>I like these recommendations.  Longer email threads get too complicated, with each email requiring an understanding of the previous message&#8217;s context.  I have to agree with John though, I think bold keywords and excessive use of colour makes email harder to read.  </p>
<p>Bottom line is that by clearly stating action items and issues I think you can save people time and avoid miscommunication.  If people followed most of the items on your list and avoided using Reply All, the world would be a better place.  </p>
<p>Thanks for sharing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://blog.greenonions.com/2010/04/21/the-well-structured-email/#comment-68</link>
		<dc:creator><![CDATA[John]]></dc:creator>
		<pubDate>Wed, 21 Apr 2010 13:43:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.greenonions.com/?p=153#comment-68</guid>
		<description><![CDATA[First thing: fresh approaches to email are sorely needed. Despite its brokenness it&#039;s not going away, and we need these types of discussions. I do have a couple of misgivings though particular to some of your proposals. How does bolding text or using colors rhyme with keeping things plain text? For me, in business communications especially, plain text is important as it ensures consistency, especially when communicating with those outside your company/profession. I also quote extensively in my emails, so things are kept as contextual as possible. But of course, this is only really successful if the recipients continue to observe such protocols.]]></description>
		<content:encoded><![CDATA[<p>First thing: fresh approaches to email are sorely needed. Despite its brokenness it&#8217;s not going away, and we need these types of discussions. I do have a couple of misgivings though particular to some of your proposals. How does bolding text or using colors rhyme with keeping things plain text? For me, in business communications especially, plain text is important as it ensures consistency, especially when communicating with those outside your company/profession. I also quote extensively in my emails, so things are kept as contextual as possible. But of course, this is only really successful if the recipients continue to observe such protocols.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

