<?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: I Like Companies That Say &#8220;We Suck&#8221;</title>
	<atom:link href="http://jeffnolan.com/wp/2006/05/25/i-like-companies-that-say-we-suck/feed/" rel="self" type="application/rss+xml" />
	<link>http://jeffnolan.com/wp/2006/05/25/i-like-companies-that-say-we-suck/</link>
	<description>Jeff Nolan&#039;s take on investment, innovation, entrepreneurship and the technology industry</description>
	<lastBuildDate>Mon, 06 Feb 2012 06:44:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Andrew Fife</title>
		<link>http://jeffnolan.com/wp/2006/05/25/i-like-companies-that-say-we-suck/comment-page-1/#comment-2317</link>
		<dc:creator>Andrew Fife</dc:creator>
		<pubDate>Fri, 26 May 2006 03:48:07 +0000</pubDate>
		<guid isPermaLink="false">http://jeffnolan.com/wp/2006/05/25/i-like-companies-that-say-we-suck/#comment-2317</guid>
		<description>Jeff, 
there is no question that the action of creating better feeds is the best way for a Yahoo to demonstrate their commitment to improving the 360 product.  However, mentioning that there is a problem lets users know that Yahoo is thinking about the problem and implies that they will take some action.  Most users are fairly tolerable and acknowledging the problem buys Yahoo more time before people shift to an alternative service provider.  I agree 100% that a road map on fixing the problem would be better than the acknowledgement but the acknowledgement is far better than silence.
-Andrew</description>
		<content:encoded><![CDATA[<p>Jeff,<br />
there is no question that the action of creating better feeds is the best way for a Yahoo to demonstrate their commitment to improving the 360 product.  However, mentioning that there is a problem lets users know that Yahoo is thinking about the problem and implies that they will take some action.  Most users are fairly tolerable and acknowledging the problem buys Yahoo more time before people shift to an alternative service provider.  I agree 100% that a road map on fixing the problem would be better than the acknowledgement but the acknowledgement is far better than silence.<br />
-Andrew</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Wood</title>
		<link>http://jeffnolan.com/wp/2006/05/25/i-like-companies-that-say-we-suck/comment-page-1/#comment-2313</link>
		<dc:creator>Jason Wood</dc:creator>
		<pubDate>Thu, 25 May 2006 22:31:04 +0000</pubDate>
		<guid isPermaLink="false">http://jeffnolan.com/wp/2006/05/25/i-like-companies-that-say-we-suck/#comment-2313</guid>
		<description>Jeff, very true...it&#039;s like when Typepad was having it&#039;s outages. I didn&#039;t really care that management was posting how sorry they were on the Six Apart blog, as a customer I wanted assurances that the problem was being fixed and wouldn&#039;t recur down the road.

And on the flip side, a company like Salesforce.com, which has received plenty of bad press for its outages, at least did something proactive by putting up a monitoring system for anyone to view on the web, with basic drill down capabilities to explain the situation rather than a panderings &quot;oops, my bad.&quot;</description>
		<content:encoded><![CDATA[<p>Jeff, very true&#8230;it&#8217;s like when Typepad was having it&#8217;s outages. I didn&#8217;t really care that management was posting how sorry they were on the Six Apart blog, as a customer I wanted assurances that the problem was being fixed and wouldn&#8217;t recur down the road.</p>
<p>And on the flip side, a company like Salesforce.com, which has received plenty of bad press for its outages, at least did something proactive by putting up a monitoring system for anyone to view on the web, with basic drill down capabilities to explain the situation rather than a panderings &#8220;oops, my bad.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

