<?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/"
	>

<channel>
	<title>Art of the Product</title>
	<atom:link href="http://artoftheproduct.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://artoftheproduct.com</link>
	<description>The Art of the Product</description>
	<pubDate>Thu, 08 Jan 2009 21:10:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Fix This: Use the Most Natural Sort</title>
		<link>http://artoftheproduct.com/2009/01/08/fix-this-use-the-most-natural-sort/</link>
		<comments>http://artoftheproduct.com/2009/01/08/fix-this-use-the-most-natural-sort/#comments</comments>
		<pubDate>Thu, 08 Jan 2009 21:05:39 +0000</pubDate>
		<dc:creator>sean</dc:creator>
		
		<category><![CDATA[Fix This]]></category>

		<category><![CDATA[Sketch]]></category>

		<guid isPermaLink="false">http://artoftheproduct.com/?p=203</guid>
		<description><![CDATA[Google Reader breaks a cardinal rule of presenting lists. Manual sorting is great, but by default use (or at least support) the most natural dynamic sorting of the information.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m a big Google Reader fan. It&#8217;s a great application. I can move from desktop to laptop to iPhone to my wife&#8217;s computer and everywhere there is a browser, there is Google Reader, waiting for me with all my sweet, sweet blog feeds, up to date with what I&#8217;ve read and haven&#8217;t read. It&#8217;s got a decent interface (not great, but good enough) and good keyboard support.</p>
<p>So what&#8217;s wrong? Take a look:</p>
<p><img class="aligncenter" title="Google Reader" src="http://artoftheproduct.com/images/Google_Reader.jpg" alt="" width="127" height="466" /></p>
<p>The list is ordered by when I added the subscription. I can manually change the order, but there is no sorting. Google Reader breaks a cardinal rule of presenting lists. Manual sorting is great, but <strong>by default use (or at least support) the most natural dynamic sorting of the information</strong>. In the case of Google Reader, I need to see those feeds sorted by unread messages. It&#8217;s too bad such a great product has such a lousy problem.</p>
<p>(On the off chance that I just missed Google Reader&#8217;s sorting option, please let me know!)</p>
]]></content:encoded>
			<wfw:commentRss>http://artoftheproduct.com/2009/01/08/fix-this-use-the-most-natural-sort/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Stroke of Genius: Make Use of Your Medium</title>
		<link>http://artoftheproduct.com/2009/01/07/stroke-of-genius-make-use-of-your-medium/</link>
		<comments>http://artoftheproduct.com/2009/01/07/stroke-of-genius-make-use-of-your-medium/#comments</comments>
		<pubDate>Wed, 07 Jan 2009 11:53:47 +0000</pubDate>
		<dc:creator>jake</dc:creator>
		
		<category><![CDATA[Sketch]]></category>

		<category><![CDATA[Stroke of Genius]]></category>

		<guid isPermaLink="false">http://artoftheproduct.com/?p=195</guid>
		<description><![CDATA[As you play it, the map pans and zooms to follow the action, it shows troop movements and major offensives, and it redraws the front line with each major battle.  Why does all this come across so well?  Because the creators of this tool made good trade-offs given that their medium was the web.]]></description>
			<content:encoded><![CDATA[<p>Stroke of Genius: Make Use of Your Medium</p>
<p>The <a id="hpk9" title="BBC History site" href="http://www.bbc.co.uk/history/">BBC History site</a> is an excellent place to learn about WWI and WWII.  Among the many great resources are a set of animated maps covering things like the <a id="bxp4" title="fall of France during WWII" href="http://www.bbc.co.uk/history/worldwars/wwtwo/launch_ani_fall_france_campaign.shtml">fall of France during WWII</a>, the <a id="jybk" title="landings on D-Day" href="http://www.bbc.co.uk/history/worldwars/wwtwo/launch_ani_d_day.shtml">landings on D-Day</a>,and the <a id="g-d3" title="Western Front from 1914-1918" href="http://www.bbc.co.uk/history/worldwars/wwone/launch_ani_western_front.shtml">Western Front from 1914-1918</a> (screenshot below).</p>
<div id="bk0i" style="padding: 1em 0pt; text-align: left;"><a href="http://www.bbc.co.uk/history/worldwars/wwone/launch_ani_western_front.shtml"><img src="http://docs.google.com/a/artoftheproduct.com/File?id=drdjjrb_15dtxbbqgg_b" alt="" width="475" height="389" /></a></div>
<p>A static screenshot doesn&#8217;t do this tool justice.  As you play it, the map pans and zooms to follow the action, it shows troop movements and major offensives, and it redraws the front line with each major battle.  Why does all this come across so well?  Because the creators of this tool made good trade-offs given that their medium was the web.</p>
<p>Here&#8217;s a quick comparison of 3 different mediums:</p>
<div>
<table id="a.me" class="zeroBorder" style="height: 114px;" border="0" cellspacing="0" cellpadding="3" width="565">
<tbody>
<tr>
<td width="10%"></td>
<td width="10%"><strong> Resolution<br />
</strong></td>
<td width="10%"><strong> Portability<br />
</strong></td>
<td width="10%"><strong> Dynamism<br />
</strong></td>
<td width="10%"><strong> Interactivity<br />
</strong></td>
<td width="20%"><strong> User context<br />
</strong></td>
</tr>
<tr>
<td width="10%"><strong> Books<br />
</strong></td>
<td width="10%">High</td>
<td width="10%">High</td>
<td width="10%">Low</td>
<td width="10%">Low</td>
<td width="20%">Tell me a story</td>
</tr>
<tr>
<td width="10%"><strong> Television<br />
</strong></td>
<td width="10%">Low</td>
<td width="10%">Low</td>
<td width="10%">High</td>
<td width="10%">Low</td>
<td width="20%">Entertain me</td>
</tr>
<tr>
<td width="10%"><strong> Web sites<br />
</strong></td>
<td width="10%">Medium</td>
<td width="10%">Medium</td>
<td width="10%">High</td>
<td width="10%">High</td>
<td width="20%">Let me find exactly what I want</td>
</tr>
</tbody>
</table>
</div>
<p>So if the author were trying to find the right map for a book, they might choose a static but high-resolution, highly detailed one like this <a id="unf0" title="WWI map" href="http://history.sandiego.edu/GEN/maps/1900s/1918AEF3200.jpg">WWI map</a> (3.4 MB).  For television, they might choose to animate the map and include voice-overs that tell one specific story-line, but would avoid text as much as possible.</p>
<p>Since in our case, the medium is the web, the author chose a fairly low-resolution map, animated it, including <strong>pans and zooms</strong> to get more detail when needed (<strong>overcoming some of the resolution limitations of the web</strong>), included text (<strong>because web surfers typically prefer to read rather than listen</strong>), and made it interactive (to <strong>allow users to follow along at their own pace</strong>, taking advantage of one of the key benefits of web content).  Had the author put up a large static map, or an animated, non-interactive movie, it wouldn&#8217;t have been nearly as effective.</p>
<p>If anything, the map should be more interactive, allowing the user to pan and zoom himself and click on the timeline as an alternate way to jump around the animation.  And, even though users&#8217; screens are typically low resolution, if this map scaled with the user&#8217;s window, it would allow the lucky folks who have high-resolution monitors to take full advantage of their real estate.</p>
<p>If you think about your medium, you have the chance to turn something good into something great.</p>
]]></content:encoded>
			<wfw:commentRss>http://artoftheproduct.com/2009/01/07/stroke-of-genius-make-use-of-your-medium/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Art of the Link: Increase Sales</title>
		<link>http://artoftheproduct.com/2009/01/03/increase-sales/</link>
		<comments>http://artoftheproduct.com/2009/01/03/increase-sales/#comments</comments>
		<pubDate>Sat, 03 Jan 2009 15:54:48 +0000</pubDate>
		<dc:creator>sean</dc:creator>
		
		<category><![CDATA[Art of the Link]]></category>

		<guid isPermaLink="false">http://artoftheproduct.com/?p=191</guid>
		<description><![CDATA[Even if 99 of these 100 ideas are not right for your product, that means one of them is and you have an immediate action you can take to boost sales in 2009.]]></description>
			<content:encoded><![CDATA[<p><a href="http://successfulsoftware.net/about/">Andy Brice</a> of the <a href="http://successfulsoftware.net/">Successful Software blog</a> has written a list of <a href="http://successfulsoftware.net/2008/12/29/100-ways-to-increase-your-software-sales/">100 ways to increase software sales in 2009</a>. They come in 5 categories: website traffic, trial conversion rate, sales conversion rate, value per sale, and alternative sales channels. Not everyone idea is a priceless gem, but a surprising number of them are. Some of which might be just right for your product and others may lead you to think of similar ideas that would work well.</p>
<p>Things I plan to try from the list are <a href="http://www.trialpay.com/">TrialPay</a> and promoting software on one day sale sites, such as <a href="http://bitsdujour.com/" target="_self">BitsDuJour</a> or <a href="http://www.giveawayoftheday.com/">GiveAwayOfTheDay</a>.</p>
<p>Some of the 100 ideas are specific to downloadable software, and some of them are specific to micro-ISVs. Even if 99 of these 100 ideas are not right for your product, that means one of them is and you have an immediate action you can take to boost sales in 2009. Go check out the <a href="http://successfulsoftware.net/2008/12/29/100-ways-to-increase-your-software-sales/">list</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://artoftheproduct.com/2009/01/03/increase-sales/feed/</wfw:commentRss>
		</item>
		<item>
		<title>(A)bort, (R)etry, (F)ail</title>
		<link>http://artoftheproduct.com/2009/01/02/abort-retry-fail/</link>
		<comments>http://artoftheproduct.com/2009/01/02/abort-retry-fail/#comments</comments>
		<pubDate>Fri, 02 Jan 2009 22:56:41 +0000</pubDate>
		<dc:creator>sean</dc:creator>
		
		<category><![CDATA[Featured Article]]></category>

		<guid isPermaLink="false">http://artoftheproduct.com/?p=181</guid>
		<description><![CDATA[Users are usually pretty understanding of errors if you let them know exactly what happened, why it happened, and what they should do about it.]]></description>
			<content:encoded><![CDATA[<p>Covering every aspect of dealing well with error conditions could take a <a id="gqp1" title="whole book" href="http://www.amazon.com/Defensive-Design-Web-improve-messages/dp/073571410X/ref=pd_bbs_sr_1?ie=UTF8&amp;s=books&amp;qid=1228475487&amp;sr=8-1">whole book</a>. What I want to talk about specifically is the information that you pass on to your user when an error occurs. Here are some rules you should follow for error pages and dialogs:</p>
<ul>
<li> <strong>Never show your users error codes</strong> - ever</li>
<li> <strong style="background-color: #ffffff;">Pass error information to technical support without user involvement </strong>- when acceptable, solve errors proactively. Make it so you can easily correlate the error with the human user that was affected</li>
<li> <strong>Exceptions, stack traces and HTTP error statuses are just another form of error code</strong> - keep them tucked away</li>
<li> <strong>Take care in crafting your error messages</strong> - not too much or too little information, all the relevant information</li>
<li> <strong>Be friendly, humble and apologetic</strong> - you screwed up, not the user</li>
<li> <strong>Make error messages actionable</strong> - empower your user with the next step they should take</li>
<li> <strong>If you absolutely must show an error code, tell the user why and what they need to do with it</strong></li>
</ul>
<p>Provide users with all the relevant information and <span style="background-color: #ffffff;">tell them what action they should be taking </span>next.  Users are usually pretty understanding of errors if you let them know exactly what happened, why it happened, and what they should do about it. The two biggest sources of frustration to a user in the face of an error are, &#8220;I don&#8217;t know what to do now&#8221; or &#8220;<span style="background-color: #ffffff;">I would know what to do now but I don&#8217;t have the information.&#8221;</span><br style="background-color: #ffff00;" /><br />
What I&#8217;d like to do now is play a little Extreme Makeover: Error Page Edition.</p>
<p>The first contestant is my friendly neighborhood bank, <a id="dm.j" title="Wachovia" href="http://wachovia.com/">Wachovia</a>. Nothing like kicking a company while they are <a id="lron" title="down" href="http://www.financialweek.com/apps/pbcs.dll/article?AID=/20081204/REG/812039951/1036">down</a>. Like most banks, Wachovia provides online banking services to their customers, and like most banks, these services are essentially web front ends to a mainframe. The thing about mainframes is they predate our online, real-time, 24/7 world, so many mornings when I get up at 4 AM EST, many of the services Wachovia offers to me online are not available. My morning error page comes with an amusing and ever changing variety of error codes. To Wachovia&#8217;s credit, these services have a good track record for me of being up by 6 or 7 AM and the English in their error message is rather helpful. By applying the rules above it can be better.</p>
<p><img class="aligncenter" src="http://artoftheproduct.com/images/Wachovia_Before.jpg" alt="" width="580" height="201" /></p>
<p>The error page is already friendly and actionable. This is a good first step and is more than we&#8217;ve come to expect from most error pages. It would be better if Wachovia wasn&#8217;t so stingy with information, if they made it clear why they are providing the error code and what should be done with it, and if they recognized that it is an inconvenience (&#8221;this inconvenience&#8221;) versus just a potential inconvenience (&#8221;any inconvenience&#8221;).</p>
<p style="text-align: center;"><img class="aligncenter" title="Wachovia Error Page: Before Makeover" src="http://artoftheproduct.com/images/Wachovia_After_1.jpg" alt="" width="616" height="64" /></p>
<p>The next step for Wachovia would be getting rid of the error code. They presumably provide the error code so the user can pass it along to the customer service representative on the phone (I&#8217;ve been asked by Wachovia for the error code before). But it&#8217;s a bank and I&#8217;m logged in. They know who I am! Their systems should be making that information available to customer service representatives that need it without me needing to relay it to them. Even better, send me an email when the situation is resolved saying, &#8220;We&#8217;re sorry about the error that occurred while you were on our online banking site this morning, the problem has been fixed and you can access the service now.&#8221;</p>
<p style="text-align: center;"><img class="aligncenter" title="Wachovia Error Page: After Makeover" src="http://artoftheproduct.com/images/Wachovia_After_2.jpg" alt="" width="616" height="109" /></p>
<p>Next I&#8217;d like to makeover a company many consider to be the world&#8217;s top super model. <a id="jfn6" title="Apple" href="http://www.apple.com/">Apple</a>. Sacrilege? Not everything coming out of Cupertino smells of roses and gumdrops. Take the <a id="s800" title="Time Machine" href="http://www.apple.com/macosx/features/timemachine.html">Time Machine</a> (Mac OS X&#8217;s backup system) error dialog that unfortunately every Time Machine user has seen too many times. Apple does a good job following many of our rules, there are no error codes for example. Yet this dialog is immensely frustrating because it provides no meaningful information. <span style="background-color: #ffffff;">What are</span> you supposed to do now?</p>
<p style="text-align: center;"><img class="aligncenter" title="Time Machine Error Dialog: Before Makeover" src="http://artoftheproduct.com/images/TimeMachineError.png" alt="" width="418" height="157" /></p>
<p>Making over this dialog is a matter of providing the user with more of the information that Time Machine obviously has, so the user can make an informed decision about what to do next.</p>
<p><img class="aligncenter" title="Time Machine Error Dialog: After Makeover" src="http://artoftheproduct.com/images/TimeMachineErrorAfter.jpg" alt="" width="461" height="241" /></p>
<p>The new dialog could be furthered improved with a link to information on how to fix the permission problem.</p>
<p>No matter how polished and foolproof you think your product is (and most of us think our products are mostly bubblegum and bailing wire), there <strong>will</strong> come a time when a user encounters an error. These are the times that try our product&#8217;s soul. The product&#8217;s response in the face of errors can make a good product great or a great product crumble.</p>
<p style="text-align: right;">Butterfly Error Dialog photo by <a href="http://www.flickr.com/photos/schoschie/">schoschie</a></p>
]]></content:encoded>
			<wfw:commentRss>http://artoftheproduct.com/2009/01/02/abort-retry-fail/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Art of the Link: 10 UI Techniques</title>
		<link>http://artoftheproduct.com/2008/12/19/art-of-the-link-10-ui-techniques/</link>
		<comments>http://artoftheproduct.com/2008/12/19/art-of-the-link-10-ui-techniques/#comments</comments>
		<pubDate>Fri, 19 Dec 2008 12:06:25 +0000</pubDate>
		<dc:creator>sean</dc:creator>
		
		<category><![CDATA[Art of the Link]]></category>

		<category><![CDATA[Sketch]]></category>

		<guid isPermaLink="false">http://artoftheproduct.com/?p=178</guid>
		<description><![CDATA[This article is a must read for anyone involved in creating Web or intranet products and many of the techniques have direct or analogous application for desktop and mobile interfaces.]]></description>
			<content:encoded><![CDATA[<p><em></em>Dmitry Fadeyev wrote a great article for Smashing Magazine called <a href="http://www.smashingmagazine.com/2008/12/15/10-useful-techniques-to-improve-your-user-interface-designs/">10 Useful Techniques To Improve Your User Interface Design</a>. This article is a must read for anyone involved in creating Web or intranet products and many of the techniques have direct or analogous application for desktop and mobile interfaces.</p>
<p>If you don&#8217;t have time for all 10 (shame on you), the 3 most important are #1 Padded block links, #7 - Auto-focus on input, and #10 - Verbs in labels.</p>
]]></content:encoded>
			<wfw:commentRss>http://artoftheproduct.com/2008/12/19/art-of-the-link-10-ui-techniques/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Give Them (Some) Choice</title>
		<link>http://artoftheproduct.com/2008/12/05/give-them-some-choice/</link>
		<comments>http://artoftheproduct.com/2008/12/05/give-them-some-choice/#comments</comments>
		<pubDate>Fri, 05 Dec 2008 11:55:59 +0000</pubDate>
		<dc:creator>jake</dc:creator>
		
		<category><![CDATA[Featured Article]]></category>

		<guid isPermaLink="false">http://artoftheproduct.com/?p=169</guid>
		<description><![CDATA[People have become accustomed to choice. In enterprise and consumer software, choice usually means "what product level or feature set do I want" and it is typically tied to price.]]></description>
			<content:encoded><![CDATA[<p>People have become accustomed to choice: 24 different types of toilet paper, 100s of car makes and models, and 47 different types of <a id="zqb7" title="tomato sauce" href="http://www.ted.com/index.php/talks/malcolm_gladwell_on_spaghetti_sauce.html">tomato sauce</a>.  A lot of this choice can be traced back to some <a id="mjdv" title="now famous" href="http://gladwell.com/2004/2004_09_06_a_ketchup.html">now famous</a> psychophysics experiments performed by Harry Moscowitz in the 70s and 80s for Pepsi and Campbell&#8217;s.  His break-through at the time (which seems obvious now) is that there is no single best tomato sauce.  There are multiple best tomato sauces for different segments of the population.</p>
<p>But in enterprise and consumer software, choice usually means &#8220;what product level or feature set do I want&#8221; and it is typically tied to price:</p>
<ul>
<li>Microsoft offers Vista Home Basic ($199.95), Home Premium ($239.95), Business ($299.95), and Ultimate ($319.95)</li>
<li>Adobe offers their Creative Suite in Design Premium ($1799), Design Standard ($1399), Web Premium ($1699), Web Standard ($999), Production Premium ($1699), and Master Collection ($2499)</li>
<li>and almost every web host in the world offers something akin to Bronze, Silver, Gold (Platinum, Diamond, Kryptonite, &#8230;) service levels, with increasing prices</li>
</ul>
<p><span style="background-color: #ffff00;"><br />
</span>Does this amount of choice make sense?  There are certainly counter-examples in software.  Apple only offers one client version of OS X, and I think it makes buying OS X easier as a result.  Barry Schwartz talks in depth about the paralysis, disappointment, and even depression that an <a id="y63m" title="over-abundance of choice" href="http://www.ted.com/index.php/talks/barry_schwartz_on_the_paradox_of_choice.html">over-abundance of choice</a> can bring.  In a world where <span style="background-color: #ffff00;"><span style="background-color: #ffffff;">almost everyone&#8217;s too busy to decide, it often makes more sense for you to do the choosing for your customers.</span></span></p>
<p>So what can you do to provide useful choices to your customers?  Start from the position of your customer&#8217;s needs, and not your own.  <span style="background-color: #ffffff;"><a id="s4fc" title="Intuit" href="http://www.intuit.com/">Intuit</a> </span> does a very good job of providing choices based on their customers&#8217; needs.</p>
<p>Some <strong>good reasons to offer choice</strong></p>
<ul>
<li>You have <strong>several different segments of your customer base</strong> who can clearly differentiate themselves.  Intuit offers Quickbooks for business accounting and Quicken for personal accounting.  Very clear.  I know whether I&#8217;m running a business or doing my personal finances.</li>
<li><strong>D</strong><strong>ifferent customers need to deploy your software in different ways</strong>.  For example, TurboTax is available as an online application, making it very easy to use.  But for customers who don&#8217;t feel comfortable putting all their private tax information online, Intuit continues to offer TurboTax as installable software.</li>
<li><strong>You offer industry-specific solutions, </strong>with specific value-added features for those industries.  QuickBooks Premier comes in specific versions for Contractors, Non-Profits, Retailers, etc.</li>
</ul>
<p>Some <strong>bad reasons to offer choice</strong></p>
<ul>
<li>You <strong>dreamed up features</strong> that somebody might want.  You did this without talking to customers and users.  Rather than understanding your customers&#8217; needs up front, you ended up using multiple versions and add-ons to make your customers choose when they buy&#8211;  &#8220;We can&#8217;t figure out why you&#8217;d want all these features, but maybe you can&#8221;.</li>
<li>The <strong>internal organization of your sales, marketing, and/or development groups </strong>has caused you to create optional add-ons when a customer would best be served by a single product.  <span style="background-color: #ffff00;"><br />
</span></li>
<li>Your <strong>competitor </strong>offers 4 levels so you think you should too.</li>
<li>You want to <strong>claim to have the lowest prices</strong> in your market, so you build a version of your product that&#8217;s so stripped down it&#8217;s useless.</li>
</ul>
<p><span style="background-color: #ffff00;"><br />
</span><span style="background-color: #ffffff;">Why does pricing matter so much, especially these days?</span></p>
<ul>
<li><strong>In a down economy, people tighten their belts</strong>.  Spending they might not have given a second thought to gets re-evaluated.</li>
<li><strong>P</strong><strong>eople will ensure they are getting real value</strong> and will decide, usually emotionally, if they are paying the right price for that value.  This doesn&#8217;t mean that all prices need to be slashed, but pricing, and especially the value of your product must be made crisp and clear to your customers.<strong></strong></li>
<li><span style="background-color: #ffffff;"><strong>People that can&#8217;t afford the &#8220;premium&#8221; option will often choose not to buy at all</strong> rather than to buy the inferior option. In providing a &#8220;status purchase&#8221; on the high end you are eroding the status of the normal purchase.</span></li>
</ul>
<p style="text-align: right;">Toilet paper photo by <a href="http://www.flickr.com/photos/49024304@N00/">anyjazz65</a></p>
]]></content:encoded>
			<wfw:commentRss>http://artoftheproduct.com/2008/12/05/give-them-some-choice/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Art of the Link: End with a High Note</title>
		<link>http://artoftheproduct.com/2008/11/19/art-of-the-link-end-with-a-high-note/</link>
		<comments>http://artoftheproduct.com/2008/11/19/art-of-the-link-end-with-a-high-note/#comments</comments>
		<pubDate>Wed, 19 Nov 2008 11:57:01 +0000</pubDate>
		<dc:creator>sean</dc:creator>
		
		<category><![CDATA[Art of the Link]]></category>

		<category><![CDATA[Sketch]]></category>

		<guid isPermaLink="false">http://artoftheproduct.com/?p=158</guid>
		<description><![CDATA[No matter how great or bad someone's experience is, how the experience ends is going to make a very big impact on how they feel about it. How can you leave your users with a big smile?]]></description>
			<content:encoded><![CDATA[<blockquote><p>&#8220;Two groups of men were asked to rate the experience of having a diagnostic colonoscopy.&#8221;</p></blockquote>
<p>Whenever you can get <a href="http://dswillis.com/uxcrank/?p=64">product design insight</a> that starts with a sentence like that, you have my attention. And what is the advice? It&#8217;s called the <a href="http://dswillis.com/uxcrank/?p=64">Peak-End Rule</a>. No matter how great or bad someone&#8217;s experience is, how the experience ends is going to make a very big impact on how they feel about it. Read that last sentence one more time and think about your own products for a minute. </p>
<p>How often do you think about how a user finishes using your product? What&#8217;s the last thing they do before they stop using it? How can you make that last thing better? How can you leave your users with a big smile?</p>
<p>These are good questions and I had never thought to ask them. <a href="http://www.dswillis.com/">Dan Willis</a> works for <a href="http://www.sapient.com/">Sapient</a> and writes a blog, <a href="http://dswillis.com/uxcrank/">UX Crank,</a> full of good advice about matters of user experience. You should read it, I highly recommended it.</p>
]]></content:encoded>
			<wfw:commentRss>http://artoftheproduct.com/2008/11/19/art-of-the-link-end-with-a-high-note/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Leave the Abstract to Art</title>
		<link>http://artoftheproduct.com/2008/11/08/leave-the-abstract-to-art/</link>
		<comments>http://artoftheproduct.com/2008/11/08/leave-the-abstract-to-art/#comments</comments>
		<pubDate>Sat, 08 Nov 2008 12:00:45 +0000</pubDate>
		<dc:creator>sean</dc:creator>
		
		<category><![CDATA[Featured Article]]></category>

		<guid isPermaLink="false">http://artoftheproduct.com/?p=89</guid>
		<description><![CDATA[Use the vocabulary of your users, not the vocabulary of your own abstract creations. Even though your software is flexible and is therefore capable of supporting many different opinions, you must pick the one way you think is best for your customers and then defend the hell out of it.]]></description>
			<content:encoded><![CDATA[<p>I recently provided a guest post to <a href="http://www.47hats.com/?p=737">47hats.com</a>, the blog that&#8217;s helping microISVs and software startups succeed. In the post I explain how abstraction that&#8217;s useful in the software development process can sabotage your product when exposed to users.</p>
<blockquote><p>The Law of Overexposed Abstractions - the users of your software don’t benefit from the same abstractions that benefited you in building the software</p></blockquote>
<p>Read the <a href="http://www.47hats.com/?p=737">full article</a>. It&#8217;s gotten some great comments.</p>
]]></content:encoded>
			<wfw:commentRss>http://artoftheproduct.com/2008/11/08/leave-the-abstract-to-art/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Stroke of Genius: Mapping Innovation</title>
		<link>http://artoftheproduct.com/2008/11/08/usability-quick-take-mapping-innovation/</link>
		<comments>http://artoftheproduct.com/2008/11/08/usability-quick-take-mapping-innovation/#comments</comments>
		<pubDate>Sat, 08 Nov 2008 11:14:45 +0000</pubDate>
		<dc:creator>sean</dc:creator>
		
		<category><![CDATA[Sketch]]></category>

		<category><![CDATA[Stroke of Genius]]></category>

		<guid isPermaLink="false">http://artoftheproduct.com/?p=141</guid>
		<description><![CDATA[How do you decide if something is a needed innovation or innovation for innovation's sake? Is it just a distraction, a fad, a nuisance or gimmick? Is it a needed change or a usability nightmare?]]></description>
			<content:encoded><![CDATA[<p>I recently <a href="http://artoftheproduct.com/?p=61">waxed poetic on the power of innovation</a>. So how do you decide if something is a needed innovation or innovation for innovation&#8217;s sake? Is it just a distraction, a fad, a nuisance or gimmick? Is it a needed change or just a usability nightmare? It can be very hard when caught up in the spirit of something exciting and new to tell the difference. Unless we are embroiled in the innovation ourselves we usually get to take a removed stance and rely on 20/20 hindsight. In our hindsight we get to laugh at the blindness of the naysayers of needed innovations or at the naivety of the proponents of fads and gimmicks. Try not to laugh so hard next time because it&#8217;s not so easy at the time.</p>
<p>Here is an innovation I can get behind. Let&#8217;s start teaching kids at an early age that ALL maps are fictions. That the only accurate representation of something is the thing itself (leaving aside Kantian epistemological concerns until at least High School). If the only maps we grow up seeing are the same old projections of geographically focused maps then everything else looks both foreign and wrong.</p>
<p>Here are two maps that show results of the recent U.S. presidential election. Both show how Obama won the urban centers and McCain won the surrounding rural areas. The map on the right has made size a function of population, not geography, and it uses shades between red and blue. The one on the right, from Physicist Mark Newman, is the more informative and innovative of the two. Are we open enough to cartographic innovations? Why didn&#8217;t I see something this informative on CNN, ABC, NBC or CBS on election night?</p>
<p><a href="http://www.sciencefriday.com/videos/watch/10176"><img class="aligncenter" title="Mark Newmans Electoral Maps" src="http://artoftheproduct.com/images/electoral_maps.png" alt="" width="342" height="102" /></a></p>
<p>Get the complete story on Mark Newman&#8217;s new electoral map in this <a href="http://www.sciencefriday.com/videos/watch/10176">short video</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://artoftheproduct.com/2008/11/08/usability-quick-take-mapping-innovation/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Stroke of Genius: Guess What They Want</title>
		<link>http://artoftheproduct.com/2008/11/04/usability-quick-take-guess-what-they-want/</link>
		<comments>http://artoftheproduct.com/2008/11/04/usability-quick-take-guess-what-they-want/#comments</comments>
		<pubDate>Wed, 05 Nov 2008 02:53:21 +0000</pubDate>
		<dc:creator>jake</dc:creator>
		
		<category><![CDATA[Sketch]]></category>

		<category><![CDATA[Stroke of Genius]]></category>

		<guid isPermaLink="false">http://artoftheproduct.com/?p=136</guid>
		<description><![CDATA[Today is election day, and Google knows that. When you can correctly guess what your users are looking for, you have the chance to delight them.]]></description>
			<content:encoded><![CDATA[<p>Today is election day, and Google knows that.  So when you enter the search &#8220;where do I vote&#8221; (or anything similar), you get this:</p>
<p><a href="http://artoftheproduct.com/wp-content/uploads/2008/11/googlevote.gif"><img class="alignnone size-full wp-image-137" title="googlevote" src="http://artoftheproduct.com/wp-content/uploads/2008/11/googlevote.gif" alt="" width="500" height="349" /></a></p>
<p>And if you then enter your home address you get a map of your polling location.  This is brilliant.  When you can correctly guess what your users are looking for, you have the chance to delight them.  A few things to keep in mind when guessing what your users want:</p>
<ul>
<li>Give them what they want, not what you want them to want</li>
<li>Guessing works best when you know most of your users are in a certain frame of mind (e.g. voting on election day, preparing taxes in April)</li>
<li>Guessing can also work well if you deliver personalized experiences to your users (Amazon does a great job of this)</li>
<li>Since guesses can be wrong, don&#8217;t lock your users into your guess.  Google still returns standard results in the example above, letting users easily ignore their guess.</li>
</ul>
<p>So while you have to be careful, if you find an opportunity to make a good guess about what your users want, surprise them with excellent service.</p>
]]></content:encoded>
			<wfw:commentRss>http://artoftheproduct.com/2008/11/04/usability-quick-take-guess-what-they-want/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
