<?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: On the Importance of Failing Well</title>
	<atom:link href="http://www.missingfeatures.com/2007/07/30/on-the-importance-of-failing-well/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.missingfeatures.com/2007/07/30/on-the-importance-of-failing-well/</link>
	<description>Usability, software and user experience design.</description>
	<lastBuildDate>Sat, 13 Mar 2010 13:03:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Missing Features &#187; How not to run a software licensing portal</title>
		<link>http://www.missingfeatures.com/2007/07/30/on-the-importance-of-failing-well/comment-page-1/#comment-261</link>
		<dc:creator>Missing Features &#187; How not to run a software licensing portal</dc:creator>
		<pubDate>Tue, 14 Jul 2009 18:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://missingfeatures.com/2007/07/30/on-the-importance-of-failing-well/#comment-261</guid>
		<description>[...] for and eliminate dead end phone paths. Phone menu systems, like software, need to fail well. In this case, that means routing a person back to a customer service rep (at the top of the queue) [...]</description>
		<content:encoded><![CDATA[<p>[...] for and eliminate dead end phone paths. Phone menu systems, like software, need to fail well. In this case, that means routing a person back to a customer service rep (at the top of the queue) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
