<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>UsabilityBlog &#187; Content</title>
	<atom:link href="http://www.usabilityblog.com/category/content/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.usabilityblog.com</link>
	<description>Blogging about usability, user experience and design</description>
	<lastBuildDate>Wed, 08 Feb 2012 13:40:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Krappy Kayak Error Message</title>
		<link>http://www.usabilityblog.com/2010/09/krappy-kayak-error-message/</link>
		<comments>http://www.usabilityblog.com/2010/09/krappy-kayak-error-message/#comments</comments>
		<pubDate>Wed, 08 Sep 2010 15:05:56 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Content]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2010/09/krappy-kayak-error-message/</guid>
		<description><![CDATA[[Click to view full-sized] Interaction design is all too often simply surface treatment, mere smoke and mirrors. The Kayak site, if you haven&#8217;t had the good fortune to use it, is awesome. It works intuitively, powerfully, efficiently. I love me that Kayak.com. But last week, just when I&#8217;m all ready to make a purchase and [...]]]></description>
			<content:encoded><![CDATA[<p></p><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.usabilityblog.com%2F2010%2F09%2Fkrappy-kayak-error-message%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2010%2F09%2Fkrappy-kayak-error-message%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="float: right; margin-left: 10px; margin-bottom: 10px; text-align: center;"><a title="photo sharing" href="http://www.flickr.com/photos/paulsherman/4944889367/"><img style="border: solid 2px #000000;" src="http://farm5.static.flickr.com/4090/4944889367_9a65962e15_m.jpg" alt="" /></a><br />
<span style="font-size: 0.9em; margin-top: 0px;">[<a href="http://www.flickr.com/photos/paulsherman/4944889367/">Click to view full-sized</a>]<br />
</span></div>
<p>Interaction design is all too often simply surface treatment, mere smoke and mirrors. The Kayak site, if you haven&#8217;t had the good fortune to use it, is awesome. It works intuitively, powerfully, efficiently. I love me that Kayak.com.</p>
<p>But last week, just when I&#8217;m all ready to make a purchase and presumably earn Kayak a little commission scratch, I get this. And a great experience turns to poo.</p>
<p>Don&#8217;t get me wrong, Kayak is and will be my go-to flight comparator for the foreseeable future. But when you compare this to the other &#8220;oops&#8221; messages I&#8217;ve been posting lately (see <a href="http://www.usabilityblog.com/2010/08/good-flickr-error-message/">here</a>, <a href="http://www.usabilityblog.com/2010/03/good-error-page-from-slideshare/">here</a>, and <a href="http://www.usabilityblog.com/2010/03/whimsy-in-the-ui-some-examples/">here</a>), it just doesn&#8217;t stack up.</p>
<p>Thought for the day, peeps: one differentiator between an adequate experience and a great experience is that a great UX turns even the &#8220;oops&#8221; moments into an opportunity for increasing users&#8217; attachment to your offering.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2010/09/krappy-kayak-error-message/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Increasing Trust Via The UI</title>
		<link>http://www.usabilityblog.com/2010/03/increasing-trust-via-the-ui/</link>
		<comments>http://www.usabilityblog.com/2010/03/increasing-trust-via-the-ui/#comments</comments>
		<pubDate>Sun, 14 Mar 2010 15:34:36 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Content]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[trust]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=673</guid>
		<description><![CDATA[This my friends is how you increase trust and confidence through your UI. In this case, it&#8217;s Travelocity that has done this, with the simple addition of some content about disclosing information before the user makes an irrevocable change. Good on Travelocity for this one.]]></description>
			<content:encoded><![CDATA[<p></p><div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.usabilityblog.com%2F2010%2F03%2Fincreasing-trust-via-the-ui%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2010%2F03%2Fincreasing-trust-via-the-ui%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>This my friends is how you increase trust and confidence through your UI. </p>
<p>In this case, it&#8217;s <a href="http://www.travelocity.com/">Travelocity</a> that has done this, with the simple addition of some content about disclosing information before the user makes an irrevocable change.</p>
<p>Good on Travelocity for this one.</p>
<p><center><a href="http://www.flickr.com/photos/paulsherman/4424606917/" title="TravelocityTrust by pjsherman, on Flickr"><img src="http://farm5.static.flickr.com/4016/4424606917_a129b8b196_o.png" width="317" height="154" alt="TravelocityTrust" /></a></center></p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2010/03/increasing-trust-via-the-ui/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>

