<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>UsabilityBlog</title>
	
	<link>http://www.usabilityblog.com</link>
	<description>Blogging about usability, user experience and design</description>
	<lastBuildDate>Fri, 19 Oct 2012 17:39:56 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/usabilityblog/FPcP" /><feedburner:info uri="usabilityblog/fpcp" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license><image><link>http://creativecommons.org/licenses/by-sa/3.0/</link><url>http://creativecommons.org/images/public/somerights20.gif</url><title>Some Rights Reserved</title></image><item>
		<title>Some Friday UX WTF’s For You</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/OPRu_59xKk8/</link>
		<comments>http://www.usabilityblog.com/2012/10/some-friday-ux-wtfs-for-you/#comments</comments>
		<pubDate>Fri, 19 Oct 2012 17:38:20 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Bring The Funny]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[eCommerce]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[UX And...]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=970</guid>
		<description><![CDATA[It&#8217;s Friday, I&#8217;ve been working long and hard on very exciting client projects, and I&#8217;m just not up to writing cogent prose. So here are some UX WTF pics. Enjoy your weekend fellow UX&#8217;ers. A &#8220;Non-Flash Version&#8221; button? You&#8217;re Doing It Wrong. &#160; eCommerce Rule #1: Click a picture, get bigger picture. eCommerce Rule #2. [...]]]></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%2F2012%2F10%2Fsome-friday-ux-wtfs-for-you%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F10%2Fsome-friday-ux-wtfs-for-you%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>It&#8217;s Friday, I&#8217;ve been working long and hard on very exciting client projects, and I&#8217;m just not up to writing cogent prose. So here are some UX WTF pics. Enjoy your weekend fellow UX&#8217;ers.</p>
<p>A &#8220;Non-Flash Version&#8221; button? You&#8217;re Doing It Wrong.</p>
<p><a href="http://www.usabilityblog.com/2012/10/some-friday-ux-wtfs-for-you/non-flash-2/" rel="attachment wp-att-972"><img class="alignnone size-large wp-image-972" title="Non-Flash" src="http://www.usabilityblog.com/wp-content/uploads/2012/10/Non-Flash1-512x349.png" alt="" width="512" height="349" /></a></p>
<p>&nbsp;</p>
<p>eCommerce Rule #1: Click a picture, get bigger picture.</p>
<p>eCommerce Rule #2. Don&#8217;t violate Rule #1.</p>
<p><a href="http://www.usabilityblog.com/2012/10/some-friday-ux-wtfs-for-you/attachment/672502440/" rel="attachment wp-att-973"><img class="alignnone size-full wp-image-973" title="672502440" src="http://www.usabilityblog.com/wp-content/uploads/2012/10/672502440.png" alt="" width="600" height="337" /></a></p>
<p>While we&#8217;re on the topic of small product pictures&#8230;<br />
<a title="How Not To Display Products by pjsherman, on Flickr" href="http://www.flickr.com/photos/paulsherman/8023504719/"><img src="http://farm9.staticflickr.com/8174/8023504719_a9d50eca3b_z.jpg" alt="How Not To Display Products" width="500" height="500" /></a></p>
<p>&nbsp;</p>
<p>When all else fails, there&#8217;s always after-the-fact design modifications.<br />
<a title="photo by pjsherman, on Flickr" href="http://www.flickr.com/photos/paulsherman/6489644021/"><img src="http://farm8.staticflickr.com/7143/6489644021_ee60778ab3_z.jpg" alt="photo" width="480" height="320" /></a></p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=OPRu_59xKk8:txlp3YZzvo0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=OPRu_59xKk8:txlp3YZzvo0:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=OPRu_59xKk8:txlp3YZzvo0:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=OPRu_59xKk8:txlp3YZzvo0:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=OPRu_59xKk8:txlp3YZzvo0:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=OPRu_59xKk8:txlp3YZzvo0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=OPRu_59xKk8:txlp3YZzvo0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=OPRu_59xKk8:txlp3YZzvo0:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/OPRu_59xKk8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/10/some-friday-ux-wtfs-for-you/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/10/some-friday-ux-wtfs-for-you/</feedburner:origLink></item>
		<item>
		<title>How Not To Display Products</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/jSiBzSaVueg/</link>
		<comments>http://www.usabilityblog.com/2012/09/how-not-to-display-products/#comments</comments>
		<pubDate>Tue, 25 Sep 2012 15:28:30 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=964</guid>
		<description><![CDATA[How Not To Display Products, a photo by pjsherman on Flickr. When I discuss design and usability, I try to share both good and bad examples. Today&#8217;s a bad example day. Here&#8217;s a product listing page &#8211; actually, it&#8217;s the store&#8217;s home page &#8211; that just isn&#8217;t working. Why? Here&#8217;s a a few key reasons, [...]]]></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%2F2012%2F09%2Fhow-not-to-display-products%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F09%2Fhow-not-to-display-products%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0px 0px 10px; padding: 0px; font-size: 0.8em; line-height: 1.6em; text-align: center;"><a title="How Not To Display Products" href="http://www.flickr.com/photos/paulsherman/8023504719/"><img class="aligncenter" src="http://farm9.staticflickr.com/8174/8023504719_a9d50eca3b.jpg" alt="How Not To Display Products by pjsherman" /></a><br />
<span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/8023504719/">How Not To Display Products</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>When I discuss design and usability, I try to share both good and bad examples.</p>
<p>Today&#8217;s a bad example day.</p>
<p>Here&#8217;s a product listing page &#8211; actually, it&#8217;s the store&#8217;s home page &#8211; that just isn&#8217;t working.</p>
<p>Why? Here&#8217;s a a few key reasons, and I&#8217;m sure you can come up with more:</p>
<ul>
<li> The product pictures are ridiculously small and dark. I can&#8217;t tell one from another.</li>
</ul>
<ul>
<li>There&#8217;s no context. I should be able to tell at a glance which products fit my guitar and which don&#8217;t.</li>
</ul>
<ul>
<li>You&#8217;d have to be on the site to see this problem (it&#8217;s &#8220;<a href="http://store.guitarworks.net/">store.guitarworks.net</a>&#8220;), but they&#8217;ve implemented the wrong selection cursor. For some unknown reason, the cursor changes to &#8220;move&#8221; (grabby hand) instead of &#8220;select&#8221; (pointy finger). That&#8217;s just sloppy coding.</li>
</ul>
<p>Diving down to the individual product page isn&#8217;t much better. I have piles of work to do, so you&#8217;re just going to have to check out one yourself. Try <a href="http://store.rsguitarworks.net/5WAY.html" rel="nofollow">store.rsguitarworks.net/5WAY.html</a>. And feel free to buy me some cream colored historic pickup rings for my &#8217;08 Les Paul &#8211; if you can find them that is.</p>
<p>UPDATE: So I just belatedly realized that the reason for the &#8220;move&#8221; cursor is so you can drag &#8216;n drop your item into the shopping cart on the right of the page. Sorry, but that&#8217;s too clever by half. People don&#8217;t shop online like that. They click &#8220;add to cart&#8221;. And besides, there&#8217;s not enough information on a product listing page to make a selection. Sigh.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=jSiBzSaVueg:n17hkoM6UjU:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=jSiBzSaVueg:n17hkoM6UjU:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=jSiBzSaVueg:n17hkoM6UjU:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=jSiBzSaVueg:n17hkoM6UjU:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=jSiBzSaVueg:n17hkoM6UjU:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=jSiBzSaVueg:n17hkoM6UjU:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=jSiBzSaVueg:n17hkoM6UjU:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=jSiBzSaVueg:n17hkoM6UjU:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/jSiBzSaVueg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/09/how-not-to-display-products/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/09/how-not-to-display-products/</feedburner:origLink></item>
		<item>
		<title>eBay Classifieds: What’s Missing From This Page?</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/5qbtFIphqRg/</link>
		<comments>http://www.usabilityblog.com/2012/09/ebay-classifieds-whats-missing-from-this-page/#comments</comments>
		<pubDate>Thu, 13 Sep 2012 14:57:27 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[eCommerce]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=952</guid>
		<description><![CDATA[A few days ago I decided to sign up for eBay Classifieds so I could sell a few guitars I haven&#8217;t been playing much. I cruised through signup with no problem&#8230;and then face-planted at this brick wall of a page: Ouch. Stopped me dead in my tracks. So what&#8217;s missing from this picture? I mean [...]]]></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%2F2012%2F09%2Febay-classifieds-whats-missing-from-this-page%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F09%2Febay-classifieds-whats-missing-from-this-page%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>A few days ago I decided to sign up for eBay Classifieds so I could sell a few guitars I haven&#8217;t been playing much.</p>
<p>I cruised through signup with no problem&#8230;and then face-planted at this brick wall of a page:</p>
<p><a href="http://www.usabilityblog.com/2012/09/ebay-classifieds-whats-missing-from-this-page/missingcta/" rel="attachment wp-att-957"><img class="alignnone  wp-image-957" title="MissingCTA" src="http://www.usabilityblog.com/wp-content/uploads/2012/09/MissingCTA.png" alt="" width="610" height="356" /></a></p>
<p>Ouch. Stopped me dead in my tracks.</p>
<p>So what&#8217;s missing from this picture? I mean that literally, as in &#8220;what *should* be here but isn&#8217;t?</p>
<p>Yeah, you guessed it. A call-to-action in the main content area. Honestly, this workflow design is so 1992, I&#8217;m surprised it&#8217;s survived eBay&#8217;s typically close scrutiny of its user experience.</p>
<p>Here&#8217;s a simple way to turn this page from a brick wall to a well-marked path:</p>
<p><a href="http://www.usabilityblog.com/2012/09/ebay-classifieds-whats-missing-from-this-page/fixedcta/" rel="attachment wp-att-955"><img class="alignnone  wp-image-955" title="FixedCTA" src="http://www.usabilityblog.com/wp-content/uploads/2012/09/FixedCTA.png" alt="" width="610" height="355" /></a></p>
<p>Or even better&#8230;try this one on for size:</p>
<p><a href="http://www.usabilityblog.com/2012/09/ebay-classifieds-whats-missing-from-this-page/fixedcta2/" rel="attachment wp-att-956"><img class="alignnone  wp-image-956" title="FixedCTA2" src="http://www.usabilityblog.com/wp-content/uploads/2012/09/FixedCTA2.png" alt="" width="610" height="356" /></a></p>
<p>Good workflow design is not rocket science, folks!</p>
<p>&nbsp;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=5qbtFIphqRg:FCPtyZpwGX4:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=5qbtFIphqRg:FCPtyZpwGX4:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=5qbtFIphqRg:FCPtyZpwGX4:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=5qbtFIphqRg:FCPtyZpwGX4:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=5qbtFIphqRg:FCPtyZpwGX4:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=5qbtFIphqRg:FCPtyZpwGX4:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=5qbtFIphqRg:FCPtyZpwGX4:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=5qbtFIphqRg:FCPtyZpwGX4:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/5qbtFIphqRg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/09/ebay-classifieds-whats-missing-from-this-page/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/09/ebay-classifieds-whats-missing-from-this-page/</feedburner:origLink></item>
		<item>
		<title>Fab.com: So Well-Designed My Head Asplode</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/P1N2NP_XKiU/</link>
		<comments>http://www.usabilityblog.com/2012/08/fab-com-so-well-designed-my-head-asplode/#comments</comments>
		<pubDate>Tue, 07 Aug 2012 15:17:11 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[eCommerce]]></category>
		<category><![CDATA[Experience Strategy]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=948</guid>
		<description><![CDATA[For the first time in recent memory, I did something I almost *never* do &#8211; I clicked on a banner ad. Yes, I know, for shame. But here&#8217;s the thing: the banner image was enticing &#8211; it showed a cable management solution for &#8220;iDevice&#8221; plugs/cables that appeared well-designed and functional &#8211; and I just couldn&#8217;t [...]]]></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%2F2012%2F08%2Ffab-com-so-well-designed-my-head-asplode%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F08%2Ffab-com-so-well-designed-my-head-asplode%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>For the first time in recent memory, I did something I almost *never* do &#8211; I clicked on a banner ad. Yes, I know, for shame.</p>
<p>But here&#8217;s the thing: the banner image was enticing &#8211; it showed a cable management solution for &#8220;iDevice&#8221; plugs/cables that appeared well-designed and functional &#8211; and I just couldn&#8217;t resist. When I landed on the campaign page, I was just wowed &#8211; awesome product presentation, easy-to-navigate  categories, and all the buzzwords that give you that happy, hip feeling &#8211; &#8220;crowd-funded&#8221;, &#8220;domestically-produced&#8221;, etc.</p>
<p>I am so buying myself the iPhone cable holder in &#8220;Nibbles Green&#8221;.</p>
<p>The login process itself was remarkably friendly and easy, and cleverly split the process between email capture and password entry. There was no authentication round, which frankly is unnecessary for a shopping site. My only question with this practice is why bother to capture the email at all before the purchase&#8230;.but I&#8217;m guessing it&#8217;s so they can tempt me with cleverly-designed email campaigns. After all, I *did* just cough up my email address, which is implicit permission to market to me.</p>
<p>Anyway, if you want to see what a well-designed experience looks and acts like, check out Fab.com.</p>
<p>One last thing: I&#8217;m like a month late providing reviews of those design tools I said I&#8217;d look at. Sorry! Project work comes first. I promise I&#8217;ll get around to it soon.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=P1N2NP_XKiU:6jcmLQLLZBQ:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=P1N2NP_XKiU:6jcmLQLLZBQ:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=P1N2NP_XKiU:6jcmLQLLZBQ:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=P1N2NP_XKiU:6jcmLQLLZBQ:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=P1N2NP_XKiU:6jcmLQLLZBQ:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=P1N2NP_XKiU:6jcmLQLLZBQ:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=P1N2NP_XKiU:6jcmLQLLZBQ:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=P1N2NP_XKiU:6jcmLQLLZBQ:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/P1N2NP_XKiU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/08/fab-com-so-well-designed-my-head-asplode/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/08/fab-com-so-well-designed-my-head-asplode/</feedburner:origLink></item>
		<item>
		<title>Two Prototyping Tools I’ll Be Trying Out This Week</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/NimAZwsDyFk/</link>
		<comments>http://www.usabilityblog.com/2012/07/two-prototyping-tools-ill-be-trying-out-this-week/#comments</comments>
		<pubDate>Mon, 09 Jul 2012 13:44:12 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=942</guid>
		<description><![CDATA[I love me my Omnigraffle. I&#8217;ve tweaked the hell out of it, thanks to the goodies from Graffletopia and Konigi. But the user experience field is rapidly shifting, and although I consider myself mostly an ideation research practitioner, I still have to create medium- and high-fidelity wireframe screens and workflows for clients. With that in [...]]]></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%2F2012%2F07%2Ftwo-prototyping-tools-ill-be-trying-out-this-week%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F07%2Ftwo-prototyping-tools-ill-be-trying-out-this-week%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>I love me my Omnigraffle. I&#8217;ve tweaked the hell out of it, thanks to the goodies from <a href="http://www.graffletopia.com/">Graffletopia</a> and <a href="http://www.konigi.com">Konigi</a>. But the user experience field is rapidly shifting, and although I consider myself mostly an ideation research practitioner, I still have to create medium- and high-fidelity wireframe screens and workflows for clients.</p>
<p>With that in mind, I am going to try out two prototyping tools I&#8217;ve heard about over the past month:</p>
<ol>
<li><a href="http://www.antetype.com/">Antetype</a> &#8211; A desktop-based (as opposed to cloud-based) application. It looks like it has lots of widgets, the ability to export and send to clients, and the big potential advantage to me is that it supports adaptive / dynamic layout behaviors.</li>
<li><a href="http://www.fluidui.com/">FluidUI</a> &#8211; Bills itself as a tool for &#8220;iPhone and Android mobile mockups.&#8221; The big potential win for this tool is the claim that it lets you &#8220;test designs on phone and tablet.&#8221; If so, awesome.</li>
</ol>
<p>So I&#8217;ll let you know how it goes. I&#8217;ve scheduled this post for Monday 9 July, so if you haven&#8217;t heard anything by end of week feel free to send me guilt-inducing messages.</p>
<p>&nbsp;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=NimAZwsDyFk:jAENaHxjwKg:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=NimAZwsDyFk:jAENaHxjwKg:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=NimAZwsDyFk:jAENaHxjwKg:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=NimAZwsDyFk:jAENaHxjwKg:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=NimAZwsDyFk:jAENaHxjwKg:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=NimAZwsDyFk:jAENaHxjwKg:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=NimAZwsDyFk:jAENaHxjwKg:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=NimAZwsDyFk:jAENaHxjwKg:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/NimAZwsDyFk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/07/two-prototyping-tools-ill-be-trying-out-this-week/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/07/two-prototyping-tools-ill-be-trying-out-this-week/</feedburner:origLink></item>
		<item>
		<title>“Very Usable” Makes “Not Usable” Even More Noticeable</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/w4F0OTHoGlo/</link>
		<comments>http://www.usabilityblog.com/2012/07/very-usable-makes-not-usable-even-more-noticeable/#comments</comments>
		<pubDate>Fri, 06 Jul 2012 14:56:46 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=938</guid>
		<description><![CDATA[[This conversation happened late last week..] Me: &#8220;I ordered Season 2 of Doctor Who and sent it to my TiVo, but only the first two episodes are there.&#8221; Amazon customer rep (yes, you can find a phone number for Amazon if you search long enough): &#8220;OK, I&#8217;ll set it to download again. Y&#8217;know, you can [...]]]></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%2F2012%2F07%2Fvery-usable-makes-not-usable-even-more-noticeable%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F07%2Fvery-usable-makes-not-usable-even-more-noticeable%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>[This conversation happened late last week..]</p>
<blockquote><p>Me: &#8220;I ordered Season 2 of Doctor Who and sent it to my TiVo, but only the first two episodes are there.&#8221;</p>
<p>Amazon customer rep (yes, you can find a phone number for Amazon if you search long enough): &#8220;OK, I&#8217;ll set it to download again. Y&#8217;know, you can do this yourself, all you have to do is [explains in general where to go to view and manage my Amazon video orders].&#8221;</p>
<p>Me: &#8220;Great! I really don&#8217;t want to call again next time this happens!&#8221;</p></blockquote>
<p>[Skip to today...]</p>
<p>I&#8217;m at Amazon.com, looking at my video purchases, and I absolutely cannot figure out how to re-download my videos. In &#8220;scent of information&#8221; terms, I am not smelling a thing. I&#8217;m hitting multiple brick walls, swirling from the help page back to the video library page, you name it. I&#8217;m stuck. Why does this feel worse than my experiences with other sites and services?</p>
<p>That&#8217;s easy. Amazon&#8217;s consumer site is just so damn useful and usable that it&#8217;s even more noticeable &#8211; and annoying &#8211; in those rare instances when it fails. When my high expectations for the Amazon experience &#8211; built up by years of great interactions with the site &#8211; are not met, it&#8217;s even more disappointing. This really underscores the need to design consistent and consistently usable customer interactions.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=w4F0OTHoGlo:NTnuH9AJlSY:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=w4F0OTHoGlo:NTnuH9AJlSY:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=w4F0OTHoGlo:NTnuH9AJlSY:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=w4F0OTHoGlo:NTnuH9AJlSY:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=w4F0OTHoGlo:NTnuH9AJlSY:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=w4F0OTHoGlo:NTnuH9AJlSY:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=w4F0OTHoGlo:NTnuH9AJlSY:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=w4F0OTHoGlo:NTnuH9AJlSY:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/w4F0OTHoGlo" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/07/very-usable-makes-not-usable-even-more-noticeable/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/07/very-usable-makes-not-usable-even-more-noticeable/</feedburner:origLink></item>
		<item>
		<title>One Page Of Awesomeness To Help You Manage Your UX Career</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/N7Mn9yYyK3Q/</link>
		<comments>http://www.usabilityblog.com/2012/07/one-page-of-awesomeness-to-help-you-manage-your-ux-career/#comments</comments>
		<pubDate>Thu, 05 Jul 2012 13:41:22 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[UX Career Info]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=934</guid>
		<description><![CDATA[I&#8217;ve been meaning to write this post for a while. Patrick Neeman, UX Director at Jobvite and proprietor of UsabilityCounts.com and creator of the UX Drinking Game, maintains a page at UsabilityCounts that is full to overflowing with fantastic &#8211; and FREE &#8211; resources for managing your user experience career. What&#8217;s so great about Patrick&#8217;s [...]]]></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%2F2012%2F07%2Fone-page-of-awesomeness-to-help-you-manage-your-ux-career%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F07%2Fone-page-of-awesomeness-to-help-you-manage-your-ux-career%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>I&#8217;ve been meaning to write this post for a while. <a href="https://twitter.com/#!/usabilitycounts">Patrick Neeman</a>, UX Director at Jobvite and proprietor of <a href="http://www.usabilitycounts.com/">UsabilityCounts.com</a> and creator of the <a href="http://www.uxdrinkinggame.com/">UX Drinking Game</a>, maintains <a href="http://www.usabilitycounts.com/download-ux-resume-template/">a page at UsabilityCounts</a> that is full to overflowing with fantastic &#8211; and FREE &#8211; resources for managing your user experience career.</p>
<p>What&#8217;s so great about Patrick&#8217;s collection of resources?</p>
<ul>
<li><a href="http://tinyurl.com/uxresume">The UX resume template</a> &#8211; this alone makes it worth the visit.</li>
<li>For people considering UX as a career (and even for newish UX&#8217;ers), there&#8217;s &#8220;<a href="http://www.usabilitycounts.com/2011/10/18/how-to-get-started-in-user-experience-seven-tips/">How to Get Started In UX</a>&#8220;.</li>
<li><a href="http://www.usabilitycounts.com/2012/06/22/lynn-teo-portfolios-matter-building-the-portfolio-to-win-the-job/">An embedded preso</a> by Lynn Teo that demystifies the stressful process of creating and maintaining your UX portfolio.</li>
</ul>
<p>I could go on, but you need to just go check it out yourself.</p>
<p><a href="http://www.usabilitycounts.com/download-ux-resume-template/">One Page Of UX Career Awesomeness</a> (my title) :: Patrick Neeman</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=N7Mn9yYyK3Q:TOvoN0tL4Ws:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=N7Mn9yYyK3Q:TOvoN0tL4Ws:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=N7Mn9yYyK3Q:TOvoN0tL4Ws:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=N7Mn9yYyK3Q:TOvoN0tL4Ws:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=N7Mn9yYyK3Q:TOvoN0tL4Ws:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=N7Mn9yYyK3Q:TOvoN0tL4Ws:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=N7Mn9yYyK3Q:TOvoN0tL4Ws:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=N7Mn9yYyK3Q:TOvoN0tL4Ws:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/N7Mn9yYyK3Q" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/07/one-page-of-awesomeness-to-help-you-manage-your-ux-career/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/07/one-page-of-awesomeness-to-help-you-manage-your-ux-career/</feedburner:origLink></item>
		<item>
		<title>The Pivot, Or Why Product Managers Seem So Crazy Sometimes</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/Y0HhqQEu8HQ/</link>
		<comments>http://www.usabilityblog.com/2012/06/the-pivot-or-why-product-managers-seem-so-crazy-sometimes/#comments</comments>
		<pubDate>Fri, 22 Jun 2012 14:30:26 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Organizational]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Research]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=924</guid>
		<description><![CDATA[Most UX&#8217;ers who&#8217;ve worked for a product or service company know that good product managers are our strongest leverage points, and often the most vocal proponents of UX research and design. As one great PM once told me, UX research was his &#8220;decision insurance&#8221; &#8211; that is, we were the folks who could bring the [...]]]></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%2F2012%2F06%2Fthe-pivot-or-why-product-managers-seem-so-crazy-sometimes%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F06%2Fthe-pivot-or-why-product-managers-seem-so-crazy-sometimes%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Most UX&#8217;ers who&#8217;ve worked for a product or service company know that good product managers are our strongest leverage points, and often the most vocal proponents of UX research and design. As one great PM once told me, UX research was his &#8220;decision insurance&#8221; &#8211; that is, we were the folks who could bring the data to validate his business decisions&#8230;and also help him to recognize a mistake before it became too costly.</p>
<p>You may have also realized that even good product managers sometimes get saddled with a reputation for being flighty or inconsistent. Before I gained the business experience I have now, this quality mystified me. It wasn&#8217;t until I read some of the <a href="http://www.sequentlearning.com/reading-list.php">key product management books</a> that I really got a handle on the mind of the product manager.</p>
<p>A good product leader is always trying to optimize the product-to-market fit. They&#8217;re trying to uncover and exploit the most sustainable and scalable business model. And (way) more often than not, a product leader will find that the plan for delivering a product, the product features, and/or product positioning needs to change. These types of changes have come to be known as a &#8220;<a href="http://www.inc.com/magazine/20110201/the-art-of-the-pivot.html">pivot</a>&#8220;.</p>
<p>That&#8217;s why you&#8217;ll find <a href="http://steveblank.com/2010/04/12/why-startups-are-agile-and-opportunistic-%E2%80%93-pivoting-the-business-model/">this article from Steve Blank</a> as illuminating as I did. Not only does it explain how product leaders search for a sustainable and scalable business model; it also provides insight into the mind of the product manager. It&#8217;s short and to the point. Check it out.</p>
<p><a href="http://steveblank.com/2010/04/12/why-startups-are-agile-and-opportunistic-%E2%80%93-pivoting-the-business-model/">Why Startups are Agile and Opportunistic – Pivoting the Business Model</a>  ::  <a href="http://steveblank.com/">Steve Blank</a></p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=Y0HhqQEu8HQ:Uf9PuX-kUQ4:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=Y0HhqQEu8HQ:Uf9PuX-kUQ4:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=Y0HhqQEu8HQ:Uf9PuX-kUQ4:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=Y0HhqQEu8HQ:Uf9PuX-kUQ4:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=Y0HhqQEu8HQ:Uf9PuX-kUQ4:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=Y0HhqQEu8HQ:Uf9PuX-kUQ4:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=Y0HhqQEu8HQ:Uf9PuX-kUQ4:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=Y0HhqQEu8HQ:Uf9PuX-kUQ4:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/Y0HhqQEu8HQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/06/the-pivot-or-why-product-managers-seem-so-crazy-sometimes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/06/the-pivot-or-why-product-managers-seem-so-crazy-sometimes/</feedburner:origLink></item>
		<item>
		<title>Confusing Instructions In A Tiny Contact Form</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/x5cK_PI3rOQ/</link>
		<comments>http://www.usabilityblog.com/2012/06/confusing-instructions-in-a-tiny-contact-form/#comments</comments>
		<pubDate>Thu, 21 Jun 2012 13:10:16 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Bring The Funny]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Mobile]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=928</guid>
		<description><![CDATA[Kia of America, I find your contact form instructions very confusing. This has got to be a mistake, right? There&#8217;s no way a form was intentionally designed like this. This has got to be some leftover QA junk. Please tell me it is.]]></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%2F2012%2F06%2Fconfusing-instructions-in-a-tiny-contact-form%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F06%2Fconfusing-instructions-in-a-tiny-contact-form%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Kia of America, I find your contact form instructions very confusing.</p>
<p>This has got to be a mistake, right? There&#8217;s no way a form was intentionally designed like this. This has got to be some leftover QA junk. Please tell me it is.</p>
<p><a href="http://www.usabilityblog.com/2012/06/confusing-instructions-in-a-tiny-contact-form/attachment/555016101/" rel="attachment wp-att-931"><img class="size-full wp-image-931 aligncenter" title="555016101" src="http://www.usabilityblog.com/wp-content/uploads/2012/06/555016101.png" alt="" width="260" height="365" /></a></p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=x5cK_PI3rOQ:vtH6faC4Tx4:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=x5cK_PI3rOQ:vtH6faC4Tx4:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=x5cK_PI3rOQ:vtH6faC4Tx4:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=x5cK_PI3rOQ:vtH6faC4Tx4:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=x5cK_PI3rOQ:vtH6faC4Tx4:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=x5cK_PI3rOQ:vtH6faC4Tx4:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=x5cK_PI3rOQ:vtH6faC4Tx4:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=x5cK_PI3rOQ:vtH6faC4Tx4:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/x5cK_PI3rOQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/06/confusing-instructions-in-a-tiny-contact-form/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/06/confusing-instructions-in-a-tiny-contact-form/</feedburner:origLink></item>
		<item>
		<title>UX &amp; Dev Double-Shot</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/a63qRKsOFL0/</link>
		<comments>http://www.usabilityblog.com/2012/06/ux-dev-double-shot/#comments</comments>
		<pubDate>Wed, 20 Jun 2012 18:22:17 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Organizational]]></category>
		<category><![CDATA[Social]]></category>
		<category><![CDATA[UX And...]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=922</guid>
		<description><![CDATA[Long time no post. Sorry; life&#8217;s been a bit unbalanced as of late. All good now. Today I&#8217;d like to draw your attention to two resources. One is an update from the good folks at interaction-design.org. They&#8217;ve just posted a sneak preview of their newest chapter of their online UX book. It covers socio-technical system [...]]]></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%2F2012%2F06%2Fux-dev-double-shot%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F06%2Fux-dev-double-shot%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Long time no post. Sorry; life&#8217;s been a bit unbalanced as of late. All good now.</p>
<p>Today I&#8217;d like to draw your attention to two resources. One is an update from the good folks at <a href="http://interaction-design.org">interaction-design.org</a>. They&#8217;ve just posted a sneak preview of their newest chapter of their online UX book. It covers socio-technical system design, and can be found <a href="http://www.interaction-design.org/encyclopedia/socio-technical_system_design.html?p=10a6 ">here</a>. I read it. It&#8217;s good. Check it out.</p>
<p>The second resource covers how to scale a development team, and it&#8217;s <a href="http://adam.heroku.com/past/2011/4/28/scaling_a_development_team/">at Adam Wiggin&#8217;s blog</a>. I found it an interesting read from the UX perspective because it illuminates how our engineering partners think about the organization of work and tasks. Another worthwhile read if you&#8217;re a UX&#8217;er and want to better understand the software developer mindset.</p>
<p>Enjoy.</p>
<p>&nbsp;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=a63qRKsOFL0:FUzh2Y3jnI0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=a63qRKsOFL0:FUzh2Y3jnI0:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=a63qRKsOFL0:FUzh2Y3jnI0:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=a63qRKsOFL0:FUzh2Y3jnI0:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=a63qRKsOFL0:FUzh2Y3jnI0:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=a63qRKsOFL0:FUzh2Y3jnI0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=a63qRKsOFL0:FUzh2Y3jnI0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=a63qRKsOFL0:FUzh2Y3jnI0:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/a63qRKsOFL0" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/06/ux-dev-double-shot/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/06/ux-dev-double-shot/</feedburner:origLink></item>
		<item>
		<title>Want Free &amp; Awesome UX Resources? Here’s Where To Go.</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/KlsACdzzTOE/</link>
		<comments>http://www.usabilityblog.com/2012/03/want-free-awesome-ux-resources-heres-where-to-go/#comments</comments>
		<pubDate>Thu, 01 Mar 2012 19:54:11 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Content]]></category>
		<category><![CDATA[Experience Strategy]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Research]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=919</guid>
		<description><![CDATA[Apologies to Mads Soegaard, who emailed me over two weeks ago to tell me that Interaction-Design.org has another &#8220;free as in beer&#8221; chapter available in their online UX encyclopedia. If you haven&#8217;t checked out I-D.org, stop what you&#8217;re doing immediately and go there. I don&#8217;t care if you&#8217;re driving a commuter bus, operating heavy machinery, [...]]]></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%2F2012%2F03%2Fwant-free-awesome-ux-resources-heres-where-to-go%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F03%2Fwant-free-awesome-ux-resources-heres-where-to-go%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Apologies to <a href="http://www.interaction-design.org/references/authors/mads_soegaard.html">Mads Soegaard</a>, who emailed me over two weeks ago to tell me that <a href="http://www.interaction-design.org/">Interaction-Design.org</a> has another &#8220;free as in beer&#8221; chapter available in their online UX encyclopedia.</p>
<p>If you haven&#8217;t checked out <a href="http://www.interaction-design.org/">I-D.org</a>, stop what you&#8217;re doing immediately and go there. I don&#8217;t care if you&#8217;re driving a commuter bus, operating heavy machinery, or sitting for an exam. Just go there now.</p>
<p>Here&#8217;s the kicker: not only do they have contributions from well-known UX&#8217;ers such as John Carroll, Holtzblatt &amp; Beyer, etc&#8230;they&#8217;ve managed to nab a contribution by my favorite innovation writer, Clayton Christensen. Yes. Really.</p>
<p>Here&#8217;s the link to that chapter. I can&#8217;t wait to dig into it myself: <a href="http://www.interaction-design.org/encyclopedia/disruptive_innovation.html?p=10a6">Disruptive Innovation</a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=KlsACdzzTOE:yRq-G52wglA:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=KlsACdzzTOE:yRq-G52wglA:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=KlsACdzzTOE:yRq-G52wglA:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=KlsACdzzTOE:yRq-G52wglA:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=KlsACdzzTOE:yRq-G52wglA:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=KlsACdzzTOE:yRq-G52wglA:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=KlsACdzzTOE:yRq-G52wglA:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=KlsACdzzTOE:yRq-G52wglA:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/KlsACdzzTOE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/03/want-free-awesome-ux-resources-heres-where-to-go/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/03/want-free-awesome-ux-resources-heres-where-to-go/</feedburner:origLink></item>
		<item>
		<title>Longest Dialog Box Ever!</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/p2Pfl4RjGlU/</link>
		<comments>http://www.usabilityblog.com/2012/02/longest-dialog-box-ever/#comments</comments>
		<pubDate>Wed, 15 Feb 2012 15:09:42 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=916</guid>
		<description><![CDATA[Longest Dialog Box Ever! a video by pjsherman on Flickr. Here it is, people. The longest dialog box ever. I&#8217;m guessing 5000, maybe 6000 pixels wide? I know I know, Audacity is free and I shouldn&#8217;t whine. I&#8217;m not. I&#8217;m just amused.]]></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%2F2012%2F02%2Flongest-dialog-box-ever%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F02%2Flongest-dialog-box-ever%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><object type="application/x-shockwave-flash" width="500" height="307" data="http://www.flickr.com/apps/video/stewart.swf?v=109786" classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"><param name="flashvars" value="intl_lang=en-us&#038;photo_secret=662ff1e0f5&#038;photo_id=6881183745&#038;flickr_show_info_box=true"></param><param name="movie" value="http://www.flickr.com/apps/video/stewart.swf?v=109786"></param><param name="bgcolor" value="#000000"></param><param name="allowFullScreen" value="true"></param><embed type="application/x-shockwave-flash" src="http://www.flickr.com/apps/video/stewart.swf?v=109786" bgcolor="#000000" allowfullscreen="true" flashvars="intl_lang=en-us&#038;photo_secret=662ff1e0f5&#038;photo_id=6881183745&#038;flickr_show_info_box=true" height="307" width="500"></embed></object><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/6881183745/">Longest Dialog Box Ever!</a> a video by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>Here it is, people. The longest dialog box ever. </p>
<p>I&#8217;m guessing 5000, maybe 6000 pixels wide?</p>
<p>I know I know, Audacity is free and I shouldn&#8217;t whine. I&#8217;m not. I&#8217;m just amused.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=p2Pfl4RjGlU:99huzQMv0xY:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=p2Pfl4RjGlU:99huzQMv0xY:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=p2Pfl4RjGlU:99huzQMv0xY:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=p2Pfl4RjGlU:99huzQMv0xY:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=p2Pfl4RjGlU:99huzQMv0xY:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=p2Pfl4RjGlU:99huzQMv0xY:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=p2Pfl4RjGlU:99huzQMv0xY:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=p2Pfl4RjGlU:99huzQMv0xY:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/p2Pfl4RjGlU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/02/longest-dialog-box-ever/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/02/longest-dialog-box-ever/</feedburner:origLink></item>
		<item>
		<title>Need A New Site To Feel All Superior To? Check This.</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/lqkedxHwUSE/</link>
		<comments>http://www.usabilityblog.com/2012/02/need-a-new-site-to-feel-all-superior-to-check-this/#comments</comments>
		<pubDate>Wed, 08 Feb 2012 13:40:38 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Bring The Funny]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=914</guid>
		<description><![CDATA[Slow-loading, zoomy Flash animation? Check. Music that kicks on when page loads? Check. Throbbing animated .gifs? Check. Eyestrain-inducing oversaturated color palette? Check. Borderline offensive use of models in suggestive food-eating poses? Check check and check. Bonus points: The site designer link leads to an Apache setup page. Oops. The site&#8217;s got one thing going for [...]]]></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%2F2012%2F02%2Fneed-a-new-site-to-feel-all-superior-to-check-this%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F02%2Fneed-a-new-site-to-feel-all-superior-to-check-this%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<ul>
<li>Slow-loading, zoomy Flash animation? Check.</li>
<li>Music that kicks on when page loads? Check.</li>
<li>Throbbing animated .gifs? Check.</li>
<li>Eyestrain-inducing oversaturated color palette? Check.</li>
<li>Borderline offensive use of models in suggestive food-eating poses? Check check and check.</li>
<li>Bonus points: The site designer link leads to an Apache setup page. Oops.</li>
</ul>
<p>The site&#8217;s got one thing going for it. But I&#8217;m guessing they didn&#8217;t actually research the advantages of radial menus for speed of onscreen target acquisition&#8230;.it&#8217;s more about the pizza visual metaphor. The pizza pie menu is actually more efficient than a drop-down menu. <a href="http://ux.stackexchange.com/questions/1/are-radial-contextual-menus-better-than-vertical-list-menus">Read up on the advantages and drawbacks of radial menus here</a>.</p>
<p>But the zooming pizza slices are, let&#8217;s just say, optically unpleasant.</p>
<p>Could this be another &#8220;so bad it&#8217;s great&#8221; site, like <a href="http://www.usabilityblog.com/?s=lings+cars">Ling&#8217;s Cars</a>? Maybe. I have half a mind to reach out to the site&#8217;s proprietors just to find out. I&#8217;m just so slammed with the <a href="http://www.cloudpassage.com" target="_blank">new and growing company</a> I don&#8217;t have any time to go on this type of adventure these days.</p>
<p>Check it: <a href="http://www.pizza-pop.ch/" target="_blank">www.pizza-pop.ch</a></p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=lqkedxHwUSE:rDTNApBru88:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=lqkedxHwUSE:rDTNApBru88:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=lqkedxHwUSE:rDTNApBru88:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=lqkedxHwUSE:rDTNApBru88:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=lqkedxHwUSE:rDTNApBru88:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=lqkedxHwUSE:rDTNApBru88:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=lqkedxHwUSE:rDTNApBru88:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=lqkedxHwUSE:rDTNApBru88:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/lqkedxHwUSE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/02/need-a-new-site-to-feel-all-superior-to-check-this/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/02/need-a-new-site-to-feel-all-superior-to-check-this/</feedburner:origLink></item>
		<item>
		<title>Ubuntu One: Where Do I Look? What Do I Do?</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/FRg-n6O-TGs/</link>
		<comments>http://www.usabilityblog.com/2012/02/ubuntu-one-where-do-i-look-what-do-i-do/#comments</comments>
		<pubDate>Thu, 02 Feb 2012 15:10:45 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=909</guid>
		<description><![CDATA[Ubuntu One: Where Do I Look? What Do I Do?, a photo by pjsherman on Flickr. This is an object lesson in how not to lay out a screen. Background: While configuring a Linux PC, I found myself setting up Ubuntu One, Canonical&#8217;s cloud sync service. After I entered the confirmation code I received via [...]]]></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%2F2012%2F02%2Fubuntu-one-where-do-i-look-what-do-i-do%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F02%2Fubuntu-one-where-do-i-look-what-do-i-do%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0pt 0pt 10px; padding: 0pt; font-size: 0.8em; line-height: 1.6em; text-align: center;"><a title="Ubuntu One: Where Do I Look? What Do I Do?" href="http://www.flickr.com/photos/paulsherman/6806846659/"><img src="http://farm8.staticflickr.com/7172/6806846659_45749625a3.jpg" alt="Ubuntu One: Where Do I Look? What Do I Do? by pjsherman" /></a><br />
<span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/6806846659/">Ubuntu One: Where Do I Look? What Do I Do?</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>This is an object lesson in how not to lay out a screen.</p>
<p>Background: While configuring a Linux PC, I found myself setting up Ubuntu One, Canonical&#8217;s cloud sync service. After I entered the confirmation code I received via email, I was taken to this screen.</p>
<p>My first reaction: Blargh! Where do I look first? What do I do?</p>
<p>Let&#8217;s break it down:</p>
<ol>
<li>None of the calls-to-action appear to be primary. Nothing screams &#8220;Start here! Click me first!&#8221; The most visually prominent calls just sort of step on each other.</li>
<li>The layout is an eye-hurt. No really. I&#8217;m not exaggerating, it /actually/ hurts my eyes. I can&#8217;t recall the last time a screen layout actually made me go cross-eyed. Little thought seems to have been given to aligning the controls, text and links. I don&#8217;t mean to be too snarky&#8230;but it looks like the UI fairy barfed up links and controls onto the screen.</li>
<li>When I was a wee UX lad, mama always told me &#8220;If you can&#8217;t choose one font size, might as well use them all.&#8221; Unfortunately, mama was wrong. On this screen it&#8217;s disorienting. It adds to the difficulty users will experience trying to find a &#8220;start here&#8221; call-to-action.</li>
<li>Screenshots are helpful&#8230;in theory. But they have to illustrate something helpful to the user. This one falls short. The detail is too small to be of use. It just causes eyestrain. Or maybe I&#8217;m just getting old, and you youngsters have no problem with it. Well good for you. And get off my lawn.</li>
</ol>
<p>I know I&#8217;ve <a href="http://www.usabilityblog.com/?s=Linux">ranked on Linux in the past</a>, so I readily admit that Canonical has made great strides creating a better user experience for desktop Linux. Ubuntu 11.10 is by far the most usable Ubuntu release ever, and Ubuntu has always stood above other distros in ease of install, configuration and initial/ongoing use. But like any app or OS that comes from a legacy of &#8220;built by geeks for geeks&#8221;, there will always be areas of the user experience that don&#8217;t get the UX love and attention they deserve. This screen &#8211; even though it was probably created for more recent distributions &#8211; reminds us of Linux&#8217;s geeky origins.</p>
<p>One last thing, and this is a completely preference-driven personal peccadillo of mine&#8230;bevel-lowered grouping boxes must die. Hate &#8216;em. They&#8217;re /so/ Windows 3.11&#8230;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=FRg-n6O-TGs:yMcCgkdA-IM:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=FRg-n6O-TGs:yMcCgkdA-IM:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=FRg-n6O-TGs:yMcCgkdA-IM:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=FRg-n6O-TGs:yMcCgkdA-IM:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=FRg-n6O-TGs:yMcCgkdA-IM:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=FRg-n6O-TGs:yMcCgkdA-IM:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=FRg-n6O-TGs:yMcCgkdA-IM:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=FRg-n6O-TGs:yMcCgkdA-IM:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/FRg-n6O-TGs" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/02/ubuntu-one-where-do-i-look-what-do-i-do/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/02/ubuntu-one-where-do-i-look-what-do-i-do/</feedburner:origLink></item>
		<item>
		<title>Google+ Add To Circles Interaction: Some Good &amp; Not-So-Good UX</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/NVaiCt05ESA/</link>
		<comments>http://www.usabilityblog.com/2012/01/google-add-to-circles-interaction-some-good-not-so-good-ux/#comments</comments>
		<pubDate>Tue, 10 Jan 2012 14:12:58 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=904</guid>
		<description><![CDATA[Google+ Circle Interaction: Some Good &#38; Not-So-Good UX a video by pjsherman on Flickr. This is an impromptu video of me interacting with the Google+ &#8220;add people to circles&#8221; feature. Like most things we interact with in the world, there&#8217;s some good and some not-so-good to the experience. First, the good: 1. The people &#8220;cards&#8221; [...]]]></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%2F2012%2F01%2Fgoogle-add-to-circles-interaction-some-good-not-so-good-ux%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F01%2Fgoogle-add-to-circles-interaction-some-good-not-so-good-ux%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><object width="500" height="345" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="flashvars" value="intl_lang=en-us&amp;photo_secret=58774801e3&amp;photo_id=6673076143&amp;flickr_show_info_box=true" /><param name="allowFullScreen" value="true" /><param name="src" value="http://www.flickr.com/apps/video/stewart.swf?v=109786" /><param name="allowfullscreen" value="true" /><embed width="500" height="345" type="application/x-shockwave-flash" src="http://www.flickr.com/apps/video/stewart.swf?v=109786" flashvars="intl_lang=en-us&amp;photo_secret=58774801e3&amp;photo_id=6673076143&amp;flickr_show_info_box=true" allowFullScreen="true" allowfullscreen="true" /></object><br />
<span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/6673076143/">Google+ Circle Interaction: Some Good &amp; Not-So-Good UX</a> a video by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>This is an impromptu video of me interacting with the Google+ &#8220;add people to circles&#8221; feature.</p>
<p>Like most things we interact with in the world, there&#8217;s some good and some not-so-good to the experience.</p>
<p>First, the good:<br />
1. The people &#8220;cards&#8221; are just the right size. The picture is just right also &#8211; big enough so I can recognize the person, small enough to fit their name.<br />
2. It was also a smart idea to just show the target&#8217;s name (or email if the name is unavailable). It makes for easier and quicker scanning and target acquisition.<br />
3. The whole card is a click target.<br />
4. You can select multiple cards with clicks; no CMD+ or shift+click necessary. However, using a key combination (which some people will carry over from the desktop software interaction paradigm) works just fine as well.</p>
<p>The not-so-good:<br />
1. Drag and drop appears to be the only way to get people into circles. Really? Given Google&#8217;s demonstrated commitment to accessibility, I *can&#8217;t* believe this is the only way to manage circle assignment. I must be missing something. That just can&#8217;t be.<br />
2. A few times I highlighted multiple cards and then inadvertently deselected them. I have no idea why or how.<br />
3. Believe it or not, on first view I thought Google+ had only found 28 (7 x 4) people I knew. It took more time than it should&#8217;ve to realize that the card area was scrollable. I might not be able to pin that on Google however. I used Safari on Mac OS X 10.7, which together are a walking advertisement for iOS disappearing scrollbars.</p>
<p>So what does this little spiel demonstrate? I guess it shows that even cutting-edge design with massive resources behind it can still occasionally be a struggle for users. Oh, and don&#8217;t forget the accessibility.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=NVaiCt05ESA:yqdb6QN1AhI:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=NVaiCt05ESA:yqdb6QN1AhI:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=NVaiCt05ESA:yqdb6QN1AhI:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=NVaiCt05ESA:yqdb6QN1AhI:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=NVaiCt05ESA:yqdb6QN1AhI:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=NVaiCt05ESA:yqdb6QN1AhI:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=NVaiCt05ESA:yqdb6QN1AhI:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=NVaiCt05ESA:yqdb6QN1AhI:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/NVaiCt05ESA" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/01/google-add-to-circles-interaction-some-good-not-so-good-ux/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/01/google-add-to-circles-interaction-some-good-not-so-good-ux/</feedburner:origLink></item>
		<item>
		<title>I’ve Found It: The Worst Thermostat Ever</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/PPonSnUKN20/</link>
		<comments>http://www.usabilityblog.com/2012/01/ive-found-it-the-worth-thermostat-ever/#comments</comments>
		<pubDate>Wed, 04 Jan 2012 20:39:20 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>
		<category><![CDATA[Hardware]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2012/01/ive-found-it-the-worth-thermostat-ever/</guid>
		<description><![CDATA[I&#8217;ve Found It: The Worth Thermostat Ever, a photo by pjsherman on Flickr. After many years of working in user experience, I&#8217;ve found the semi-mythical holy grail of poor design: in my grandmother&#8217;s condo I encountered the dreaded &#8220;which way is which?&#8221; thermostat. Just looking at this picture, you might think that pressing the left-facing [...]]]></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%2F2012%2F01%2Five-found-it-the-worth-thermostat-ever%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2012%2F01%2Five-found-it-the-worth-thermostat-ever%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><a href="http://www.flickr.com/photos/paulsherman/6636795227/" title="I've Found It: The Worth Thermostat Ever"><img src="http://farm8.staticflickr.com/7018/6636795227_3707ae9387.jpg" alt="I've Found It: The Worth Thermostat Ever by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/6636795227/">I&#8217;ve Found It: The Worth Thermostat Ever</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>After many years of working in user experience, I&#8217;ve found the semi-mythical holy grail of poor design: in my grandmother&#8217;s condo I encountered the dreaded &#8220;which way is which?&#8221; thermostat. </p>
<p>Just looking at this picture, you might think that pressing the left-facing button would lower the temperature, and pressing the right-facing button would increase it. And you&#8217;d be wrong. At least, I think you&#8217;d be wrong. </p>
<p>If only they were reversed, I could at least deal with that&#8230;.but sadly no, what we have here is *both* a 90-degree control rotation (or negative 90; I&#8217;m not sure), and some kind of mode problem where I couldn&#8217;t actually just change the temperature on the fly without entering a &#8220;temperature change&#8221; state.</p>
<p>And no, I never discovered how to enter the &#8220;change temp&#8221; mode&#8230;I just sweltered in the Florida heat for the rest of the visit.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=PPonSnUKN20:WUB0tnEQRWY:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=PPonSnUKN20:WUB0tnEQRWY:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=PPonSnUKN20:WUB0tnEQRWY:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=PPonSnUKN20:WUB0tnEQRWY:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=PPonSnUKN20:WUB0tnEQRWY:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=PPonSnUKN20:WUB0tnEQRWY:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=PPonSnUKN20:WUB0tnEQRWY:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=PPonSnUKN20:WUB0tnEQRWY:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/PPonSnUKN20" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2012/01/ive-found-it-the-worth-thermostat-ever/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2012/01/ive-found-it-the-worth-thermostat-ever/</feedburner:origLink></item>
		<item>
		<title>When Requirements And Design Lose The Sale</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/QhZMNEUkppk/</link>
		<comments>http://www.usabilityblog.com/2011/12/when-requirements-and-design-lose-the-sale/#comments</comments>
		<pubDate>Fri, 30 Dec 2011 16:00:21 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=893</guid>
		<description><![CDATA[Here&#8217;s a great example of how feature requirements and design have combined to cause a lost sale. Some background: This is the donation page for the Presidential candidate I support. I&#8217;m not getting into who it is; those who know me personally can probably guess, and those readers who don&#8217;t can visit candidates&#8217; donation pages [...]]]></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%2F2011%2F12%2Fwhen-requirements-and-design-lose-the-sale%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F12%2Fwhen-requirements-and-design-lose-the-sale%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><a href="http://www.usabilityblog.com/2011/12/when-requirements-and-design-lose-the-sale/lostsale/" rel="attachment wp-att-894"><img class="size-full wp-image-894 aligncenter" title="Lost Sale" src="http://www.usabilityblog.com/wp-content/uploads/2011/12/LostSale.png" alt="Image of a donation form page with a thought bubble on it reading &quot;Yes, but...I only want to donate until this election cycle is over!&quot;" width="508" height="458" /></a></p>
<p>Here&#8217;s a great example of how feature requirements and design have combined to cause a lost sale. Some background: This is the donation page for the Presidential candidate I support. I&#8217;m not getting into who it is; those who know me personally can probably guess, and those readers who don&#8217;t can visit candidates&#8217; donation pages until they find this example.</p>
<p>I&#8217;m your typical semi-involved voter: I care a bit about local policitics, I try to vote in every election, but don&#8217;t always make the smaller or off-year ones. But I do care about state and national politics, and since I live in *the* quintessential swing state, I feel like my vote actually matters.</p>
<p>This morning I received a call-to-action email asking me to donate, and followed the link, landing at the page you see (in part). I noticed the &#8220;Make this a monthly recurring donation&#8221; checkbox, and immediately thought &#8220;Awesome! That&#8217;s what I want to do!&#8221; I figured it would be easier for me to just automagically kick in $25 per month until the general election was over. So I ticked the box, expecting to get one of those &#8220;For how many months?&#8221; dialog or AJAX partial page update. Nope. Nothing. Which sucks for the candidate and party, because I &#8211; and I suspect many, many other small donors &#8211; only want to make a recurring donation until the general election is over. And if I can&#8217;t do this &#8211; or easily figure out how to do this &#8211; there is no way I&#8217;m setting up an autopayment.</p>
<p>This is a classic failure of the product managers and designers to understand the customer. They may *want* me to set up an autopay in perpetuity. But I guarantee that most small, semi-involved donors most certainly do not want to do this.</p>
<p>Lesson: Learn what your customers want from your product and what their motivations are when they use it. Wishful thinking about user behavior is not a good way to meet their wants and needs.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=QhZMNEUkppk:rD23mxUCBig:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=QhZMNEUkppk:rD23mxUCBig:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=QhZMNEUkppk:rD23mxUCBig:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=QhZMNEUkppk:rD23mxUCBig:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=QhZMNEUkppk:rD23mxUCBig:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=QhZMNEUkppk:rD23mxUCBig:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=QhZMNEUkppk:rD23mxUCBig:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=QhZMNEUkppk:rD23mxUCBig:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/QhZMNEUkppk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/12/when-requirements-and-design-lose-the-sale/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/12/when-requirements-and-design-lose-the-sale/</feedburner:origLink></item>
		<item>
		<title>User Experience Design: A Mini-Festo</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/8UJlEkqV72E/</link>
		<comments>http://www.usabilityblog.com/2011/12/we-are-uxd-a-mini-festo/#comments</comments>
		<pubDate>Sat, 17 Dec 2011 20:19:16 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[Experience Strategy]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[UX And...]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=881</guid>
		<description><![CDATA[I&#8217;m on my way back from my company&#8217;s all-hands meeting. After all the excitement and motivation the week inspired, I felt moved to write a UX mini-manifesto. A mini-festo, if you will. Excuse any grammar or spelling issues; I&#8217;m composing in Evernote on my phone. I would love to hear my readers&#8217; and followers&#8217; comments on this post. You&#8217;re an experience design practitioner. In your organizations, you should be responsible for: Creating an [...]]]></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%2F2011%2F12%2Fwe-are-uxd-a-mini-festo%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F12%2Fwe-are-uxd-a-mini-festo%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>I&#8217;m on my way back from my company&#8217;s all-hands meeting.</p>
<p>After all the excitement and motivation the week inspired, I felt moved to write a UX mini-manifesto. A mini-festo, if you will.</p>
<p>Excuse any grammar or spelling issues; I&#8217;m composing in Evernote on my phone. I would love to hear my readers&#8217; and followers&#8217; comments on this post.</p>
<p>You&#8217;re an experience design practitioner. In your organizations, you should be responsible for:</p>
<ul>
<li>Creating an inviting and well-designed initial user experience.</li>
<li>Designing and validating:</li>
</ul>
<div>
<ol>
<li>Terminology and conceptual models that reflect our target user&#8217; ways of thinking.</li>
<li>Usable workflow and navigation.</li>
<li>Clear, understandable and actionable page and view design. (I&#8217;m defining &#8221;view&#8221; as an</li>
<li>element of a page that conveys pieces of information to the user, such as a data display</li>
<li>element).</li>
</ol>
<div>
<ul>
<li>Employing consistent visual design and use of design patterns.</li>
<li>Creating and maintaining access to and connection with the broader user experience components, e.g. community resources, documentation, etc.</li>
<li>Remaining consistent with brand.</li>
</ul>
</div>
</div>
<p>Along the way, you also:</p>
<ul>
<li>Collaborate on the definition and optimization of product development lifecycle processes with our functional neighbors &#8211; i.e. PM, Dev, QA, Marketing, and Social/Community Management.</li>
<li>Measure, track and improve the user experience.</li>
<li>Discover opportunities to delight customers in ways that are not easily discoverable by market-level research methods.</li>
<li>Occasionally uncover strategic jobs that customers need doing, and design opportunities for more sustaining vs. incremental product innovations.</li>
<li>Provide the business with both strategic and tactical customer insights and understanding.</li>
</ul>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=8UJlEkqV72E:Q7hifDbdzwg:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=8UJlEkqV72E:Q7hifDbdzwg:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=8UJlEkqV72E:Q7hifDbdzwg:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=8UJlEkqV72E:Q7hifDbdzwg:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=8UJlEkqV72E:Q7hifDbdzwg:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=8UJlEkqV72E:Q7hifDbdzwg:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=8UJlEkqV72E:Q7hifDbdzwg:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=8UJlEkqV72E:Q7hifDbdzwg:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/8UJlEkqV72E" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/12/we-are-uxd-a-mini-festo/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/12/we-are-uxd-a-mini-festo/</feedburner:origLink></item>
		<item>
		<title>eBay: Hah Hah, Made You Think!</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/mK7qbaO50yg/</link>
		<comments>http://www.usabilityblog.com/2011/09/ebay-hah-hah-made-you-think/#comments</comments>
		<pubDate>Wed, 28 Sep 2011 13:43:57 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/09/ebay-hah-hah-made-you-think/</guid>
		<description><![CDATA[eBay: Hah Hah, Made You Think!, a photo by pjsherman on Flickr. Standard disclaimer: I am a user and fan of eBay. When it comes to user experience, they do lots of things right. Here&#8217;s one thing they did wrong: They provided half-hearted, linkless &#8220;help&#8221; in the form of &#8220;to do x, go to [place [...]]]></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%2F2011%2F09%2Febay-hah-hah-made-you-think%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F09%2Febay-hah-hah-made-you-think%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><a href="http://www.flickr.com/photos/paulsherman/6191637495/" title="eBay: Hah Hah, Made You Think!"><img src="http://farm7.static.flickr.com/6152/6191637495_5b6a105583.jpg" alt="eBay: Hah Hah, Made You Think! by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/6191637495/">eBay: Hah Hah, Made You Think!</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>Standard disclaimer: I am a user and fan of eBay. When it comes to user experience, they do lots of things right. </p>
<p>Here&#8217;s one thing they did wrong: They provided  half-hearted, linkless &#8220;help&#8221; in the form of &#8220;to do x, go to [place A] or [place B]&#8220;, without including links to those locations. This is a no-brainer and should&#8217;ve been coded ages ago. </p>
<p>As a result, I had to hunt around for a small but still-annoying period of time before I found where I needed to go. </p>
<p>Somebody add that to the eBay UX fix list.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=mK7qbaO50yg:Jq_Oz4SWORM:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=mK7qbaO50yg:Jq_Oz4SWORM:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=mK7qbaO50yg:Jq_Oz4SWORM:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=mK7qbaO50yg:Jq_Oz4SWORM:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=mK7qbaO50yg:Jq_Oz4SWORM:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=mK7qbaO50yg:Jq_Oz4SWORM:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=mK7qbaO50yg:Jq_Oz4SWORM:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=mK7qbaO50yg:Jq_Oz4SWORM:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/mK7qbaO50yg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/09/ebay-hah-hah-made-you-think/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/09/ebay-hah-hah-made-you-think/</feedburner:origLink></item>
		<item>
		<title>Message Can’t Be Blank? Why The Hell Not?</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/9Ke19FgmiU0/</link>
		<comments>http://www.usabilityblog.com/2011/09/message-cant-be-blank-why-the-hell-not/#comments</comments>
		<pubDate>Sun, 25 Sep 2011 14:27:37 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/09/message-cant-be-blank-why-the-hell-not/</guid>
		<description><![CDATA[Message Can&#8217;t Be Blank? Why The Hell Not?, a photo by pjsherman on Flickr. This screenshot is about a year old, so my apologies to the site if they&#8217;ve fixed this UX issue. The point remains, however, that when someone wishes to unsubscribe from your email list, it is incredibly imperious to *require* them to [...]]]></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%2F2011%2F09%2Fmessage-cant-be-blank-why-the-hell-not%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F09%2Fmessage-cant-be-blank-why-the-hell-not%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><a href="http://www.flickr.com/photos/paulsherman/6180938545/" title="Message Can't Be Blank? Why The Hell Not?"><img src="http://farm7.static.flickr.com/6165/6180938545_bedf7d409c.jpg" alt="Message Can't Be Blank? Why The Hell Not? by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/6180938545/">Message Can&#8217;t Be Blank? Why The Hell Not?</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>This screenshot is about a year old, so my apologies to the site if they&#8217;ve fixed this UX issue. </p>
<p>The point remains, however, that when someone wishes to unsubscribe from your email list, it is incredibly imperious to *require* them to explain why. </p>
<p>Sure, as a business you might *like* to know, but you have no right to demand an answer. </p>
<p>That&#8217;s treating your visitor rudely.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=9Ke19FgmiU0:30BOZv_-KtE:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=9Ke19FgmiU0:30BOZv_-KtE:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=9Ke19FgmiU0:30BOZv_-KtE:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=9Ke19FgmiU0:30BOZv_-KtE:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=9Ke19FgmiU0:30BOZv_-KtE:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=9Ke19FgmiU0:30BOZv_-KtE:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=9Ke19FgmiU0:30BOZv_-KtE:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=9Ke19FgmiU0:30BOZv_-KtE:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/9Ke19FgmiU0" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/09/message-cant-be-blank-why-the-hell-not/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/09/message-cant-be-blank-why-the-hell-not/</feedburner:origLink></item>
		<item>
		<title>A Dubious Claim</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/xJ-VcPpFoRs/</link>
		<comments>http://www.usabilityblog.com/2011/09/a-dubious-claim/#comments</comments>
		<pubDate>Thu, 22 Sep 2011 17:09:34 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/09/a-dubious-claim/</guid>
		<description><![CDATA[A Dubious Claim, a photo by pjsherman on Flickr. Paypal goes a little too far with this login transition screen. &#8220;The world&#8217;s most loved way to pay and get paid&#8221;? I don&#8217;t think so. Using marketing-speak in the UI is one thing. It&#8217;s come to be expected and (mostly) accepted. Just make sure it doesn&#8217;t [...]]]></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%2F2011%2F09%2Fa-dubious-claim%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F09%2Fa-dubious-claim%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><a href="http://www.flickr.com/photos/paulsherman/6172304883/" title="A Dubious Claim"><img src="http://farm7.static.flickr.com/6158/6172304883_cbca45466d.jpg" alt="A Dubious Claim by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/6172304883/">A Dubious Claim</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>Paypal goes a little too far with this login transition screen. </p>
<p>&#8220;The world&#8217;s most loved way to pay and get paid&#8221;?</p>
<p>I don&#8217;t think so. </p>
<p>Using marketing-speak in the UI is one thing. It&#8217;s come to be expected and (mostly) accepted. Just make sure it doesn&#8217;t trigger your users&#8217; BS detectors.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=xJ-VcPpFoRs:vU-3LTG5rHI:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=xJ-VcPpFoRs:vU-3LTG5rHI:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=xJ-VcPpFoRs:vU-3LTG5rHI:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=xJ-VcPpFoRs:vU-3LTG5rHI:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=xJ-VcPpFoRs:vU-3LTG5rHI:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=xJ-VcPpFoRs:vU-3LTG5rHI:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=xJ-VcPpFoRs:vU-3LTG5rHI:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=xJ-VcPpFoRs:vU-3LTG5rHI:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/xJ-VcPpFoRs" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/09/a-dubious-claim/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/09/a-dubious-claim/</feedburner:origLink></item>
		<item>
		<title>Whatever You Do…Don’t Search For “ASCII Mr. Burns” Or Google Will Flip Out</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/VTtjY2QgguA/</link>
		<comments>http://www.usabilityblog.com/2011/09/whatever-you-do-dont-search-for-ascii-mr-burns-or-google-will-flip-out/#comments</comments>
		<pubDate>Mon, 12 Sep 2011 17:30:44 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/09/whatever-you-do-dont-search-for-ascii-mr-burns-or-google-will-flip-out/</guid>
		<description><![CDATA[Whatever You Do&#8230;Don&#8217;t Search For &#8220;ASCII Mr. Burns&#8221; Or Google Will Flip Out, a photo by pjsherman on Flickr. Really Google? I&#8217;m on my home network. No one else is using my connection, according to my outbound connection monitoring software. Nothing but little ol&#8217; me on Firefox.]]></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%2F2011%2F09%2Fwhatever-you-do-dont-search-for-ascii-mr-burns-or-google-will-flip-out%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F09%2Fwhatever-you-do-dont-search-for-ascii-mr-burns-or-google-will-flip-out%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><a title="Whatever You Do...Don't Search For &quot;ASCII Mr. Burns&quot; Or Google Will Flip Out" href="http://www.flickr.com/photos/paulsherman/6141153298/"><img src="http://farm7.static.flickr.com/6155/6141153298_bf41a4a387.jpg" alt="Whatever You Do...Don't Search For &quot;ASCII Mr. Burns&quot; Or Google Will Flip Out by pjsherman" /></a><br />
<span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/6141153298/">Whatever You Do&#8230;Don&#8217;t Search For &#8220;ASCII Mr. Burns&#8221; Or Google Will Flip Out</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>Really Google? I&#8217;m on my home network. No one else is using my connection, according to my outbound connection monitoring software.</p>
<p>Nothing but little ol&#8217; me on Firefox.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=VTtjY2QgguA:vJCBDBMZSks:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=VTtjY2QgguA:vJCBDBMZSks:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=VTtjY2QgguA:vJCBDBMZSks:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=VTtjY2QgguA:vJCBDBMZSks:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=VTtjY2QgguA:vJCBDBMZSks:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=VTtjY2QgguA:vJCBDBMZSks:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=VTtjY2QgguA:vJCBDBMZSks:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=VTtjY2QgguA:vJCBDBMZSks:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/VTtjY2QgguA" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/09/whatever-you-do-dont-search-for-ascii-mr-burns-or-google-will-flip-out/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/09/whatever-you-do-dont-search-for-ascii-mr-burns-or-google-will-flip-out/</feedburner:origLink></item>
		<item>
		<title>One-Try Lockout? That’s BS.</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/mj5BXfmaENU/</link>
		<comments>http://www.usabilityblog.com/2011/09/one-try-lockout-thats-bs/#comments</comments>
		<pubDate>Mon, 12 Sep 2011 12:45:46 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/09/one-try-lockout-thats-bs/</guid>
		<description><![CDATA[One-Try Lockout? That&#8217;s BS., a photo by pjsherman on Flickr. This is a pure customer experience issue: I was just locked out of my AT&#038;T wireless account after a SINGLE INCORRECT PASSWORD ENTRY. I suppose it&#8217;s theoretically feasible that someone was trying to crack my account at the very moment I was trying to legitimately [...]]]></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%2F2011%2F09%2Fone-try-lockout-thats-bs%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F09%2Fone-try-lockout-thats-bs%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><a href="http://www.flickr.com/photos/paulsherman/6140290490/" title="One-Try Lockout? That's BS."><img src="http://farm7.static.flickr.com/6174/6140290490_556112ee30.jpg" alt="One-Try Lockout? That's BS. by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/6140290490/">One-Try Lockout? That&#8217;s BS.</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>This is a pure customer experience issue: I was just locked out of my AT&#038;T wireless account after a SINGLE INCORRECT PASSWORD ENTRY. </p>
<p>I suppose it&#8217;s theoretically feasible that someone was trying to crack my account at the very  moment I was trying to legitimately log in, which would explain why I was locked out after a single try. Odds are, probably not. </p>
<p>Thanks the inconvenience, AT&#038;T. </p>
<p>And companies wonder why we call instead of self-service on the web. It&#8217;s because the web is basically a brittle support mechanism. </p>
<p>Given that the average support call costs anywhere between 5 and 50 dollars (sorry, no recent reference; going from memory), I&#8217;m about to cost AT&#038;T ~ 15 or 20 bucks because someone decided to implement a single-attempt lockout policy. </p>
<p>Whatever. Time to call a CSR and burn some of AT&#038;T&#8217;s cash.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=mj5BXfmaENU:37E2aZGX9Ys:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=mj5BXfmaENU:37E2aZGX9Ys:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=mj5BXfmaENU:37E2aZGX9Ys:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=mj5BXfmaENU:37E2aZGX9Ys:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=mj5BXfmaENU:37E2aZGX9Ys:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=mj5BXfmaENU:37E2aZGX9Ys:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=mj5BXfmaENU:37E2aZGX9Ys:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=mj5BXfmaENU:37E2aZGX9Ys:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/mj5BXfmaENU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/09/one-try-lockout-thats-bs/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/09/one-try-lockout-thats-bs/</feedburner:origLink></item>
		<item>
		<title>RushLimbaugh.com…Wait For It…Not Enough White Space</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/vAvYxByvgDg/</link>
		<comments>http://www.usabilityblog.com/2011/09/rushlimbaugh-com-wait-for-it-not-enough-white-space/#comments</comments>
		<pubDate>Fri, 09 Sep 2011 13:40:39 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/09/rushlimbaugh-com-wait-for-it-not-enough-white-space/</guid>
		<description><![CDATA[RushLimbaugh.com&#8230;Wait For It&#8230;Not Enough White Space, a photo by pjsherman on Flickr. This morning I followed a link from an independent writer&#8217;s feed, and found myself for the first time on Rush Limbaugh&#8217;s site. I don&#8217;t like the guy or what he stands for. He&#8217;s a liar and a bully. But let&#8217;s get beyond that [...]]]></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%2F2011%2F09%2Frushlimbaugh-com-wait-for-it-not-enough-white-space%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F09%2Frushlimbaugh-com-wait-for-it-not-enough-white-space%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><a href="http://www.flickr.com/photos/paulsherman/6130217952/" title="RushLimbaugh.com...Wait For It...Not Enough White Space"><img src="http://farm7.static.flickr.com/6063/6130217952_56716bd8a1.jpg" alt="RushLimbaugh.com...Wait For It...Not Enough White Space by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/6130217952/">RushLimbaugh.com&#8230;Wait For It&#8230;Not Enough White Space</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>This morning I followed a link from an independent writer&#8217;s feed, and found myself for the first time on Rush Limbaugh&#8217;s site. </p>
<p>I don&#8217;t like the guy or what he stands for. He&#8217;s a liar and a bully. But let&#8217;s get beyond that and talk about his site. </p>
<p>Clearly there&#8217;s too much&#8230;stuff. Multiple rows of nav, a riot of highly saturated opposing colors (ouch my eyes), and&#8230;not enough white space between elements. </p>
<p>Maybe he did that on purpose. That would be so meta and clever if he meant that. Get it? Not enough white space? Because, uh, that&#8217;s what he believes&#8230;there&#8217;s not enough white space. </p>
<p>Yeah&#8230;somehow I doubt it was intentional.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=vAvYxByvgDg:KGqKXJSyt4Y:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=vAvYxByvgDg:KGqKXJSyt4Y:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=vAvYxByvgDg:KGqKXJSyt4Y:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=vAvYxByvgDg:KGqKXJSyt4Y:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=vAvYxByvgDg:KGqKXJSyt4Y:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=vAvYxByvgDg:KGqKXJSyt4Y:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=vAvYxByvgDg:KGqKXJSyt4Y:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=vAvYxByvgDg:KGqKXJSyt4Y:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/vAvYxByvgDg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/09/rushlimbaugh-com-wait-for-it-not-enough-white-space/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/09/rushlimbaugh-com-wait-for-it-not-enough-white-space/</feedburner:origLink></item>
		<item>
		<title>There’s A Lot Of User Assistance In That There Screen</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/aC_SjHaF1ew/</link>
		<comments>http://www.usabilityblog.com/2011/09/theres-a-lot-of-user-assistance-in-that-there-screen/#comments</comments>
		<pubDate>Tue, 06 Sep 2011 19:21:25 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/09/theres-a-lot-of-user-assistance-in-that-there-screen/</guid>
		<description><![CDATA[There&#8217;s A Lot Of User Assistance In That There Screen, a photo by pjsherman on Flickr. My company uses this product to (surprise!) document our expense reports. When I started a few months back, one of the first emails I received from my colleagues was the &#8220;Here&#8217;s how you create an Expensify report&#8221; message. It [...]]]></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%2F2011%2F09%2Ftheres-a-lot-of-user-assistance-in-that-there-screen%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F09%2Ftheres-a-lot-of-user-assistance-in-that-there-screen%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><a href="http://www.flickr.com/photos/paulsherman/6121449384/" title="There's A Lot Of User Assistance In That There Screen"><img src="http://farm7.static.flickr.com/6192/6121449384_c567a184ec.jpg" alt="There's A Lot Of User Assistance In That There Screen by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/6121449384/">There&#8217;s A Lot Of User Assistance In That There Screen</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>My company uses this product to (surprise!) document our expense reports. When I started a few months back, one of the first emails I received from my colleagues was the &#8220;Here&#8217;s how you create an Expensify report&#8221; message. It was that hard. </p>
<p>Last time I logged in I noticed a whole bunch of user assistance in the UI, including a &#8220;faux-modal&#8221; lightbox that provides links to the two most common actions (&#8220;add expenses&#8221; and &#8220;new expense&#8221;). They&#8217;re not the most well-crafted sentences in the world, but they get the points across. </p>
<p>Because I was in a user-assistance-y mood, I also noticed the &#8220;How do I?&#8221; links on the left for the first time. I have no idea whether they&#8217;ve been there since I started using the app, or whether they were new as well. </p>
<p>In any case, while Expensify&#8217;s main workflow isn&#8217;t exactly the most well-designed interaction I&#8217;ve seen, at least they&#8217;re providing a bit of guidance at the front end.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=aC_SjHaF1ew:ahhiiwNlx_g:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=aC_SjHaF1ew:ahhiiwNlx_g:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=aC_SjHaF1ew:ahhiiwNlx_g:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=aC_SjHaF1ew:ahhiiwNlx_g:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=aC_SjHaF1ew:ahhiiwNlx_g:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=aC_SjHaF1ew:ahhiiwNlx_g:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=aC_SjHaF1ew:ahhiiwNlx_g:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=aC_SjHaF1ew:ahhiiwNlx_g:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/aC_SjHaF1ew" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/09/theres-a-lot-of-user-assistance-in-that-there-screen/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/09/theres-a-lot-of-user-assistance-in-that-there-screen/</feedburner:origLink></item>
		<item>
		<title>UX Jobs Guide Infographic</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/UPYsr83OdcY/</link>
		<comments>http://www.usabilityblog.com/2011/09/ux-jobs-guide-infographic/#comments</comments>
		<pubDate>Tue, 06 Sep 2011 15:12:29 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Organizational]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=865</guid>
		<description><![CDATA[A reader sent me a link to this infographic about user experience jobs. Although I disagree with a few items in the skillsets and tools section, I found it useful enough to pass on. Yes, her organization is a UX recruiting firm, but that there constitutes disclosure, and the fact that I&#8217;m receiving nothing from [...]]]></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%2F2011%2F09%2Fux-jobs-guide-infographic%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F09%2Fux-jobs-guide-infographic%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>A reader sent me a link to this infographic about user experience jobs. Although I disagree with a few items in the skillsets and tools section, I found it useful enough to pass on. </p>
<p>Yes, her organization is a <a href="http://www.onwardsearch.com ">UX recruiting firm</a>, but that there constitutes disclosure, and the fact that I&#8217;m receiving nothing from them by posting this constitutes full disclosure. </p>
<p>I don&#8217;t know exactly why I&#8217;m getting all journalistic about this, so without further ado here&#8217;s a screenshot and link to the graphic. Enjoy. </p>
<p><a href="http://www.onwardsearch.com/UX-Career-Guide/" target="_blank"><img src="http://www.onwardsearch.com/UX-Career-Guide/UX-Career-Guide-Infographic.png" alt="UX Career Guide" width="585" height="2181" border="0"/></a></p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=UPYsr83OdcY:VXiZi-4wIzw:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=UPYsr83OdcY:VXiZi-4wIzw:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=UPYsr83OdcY:VXiZi-4wIzw:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=UPYsr83OdcY:VXiZi-4wIzw:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=UPYsr83OdcY:VXiZi-4wIzw:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=UPYsr83OdcY:VXiZi-4wIzw:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=UPYsr83OdcY:VXiZi-4wIzw:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=UPYsr83OdcY:VXiZi-4wIzw:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/UPYsr83OdcY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/09/ux-jobs-guide-infographic/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/09/ux-jobs-guide-infographic/</feedburner:origLink></item>
		<item>
		<title>Classy Fridge Infographic</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/wb92nZMZUZE/</link>
		<comments>http://www.usabilityblog.com/2011/08/classy-fridge-infographic/#comments</comments>
		<pubDate>Thu, 18 Aug 2011 15:39:35 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/08/classy-fridge-infographic/</guid>
		<description><![CDATA[Classy Fridge Infographic, a photo by pjsherman on Flickr. I just like this infrographic from our refrigerator. There&#8217;s something classy about the dress shirt cuff and suit sleeve. Also note the grey circles that call attention to the different ice cube maker switch states. Not sure I get the warning though. &#8220;Ejector fingers&#8221;&#8230;.riiiight&#8230;]]></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%2F2011%2F08%2Fclassy-fridge-infographic%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F08%2Fclassy-fridge-infographic%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><a href="http://www.flickr.com/photos/paulsherman/4732112094/" title="Classy Fridge Infographic"><img src="http://farm2.static.flickr.com/1152/4732112094_6915cca6b7.jpg" alt="Classy Fridge Infographic by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/4732112094/">Classy Fridge Infographic</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>I just like this infrographic from our refrigerator. There&#8217;s something classy about the dress shirt cuff and suit sleeve. Also note the grey circles that call attention to the different ice cube maker switch states.</p>
<p>Not sure I get the warning though. &#8220;Ejector fingers&#8221;&#8230;.riiiight&#8230;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=wb92nZMZUZE:RG3NCZn_oVs:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=wb92nZMZUZE:RG3NCZn_oVs:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=wb92nZMZUZE:RG3NCZn_oVs:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=wb92nZMZUZE:RG3NCZn_oVs:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=wb92nZMZUZE:RG3NCZn_oVs:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=wb92nZMZUZE:RG3NCZn_oVs:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=wb92nZMZUZE:RG3NCZn_oVs:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=wb92nZMZUZE:RG3NCZn_oVs:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/wb92nZMZUZE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/08/classy-fridge-infographic/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/08/classy-fridge-infographic/</feedburner:origLink></item>
		<item>
		<title>Expensify Makes You Feel Good About A Password Reset</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/sPlB-i9SDT4/</link>
		<comments>http://www.usabilityblog.com/2011/08/expensify-makes-you-feel-good-about-a-password-reset/#comments</comments>
		<pubDate>Mon, 08 Aug 2011 15:43:53 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/08/expensify-makes-you-feel-good-about-a-password-reset/</guid>
		<description><![CDATA[Expensify Makes You Feel Good About A Password Reset, a photo by pjsherman on Flickr. And this, folks, is how you put your customers at ease and make them feel better about interacting with your web app. Lesson: If you have an opportunity to a) make your customers not feel stupid, and b) make it [...]]]></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%2F2011%2F08%2Fexpensify-makes-you-feel-good-about-a-password-reset%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F08%2Fexpensify-makes-you-feel-good-about-a-password-reset%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><a href="http://www.flickr.com/photos/paulsherman/6021886585/" title="Expensify Makes You Feel Good About A Password Reset"><img src="http://farm7.static.flickr.com/6187/6021886585_c935cd042c.jpg" alt="Expensify Makes You Feel Good About A Password Reset by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/6021886585/">Expensify Makes You Feel Good About A Password Reset</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>And this, folks, is how you put your customers at ease and make them feel better about interacting with your web app.</p>
<p>Lesson: If you have an opportunity to a) make your customers not feel stupid, and b) make it easy to fix a mistake, do it.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=sPlB-i9SDT4:9PC6kEcEqY8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=sPlB-i9SDT4:9PC6kEcEqY8:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=sPlB-i9SDT4:9PC6kEcEqY8:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=sPlB-i9SDT4:9PC6kEcEqY8:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=sPlB-i9SDT4:9PC6kEcEqY8:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=sPlB-i9SDT4:9PC6kEcEqY8:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=sPlB-i9SDT4:9PC6kEcEqY8:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=sPlB-i9SDT4:9PC6kEcEqY8:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/sPlB-i9SDT4" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/08/expensify-makes-you-feel-good-about-a-password-reset/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/08/expensify-makes-you-feel-good-about-a-password-reset/</feedburner:origLink></item>
		<item>
		<title>NYT Regwall = Bad User Experience</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/x8_6YWXt6lQ/</link>
		<comments>http://www.usabilityblog.com/2011/08/nyt-regwall-bad-user-experience/#comments</comments>
		<pubDate>Thu, 04 Aug 2011 16:50:05 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/08/nyt-regwall-bad-user-experience/</guid>
		<description><![CDATA[NYT Joinwall = Bad User Experience, a photo by pjsherman on Flickr. I&#8217;d love to get a peek at the New York Times&#8217; server logs and see just how many thousands of bounces this page generates every day. Understand, it&#8217;s not a bad interaction design. It&#8217;s a fundamental misunderstanding of how to treat visitors. In [...]]]></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%2F2011%2F08%2Fnyt-regwall-bad-user-experience%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F08%2Fnyt-regwall-bad-user-experience%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><a href="http://www.flickr.com/photos/paulsherman/4945470440/" title="NYT Joinwall = Bad User Experience"><img src="http://farm5.static.flickr.com/4141/4945470440_a986201a48.jpg" alt="NYT Joinwall = Bad User Experience by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/4945470440/">NYT Joinwall = Bad User Experience</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>I&#8217;d love to get a peek at the New York Times&#8217; server logs and see just how many thousands of bounces this page generates every day. </p>
<p>Understand, it&#8217;s not a bad interaction design. It&#8217;s a fundamental misunderstanding of how to treat visitors. </p>
<p>In other words, the NYT is shooting itself in the foot and driving away visitors in droves.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=x8_6YWXt6lQ:qns63J9KFfs:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=x8_6YWXt6lQ:qns63J9KFfs:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=x8_6YWXt6lQ:qns63J9KFfs:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=x8_6YWXt6lQ:qns63J9KFfs:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=x8_6YWXt6lQ:qns63J9KFfs:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=x8_6YWXt6lQ:qns63J9KFfs:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=x8_6YWXt6lQ:qns63J9KFfs:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=x8_6YWXt6lQ:qns63J9KFfs:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/x8_6YWXt6lQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/08/nyt-regwall-bad-user-experience/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/08/nyt-regwall-bad-user-experience/</feedburner:origLink></item>
		<item>
		<title>How Not To Incorporate Graphs In Your Blog Post</title>
		<link>http://feedproxy.google.com/~r/usabilityblog/FPcP/~3/Aw4EC5lX8DE/</link>
		<comments>http://www.usabilityblog.com/2011/08/how-not-to-incorporate-graphs-in-your-blog-post/#comments</comments>
		<pubDate>Wed, 03 Aug 2011 17:55:04 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/08/how-not-to-incorporate-graphs-in-your-blog-post/</guid>
		<description><![CDATA[How Not To Incorporate Graphs In Your Blog Post, a photo by pjsherman on Flickr. Finding myself working in the info security world, I have little doubt that the content of this article is spot-on. The problems lay with the graphs embedded in the article: 1. The graphs are unreadable at the embedded resolution. 2. [...]]]></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%2F2011%2F08%2Fhow-not-to-incorporate-graphs-in-your-blog-post%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F08%2Fhow-not-to-incorporate-graphs-in-your-blog-post%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<div style="margin: 0 0 10px 0; padding: 0; font-size: 0.8em; line-height: 1.6em;"><a title="How Not To Incorporate Graphs In Your Blog Post" href="http://www.flickr.com/photos/paulsherman/6005538995/"><img src="http://farm7.static.flickr.com/6143/6005538995_5900062a9b.jpg" alt="How Not To Incorporate Graphs In Your Blog Post by pjsherman" /></a><br />
<span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/6005538995/">How Not To Incorporate Graphs In Your Blog Post</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>Finding myself working in the info security world, I have little doubt that <a href="http://blogs.mcafee.com/mcafee-labs/revealed-operation-shady-rat">the content of this article</a> is spot-on.</p>
<p>The problems lay with the graphs embedded in the article:</p>
<p>1. The graphs are unreadable at the embedded resolution.</p>
<p>2. It&#8217;s not immediately clear that you can click to embiggen them. You merely *hope* that you get the hand cursor when you roll over the images.</p>
<p>3. When you do click the image, you&#8217;ve lost context. Even a simple title or line or two of text recapping the post content prior to the image would help maintain continuity and context.</p>
<p>On the plus side, at least the embiggened image is not the same size as the thumbnail, which is probably in most people&#8217;s list of top 10 annoying web design flaws.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=Aw4EC5lX8DE:po6FWEwZRYk:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=Aw4EC5lX8DE:po6FWEwZRYk:UHM0dnFdquY"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=Aw4EC5lX8DE:po6FWEwZRYk:UHM0dnFdquY" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=Aw4EC5lX8DE:po6FWEwZRYk:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=Aw4EC5lX8DE:po6FWEwZRYk:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=Aw4EC5lX8DE:po6FWEwZRYk:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?i=Aw4EC5lX8DE:po6FWEwZRYk:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?a=Aw4EC5lX8DE:po6FWEwZRYk:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/usabilityblog/FPcP?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/usabilityblog/FPcP/~4/Aw4EC5lX8DE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/08/how-not-to-incorporate-graphs-in-your-blog-post/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://www.usabilityblog.com/2011/08/how-not-to-incorporate-graphs-in-your-blog-post/</feedburner:origLink></item>
	</channel>
</rss><!-- Dynamic page generated in 1.096 seconds. --><!-- Cached page generated by WP-Super-Cache on 2013-03-25 09:39:06 -->
