<?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>The Hammock &#187; Uncategorized</title>
	<atom:link href="http://juanpatten.com/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://juanpatten.com</link>
	<description>Hey. I&#039;m J.R. and this is...</description>
	<lastBuildDate>Sat, 10 Jul 2010 15:09:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>On Surprising Users</title>
		<link>http://juanpatten.com/2009/on-surprising-users/</link>
		<comments>http://juanpatten.com/2009/on-surprising-users/#comments</comments>
		<pubDate>Tue, 11 Aug 2009 15:44:13 +0000</pubDate>
		<dc:creator>JR Patten</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://juanpatten.com/?p=166</guid>
		<description><![CDATA[The Principle of Least Surprise is a common axiom in user interface design, and any sort of interface design (be it an object, a screen, or an API), and it&#8217;s a useful one. I (and everyone else) enjoy using an &#8230; <a href="http://juanpatten.com/2009/on-surprising-users/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><img class="float-r alignright size-full wp-image-167" title="Surprised Guy" src="http://juanpatten.com/wp-content/uploads/2009/08/dude.png" alt="Surprised Guy" width="195" height="244" />The <a href="http://en.wikipedia.org/wiki/Principle_of_least_astonishment">Principle of Least Surprise</a> is a common axiom in user interface design, and any sort of interface design (be it an object, a screen, or an API), and it&#8217;s a useful one. I (and everyone else) enjoy using an interface that just behaves exactly like I expect. It makes me comfortable, and gives me confidence that the product is well-engineered. It makes using a product *<em>gasp</em>* enjoyable.</p>
<p>But there&#8217;s another side to the double-edged surprise sword: <strong>delight</strong>.</p>
<p>Delight is when you surprise a user by transforming something they take for granted (something they normally wouldn&#8217;t give a second thought, if a first) and transforming it into something that directly and noticeably makes their experience better. Delight comes from making the user take that second glance and thinking, &#8220;Wow. They thought of everything.&#8221;</p>
<p>Delight makes people tell other people about your product.<br />
Delight makes people <em>want</em> to use your product again and again.<br />
Delight makes your product stand out from your competitors.<br />
Delight makes ordinary extraordinary.</p>
<p>Delight people.</p>
<p><em>Have thoughts? Leave a comment.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://juanpatten.com/2009/on-surprising-users/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
