<?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: How To Apologize for Server Outages</title>
	<atom:link href="http://www.mailchimp.com/blog/how-to-apologize-for-server-outages/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mailchimp.com/blog/how-to-apologize-for-server-outages/</link>
	<description>MailChimp, email marketing, and monkeys!</description>
	<lastBuildDate>Fri, 20 Nov 2009 22:25:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Terrible Corporate Apologies Product Managers Should Avoid &#124; Product Management Meets Pop Culture</title>
		<link>http://www.mailchimp.com/blog/how-to-apologize-for-server-outages/comment-page-1/#comment-5827</link>
		<dc:creator>Terrible Corporate Apologies Product Managers Should Avoid &#124; Product Management Meets Pop Culture</dc:creator>
		<pubDate>Thu, 29 Oct 2009 14:06:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/how-to-apologize-for-server-outages/#comment-5827</guid>
		<description>[...] Ben at MailChimp points out, server problems are embarrassing, interruptive, and happen to everybody. The question is, how to [...]</description>
		<content:encoded><![CDATA[<p>[...] Ben at MailChimp points out, server problems are embarrassing, interruptive, and happen to everybody. The question is, how to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Server Status - Slow Delivery Today &#124; MailChimp Blog</title>
		<link>http://www.mailchimp.com/blog/how-to-apologize-for-server-outages/comment-page-1/#comment-2971</link>
		<dc:creator>Server Status - Slow Delivery Today &#124; MailChimp Blog</dc:creator>
		<pubDate>Tue, 17 Feb 2009 00:59:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/how-to-apologize-for-server-outages/#comment-2971</guid>
		<description>[...] companies that have handled it well, like this example from Intuit. I&#8217;ve written about &#8220;How to apologize for server outages&#8221; in the past.  Here&#8217;s a nice interview from the founder of Magnolia talking about [...]</description>
		<content:encoded><![CDATA[<p>[...] companies that have handled it well, like this example from Intuit. I&#8217;ve written about &#8220;How to apologize for server outages&#8221; in the past.  Here&#8217;s a nice interview from the founder of Magnolia talking about [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Scott</title>
		<link>http://www.mailchimp.com/blog/how-to-apologize-for-server-outages/comment-page-1/#comment-1865</link>
		<dc:creator>Rob Scott</dc:creator>
		<pubDate>Thu, 30 Oct 2008 23:02:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/how-to-apologize-for-server-outages/#comment-1865</guid>
		<description>There&#039;s something to be learned from every outage! Good to see it isn&#039;t just me doing 48 hour head scratching sessions. Great post. Rob.</description>
		<content:encoded><![CDATA[<p>There&#8217;s something to be learned from every outage! Good to see it isn&#8217;t just me doing 48 hour head scratching sessions. Great post. Rob.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 7 Basic Email Templates Every Business Needs &#124; MailChimp Blog</title>
		<link>http://www.mailchimp.com/blog/how-to-apologize-for-server-outages/comment-page-1/#comment-232</link>
		<dc:creator>7 Basic Email Templates Every Business Needs &#124; MailChimp Blog</dc:creator>
		<pubDate>Wed, 30 Jan 2008 18:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/how-to-apologize-for-server-outages/#comment-232</guid>
		<description>[...] changes, shipping problems, billing errors, or &#8220;system is temporarily down&#8221; alerts. But read this before you send any public apologies with [...]</description>
		<content:encoded><![CDATA[<p>[...] changes, shipping problems, billing errors, or &#8220;system is temporarily down&#8221; alerts. But read this before you send any public apologies with [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
