<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	>
<channel>
	<title>Comments on: Terrible Corporate Apologies Product Managers Can Learn From</title>
	<atom:link href="http://christophercummings.com/2009/10/29/terrible-corporate-apologies-product-managers-can-learn-from/feed/" rel="self" type="application/rss+xml" />
	<link>http://christophercummings.com/2009/10/29/terrible-corporate-apologies-product-managers-can-learn-from/</link>
	<description>ChristopherCummings.com - Product Management Blog</description>
	<lastBuildDate>Fri, 10 Sep 2010 17:13:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Great Apologies Product Managers Can Learn From. (Plus, One Of My Own.) &#124; Product Management Meets Pop Culture</title>
		<link>http://christophercummings.com/2009/10/29/terrible-corporate-apologies-product-managers-can-learn-from/comment-page-1/#comment-680</link>
		<dc:creator>Great Apologies Product Managers Can Learn From. (Plus, One Of My Own.) &#124; Product Management Meets Pop Culture</dc:creator>
		<pubDate>Mon, 02 Nov 2009 11:12:21 +0000</pubDate>
		<guid isPermaLink="false">http://christophercummings.com/blog/2009/10/29/terrible-corporate-apologies-product-managers-should-avoid/#comment-680</guid>
		<description>[...] time we looked at three truly terrible ways businesses have apologized to [...]</description>
		<content:encoded><![CDATA[<p>[...] time we looked at three truly terrible ways businesses have apologized to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saeed Khan</title>
		<link>http://christophercummings.com/2009/10/29/terrible-corporate-apologies-product-managers-can-learn-from/comment-page-1/#comment-681</link>
		<dc:creator>Saeed Khan</dc:creator>
		<pubDate>Sat, 31 Oct 2009 18:30:58 +0000</pubDate>
		<guid isPermaLink="false">http://christophercummings.com/blog/2009/10/29/terrible-corporate-apologies-product-managers-should-avoid/#comment-681</guid>
		<description>One of the issues with corporate apologies is legal liability. A lot of companies don&#039;t or can&#039;t explicitly say sorry for something because of the potential law suits that can arise because the apology could also be seen by courts (and litigious citizens) as admission of liability.

I doubt the Pepsi example could have resulted in any legal liabilities, but who knows.  There have been successful lawsuits for much less.</description>
		<content:encoded><![CDATA[<p>One of the issues with corporate apologies is legal liability. A lot of companies don&#8217;t or can&#8217;t explicitly say sorry for something because of the potential law suits that can arise because the apology could also be seen by courts (and litigious citizens) as admission of liability.</p>
<p>I doubt the Pepsi example could have resulted in any legal liabilities, but who knows.  There have been successful lawsuits for much less.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Cummings</title>
		<link>http://christophercummings.com/2009/10/29/terrible-corporate-apologies-product-managers-can-learn-from/comment-page-1/#comment-686</link>
		<dc:creator>Christopher Cummings</dc:creator>
		<pubDate>Fri, 30 Oct 2009 00:19:51 +0000</pubDate>
		<guid isPermaLink="false">http://christophercummings.com/blog/2009/10/29/terrible-corporate-apologies-product-managers-should-avoid/#comment-686</guid>
		<description>@Patrick - I can concede that point. But it still feels very cheap to me. Given the attention they were getting, wouldn&#039;t their response have been retweeted by folks and appended with the appropriate hashtag anyway? It feels like Pepsi was trying 2 hard 2 be hip, and missing an opportunity to engage in a real dialog in a more appropriate venue.</description>
		<content:encoded><![CDATA[<p>@Patrick &#8211; I can concede that point. But it still feels very cheap to me. Given the attention they were getting, wouldn&#8217;t their response have been retweeted by folks and appended with the appropriate hashtag anyway? It feels like Pepsi was trying 2 hard 2 be hip, and missing an opportunity to engage in a real dialog in a more appropriate venue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry McKeogh</title>
		<link>http://christophercummings.com/2009/10/29/terrible-corporate-apologies-product-managers-can-learn-from/comment-page-1/#comment-685</link>
		<dc:creator>Larry McKeogh</dc:creator>
		<pubDate>Thu, 29 Oct 2009 15:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://christophercummings.com/blog/2009/10/29/terrible-corporate-apologies-product-managers-should-avoid/#comment-685</guid>
		<description>Chris,
Excellent reminder on how to handle an embarrassing situation.  As I was reading I kept thinking back to the 1994 debacle with Intel and the floating point error.  Intel, after some arm twisting acknowledged the floating point issue.  Rather than fess up they proceeded to denigrate their user base by claiming it was not serious and would not affect most users.  To resolve the issue they then required proof before replacement. http://bit.ly/4tHbuK.  Ultimately they did finally &lt;i&gt;get&lt;/i&gt; it but by then they had more problems than a minor processor error.

As I was searching to refresh my memory I came across a couple of other more recent apologies and how not to handle courtesy of Intel.
http://www.ecogeek.org/component/content/article/1900

Hopefully I will never have such a situation, but if i do, I may just seek out Intel cases and do the opposite.

I look forward to your suggestions on how to handle such a tricky situation.</description>
		<content:encoded><![CDATA[<p>Chris,<br />
Excellent reminder on how to handle an embarrassing situation.  As I was reading I kept thinking back to the 1994 debacle with Intel and the floating point error.  Intel, after some arm twisting acknowledged the floating point issue.  Rather than fess up they proceeded to denigrate their user base by claiming it was not serious and would not affect most users.  To resolve the issue they then required proof before replacement. <a href="http://bit.ly/4tHbuK" rel="nofollow">http://bit.ly/4tHbuK</a>.  Ultimately they did finally <i>get</i> it but by then they had more problems than a minor processor error.</p>
<p>As I was searching to refresh my memory I came across a couple of other more recent apologies and how not to handle courtesy of Intel.<br />
<a href="http://www.ecogeek.org/component/content/article/1900" rel="nofollow">http://www.ecogeek.org/component/content/article/1900</a></p>
<p>Hopefully I will never have such a situation, but if i do, I may just seek out Intel cases and do the opposite.</p>
<p>I look forward to your suggestions on how to handle such a tricky situation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://christophercummings.com/2009/10/29/terrible-corporate-apologies-product-managers-can-learn-from/comment-page-1/#comment-684</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Thu, 29 Oct 2009 14:35:45 +0000</pubDate>
		<guid isPermaLink="false">http://christophercummings.com/blog/2009/10/29/terrible-corporate-apologies-product-managers-should-avoid/#comment-684</guid>
		<description>Not to defend Pepsi too much here, but they could have just been using the hashtag as a way to reach the core audience.  If everybody out there complaining about Pepsi is watching that hashtag, then an apology aimed at those people is most effective on the same conversation thread.</description>
		<content:encoded><![CDATA[<p>Not to defend Pepsi too much here, but they could have just been using the hashtag as a way to reach the core audience.  If everybody out there complaining about Pepsi is watching that hashtag, then an apology aimed at those people is most effective on the same conversation thread.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Williams</title>
		<link>http://christophercummings.com/2009/10/29/terrible-corporate-apologies-product-managers-can-learn-from/comment-page-1/#comment-683</link>
		<dc:creator>Chris Williams</dc:creator>
		<pubDate>Thu, 29 Oct 2009 14:15:02 +0000</pubDate>
		<guid isPermaLink="false">http://christophercummings.com/blog/2009/10/29/terrible-corporate-apologies-product-managers-should-avoid/#comment-683</guid>
		<description>Nice post. I remember reading that DreamHost &quot;apology&quot; letter. Good thing they were quick to send my refund, but I left them after I received that email.</description>
		<content:encoded><![CDATA[<p>Nice post. I remember reading that DreamHost &#8220;apology&#8221; letter. Good thing they were quick to send my refund, but I left them after I received that email.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
