<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>UsabilityBlog</title>
	<atom:link href="http://www.usabilityblog.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.usabilityblog.com</link>
	<description>Blogging about usability, user experience and design</description>
	<lastBuildDate>Wed, 08 Feb 2012 13:40:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Need A New Site To Feel All Superior To? Check This.</title>
		<link>http://www.usabilityblog.com/2012/02/need-a-new-site-to-feel-all-superior-to-check-this/</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>
]]></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>
		</item>
		<item>
		<title>Ubuntu One: Where Do I Look? What Do I Do?</title>
		<link>http://www.usabilityblog.com/2012/02/ubuntu-one-where-do-i-look-what-do-i-do/</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>
]]></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>
		</item>
		<item>
		<title>Google+ Add To Circles Interaction: Some Good &amp; Not-So-Good UX</title>
		<link>http://www.usabilityblog.com/2012/01/google-add-to-circles-interaction-some-good-not-so-good-ux/</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>
]]></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>
		</item>
		<item>
		<title>I&#8217;ve Found It: The Worst Thermostat Ever</title>
		<link>http://www.usabilityblog.com/2012/01/ive-found-it-the-worth-thermostat-ever/</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>
]]></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>
		</item>
		<item>
		<title>When Requirements And Design Lose The Sale</title>
		<link>http://www.usabilityblog.com/2011/12/when-requirements-and-design-lose-the-sale/</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>
]]></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>
		</item>
		<item>
		<title>User Experience Design: A Mini-Festo</title>
		<link>http://www.usabilityblog.com/2011/12/we-are-uxd-a-mini-festo/</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>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/12/we-are-uxd-a-mini-festo/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>eBay: Hah Hah, Made You Think!</title>
		<link>http://www.usabilityblog.com/2011/09/ebay-hah-hah-made-you-think/</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>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/09/ebay-hah-hah-made-you-think/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Message Can&#8217;t Be Blank? Why The Hell Not?</title>
		<link>http://www.usabilityblog.com/2011/09/message-cant-be-blank-why-the-hell-not/</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>
]]></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>
		</item>
		<item>
		<title>A Dubious Claim</title>
		<link>http://www.usabilityblog.com/2011/09/a-dubious-claim/</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>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/09/a-dubious-claim/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Whatever You Do&#8230;Don&#8217;t Search For &#8220;ASCII Mr. Burns&#8221; Or Google Will Flip Out</title>
		<link>http://www.usabilityblog.com/2011/09/whatever-you-do-dont-search-for-ascii-mr-burns-or-google-will-flip-out/</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>
]]></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>
		</item>
		<item>
		<title>One-Try Lockout? That&#8217;s BS.</title>
		<link>http://www.usabilityblog.com/2011/09/one-try-lockout-thats-bs/</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>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/09/one-try-lockout-thats-bs/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RushLimbaugh.com&#8230;Wait For It&#8230;Not Enough White Space</title>
		<link>http://www.usabilityblog.com/2011/09/rushlimbaugh-com-wait-for-it-not-enough-white-space/</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>
]]></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>
		</item>
		<item>
		<title>There&#8217;s A Lot Of User Assistance In That There Screen</title>
		<link>http://www.usabilityblog.com/2011/09/theres-a-lot-of-user-assistance-in-that-there-screen/</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>
]]></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>
		</item>
		<item>
		<title>UX Jobs Guide Infographic</title>
		<link>http://www.usabilityblog.com/2011/09/ux-jobs-guide-infographic/</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>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/09/ux-jobs-guide-infographic/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Classy Fridge Infographic</title>
		<link>http://www.usabilityblog.com/2011/08/classy-fridge-infographic/</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>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/08/classy-fridge-infographic/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Expensify Makes You Feel Good About A Password Reset</title>
		<link>http://www.usabilityblog.com/2011/08/expensify-makes-you-feel-good-about-a-password-reset/</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>
]]></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>
		</item>
		<item>
		<title>NYT Regwall = Bad User Experience</title>
		<link>http://www.usabilityblog.com/2011/08/nyt-regwall-bad-user-experience/</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>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/08/nyt-regwall-bad-user-experience/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>How Not To Incorporate Graphs In Your Blog Post</title>
		<link>http://www.usabilityblog.com/2011/08/how-not-to-incorporate-graphs-in-your-blog-post/</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>
]]></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>
		</item>
		<item>
		<title>Yes, There&#8217;s Room For Funny In The UI</title>
		<link>http://www.usabilityblog.com/2011/07/yes-theres-room-for-funny-in-the-ui/</link>
		<comments>http://www.usabilityblog.com/2011/07/yes-theres-room-for-funny-in-the-ui/#comments</comments>
		<pubDate>Thu, 28 Jul 2011 15:10:28 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/07/yes-theres-room-for-funny-in-the-ui/</guid>
		<description><![CDATA[Yes, There&#8217;s Room For Funny, a photo by pjsherman on Flickr. If your brand and on-web persona fit the attempt at humor, that is. This little piece of fun is from Woot, who pretty much define funny in the e-commerce space. In this case, I was amused enough to get that little brand affinity glow. [...]]]></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%2F07%2Fyes-theres-room-for-funny-in-the-ui%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F07%2Fyes-theres-room-for-funny-in-the-ui%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/5984306331/" title="Yes, There's Room For Funny"><img src="http://farm7.static.flickr.com/6018/5984306331_e4dc75d37c.jpg" alt="Yes, There's Room For Funny by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/5984306331/">Yes, There&#8217;s Room For Funny</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>If your brand and on-web persona fit the attempt at humor, that is. </p>
<p>This little piece of fun is from Woot, who pretty much define funny in the e-commerce space. </p>
<p>In this case, I was amused enough to get that little brand affinity glow. </p>
<p>Good experience.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/07/yes-theres-room-for-funny-in-the-ui/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Mashableahhh</title>
		<link>http://www.usabilityblog.com/2011/07/mashableahhh/</link>
		<comments>http://www.usabilityblog.com/2011/07/mashableahhh/#comments</comments>
		<pubDate>Thu, 14 Jul 2011 13:52:53 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/07/mashableahhh/</guid>
		<description><![CDATA[Mashableahhh, a photo by pjsherman on Flickr. Mashable&#8217;s gotten a bit, um, *busy* over the past few months. OK, it looks like someone barfed food coloring on the page. There. I said 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%2F07%2Fmashableahhh%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F07%2Fmashableahhh%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="Mashableahhh" href="http://www.flickr.com/photos/paulsherman/5936511349/"><img src="http://farm7.static.flickr.com/6124/5936511349_3139dfedb4.jpg" alt="Mashableahhh by pjsherman" /></a><br />
<span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/5936511349/">Mashableahhh</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>Mashable&#8217;s gotten a bit, um, *busy* over the past few months.</p>
<p>OK, it looks like someone barfed food coloring on the page. There. I said it.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/07/mashableahhh/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Now That&#8217;s A Delightful Feature</title>
		<link>http://www.usabilityblog.com/2011/07/now-thats-a-delightful-feature/</link>
		<comments>http://www.usabilityblog.com/2011/07/now-thats-a-delightful-feature/#comments</comments>
		<pubDate>Wed, 13 Jul 2011 14:04:42 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/07/now-thats-a-delightful-feature/</guid>
		<description><![CDATA[Now That&#8217;s A Delightful Feature, a photo by pjsherman on Flickr. From the Delta Airlines iOS app. It solves the age-old problem of remembering where you&#8217;ve parked at the airport. If you don&#8217;t have a fancy-shmancy smartphone, here&#8217;s an analog life hack for you: Just write the row number on the little ticket and PUT [...]]]></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%2F07%2Fnow-thats-a-delightful-feature%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F07%2Fnow-thats-a-delightful-feature%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="Now That's A Delightful Feature" href="http://www.flickr.com/photos/paulsherman/5489948859/"><img src="http://farm6.static.flickr.com/5175/5489948859_108e2d71a1.jpg" alt="Now That's A Delightful Feature by pjsherman" /></a><br />
<span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/5489948859/">Now That&#8217;s A Delightful Feature</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>From the <a href="http://delta.com/">Delta Airlines</a> <a href="http://www.apple.com/iphone/apps-for-iphone/?cid=OAS-US-DOMAINS-appstore.com">iOS app</a>. It solves the age-old problem of remembering where you&#8217;ve parked at the airport.</p>
<p>If you don&#8217;t have a fancy-shmancy smartphone, here&#8217;s an analog life hack for you: Just write the row number on the little ticket and PUT THE TICKET IN YOUR WALLET (or purse).</p>
<p>Uh, you *do* have a pen in your car, don&#8217;t you?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/07/now-thats-a-delightful-feature/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Those Prone To Motion-Induced Nausea Should Avoid This Site&#8230;</title>
		<link>http://www.usabilityblog.com/2011/07/those-prone-to-motion-induced-nausea-should-avoid-this-site/</link>
		<comments>http://www.usabilityblog.com/2011/07/those-prone-to-motion-induced-nausea-should-avoid-this-site/#comments</comments>
		<pubDate>Tue, 12 Jul 2011 20:56:00 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/?p=845</guid>
		<description><![CDATA[&#8230;but you know you&#8217;re going to click anyway. http://www.gershoni.com The kicker? They&#8217;re a design firm that purports to understand UX design. &#160;]]></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%2F07%2Fthose-prone-to-motion-induced-nausea-should-avoid-this-site%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F07%2Fthose-prone-to-motion-induced-nausea-should-avoid-this-site%2F&amp;source=pjsherman&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>&#8230;but you know you&#8217;re going to click anyway.</p>
<p><a href="http://www.gershoni.com" target="_blank">http://www.gershoni.com</a></p>
<p>The kicker? They&#8217;re a design firm that purports to understand UX design.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/07/those-prone-to-motion-induced-nausea-should-avoid-this-site/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FIle Under &#8220;If You Have To Stick A Sign On It, It Ain&#8217;t Usable.&#8221;</title>
		<link>http://www.usabilityblog.com/2011/07/file-under-if-you-have-to-stick-a-sign-on-it-it-aint-usable/</link>
		<comments>http://www.usabilityblog.com/2011/07/file-under-if-you-have-to-stick-a-sign-on-it-it-aint-usable/#comments</comments>
		<pubDate>Tue, 12 Jul 2011 15:40:38 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/07/file-under-if-you-have-to-stick-a-sign-on-it-it-aint-usable/</guid>
		<description><![CDATA[FIle Under &#34;If You Have To Stick A Sign On It, It Ain&#8217;t Usable.&#34;, a photo by pjsherman on Flickr. Found at an e-Reader display table in an airport somewhere. The post title says it all really.]]></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%2F07%2Ffile-under-if-you-have-to-stick-a-sign-on-it-it-aint-usable%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F07%2Ffile-under-if-you-have-to-stick-a-sign-on-it-it-aint-usable%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/5489949273/" title="FIle Under &quot;If You Have To Stick A Sign On It, It Ain't Usable.&quot;"><img src="http://farm6.static.flickr.com/5220/5489949273_dee8bd324a.jpg" alt="FIle Under &quot;If You Have To Stick A Sign On It, It Ain't Usable.&quot; by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/5489949273/">FIle Under &quot;If You Have To Stick A Sign On It, It Ain&#8217;t Usable.&quot;</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>Found at an e-Reader display table in an airport somewhere.</p>
<p>The post title says it all really.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/07/file-under-if-you-have-to-stick-a-sign-on-it-it-aint-usable/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Small But Good Feature</title>
		<link>http://www.usabilityblog.com/2011/07/small-but-good-feature/</link>
		<comments>http://www.usabilityblog.com/2011/07/small-but-good-feature/#comments</comments>
		<pubDate>Mon, 11 Jul 2011 12:34:29 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/07/small-but-good-feature/</guid>
		<description><![CDATA[Small But Good Feature, a photo by pjsherman on Flickr. For whatever reason, I&#8217;m not a big RSS feed user. I like visiting blog and aggregation sites rather than taking in the content via a reader. Which is why I appreciate this little feature in the corner of The Consumerist&#8216;s banner that tells me how [...]]]></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%2F07%2Fsmall-but-good-feature%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F07%2Fsmall-but-good-feature%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="Small But Good Feature" href="http://www.flickr.com/photos/paulsherman/5926213316/"><img src="http://farm7.static.flickr.com/6028/5926213316_95db86ba5c.jpg" alt="Small But Good Feature by pjsherman" /></a><br />
<span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/5926213316/">Small But Good Feature</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>For whatever reason, I&#8217;m not a big RSS feed user. I like visiting blog and aggregation sites rather than taking in the content via a reader. Which is why I appreciate this little feature in the corner of <a href="http://www.consumerist.com/">The Consumerist</a>&#8216;s banner that tells me how many posts have been made in the last day.</p>
<p>It&#8217;s not as slick as, say, <a href="http://www.huffpost.com/">Huffpost</a>&#8216;s auto-refreshing web content, but it does the job nicely for me.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/07/small-but-good-feature/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More Like A Jackson Pollock Than A Dashboard</title>
		<link>http://www.usabilityblog.com/2011/07/more-like-a-jackson-pollock-than-a-dashboard/</link>
		<comments>http://www.usabilityblog.com/2011/07/more-like-a-jackson-pollock-than-a-dashboard/#comments</comments>
		<pubDate>Tue, 05 Jul 2011 14:42:48 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/07/more-like-a-jackson-pollock-than-a-dashboard/</guid>
		<description><![CDATA[More Like A Jackson Pollock Than A Dashboard, a photo by pjsherman on Flickr. They call it a dashboard, but it looks more like a middle-period Jackson Pollock painting. There&#8217;s just no good scan to this screen. Like Gertrude Stein&#8217;s Oakland, there&#8217;s no there there. OK, let&#8217;s get specific: Poor use of white space. Crowded [...]]]></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%2F07%2Fmore-like-a-jackson-pollock-than-a-dashboard%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F07%2Fmore-like-a-jackson-pollock-than-a-dashboard%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="More Like A Jackson Pollock Than A Dashboard" href="http://www.flickr.com/photos/paulsherman/5905283596/"><img src="http://farm7.static.flickr.com/6008/5905283596_c745eafbe7.jpg" alt="More Like A Jackson Pollock Than A Dashboard by pjsherman" /></a><br />
<span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/5905283596/">More Like A Jackson Pollock Than A Dashboard</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>They call it a dashboard, but it looks more like a middle-period Jackson Pollock painting.</p>
<p>There&#8217;s just no good scan to this screen. Like Gertrude Stein&#8217;s Oakland, there&#8217;s no there there.</p>
<p>OK, let&#8217;s get specific:</p>
<ul>
<li>Poor use of white space.</li>
<li>Crowded and uneven blocks of text.</li>
<li>Mysterious graphs and charts.</li>
<li>Color? You know what they say. If you don&#8217;t know which to use, just use &#8216;em all.</li>
<li>Speaking of color, if I scored a 93%, why do I get a big &#8220;you fail&#8221; red circle?</li>
<li>Visual black hole at middle-left.</li>
<li>It&#8217;s unclear where &#8211; or even what &#8211; the main calls-to-action are.</li>
</ul>
<p>And today started off so promising&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/07/more-like-a-jackson-pollock-than-a-dashboard/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>More Drippy Nav</title>
		<link>http://www.usabilityblog.com/2011/06/more-drippy-nav/</link>
		<comments>http://www.usabilityblog.com/2011/06/more-drippy-nav/#comments</comments>
		<pubDate>Mon, 27 Jun 2011 18:28:33 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/06/more-drippy-nav/</guid>
		<description><![CDATA[More Drippy Nav, a photo by pjsherman on Flickr. Here&#8217;s AquaPure&#8217;s less painful but still annoying little brother. The main annoyance comes from the organization of the nav elements. It turns out that moving your mouse to acquire targets in a curve from top left to bottom center is surprisingly hard. Oh, and bonus points [...]]]></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%2F06%2Fmore-drippy-nav%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F06%2Fmore-drippy-nav%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/5006246521/" title="More Drippy Nav"><img src="http://farm5.static.flickr.com/4108/5006246521_13c0b5a636.jpg" alt="More Drippy Nav by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/5006246521/">More Drippy Nav</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>Here&#8217;s AquaPure&#8217;s less painful but still annoying little brother.</p>
<p>The main annoyance comes from the organization of the nav elements. It turns out that moving your mouse to acquire targets in a curve from top left to bottom center is surprisingly hard. </p>
<p>Oh, and bonus points for the completely superfluous Flash intro. Check it at http://www.cuno.com/</p>
<p>Remember, if you need to include a &#8220;skip intro&#8221; on your home page, you shouldn&#8217;t have the intro in the first place.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/06/more-drippy-nav/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nav Gone Wild</title>
		<link>http://www.usabilityblog.com/2011/06/nav-gone-wild/</link>
		<comments>http://www.usabilityblog.com/2011/06/nav-gone-wild/#comments</comments>
		<pubDate>Mon, 27 Jun 2011 18:23:20 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/06/nav-gone-wild/</guid>
		<description><![CDATA[Nav Gone Wild, a photo by pjsherman on Flickr. We have well water, so I was looking for aftermarket filters to fit our reverse osmosis filtration system. And then I found this gem of a home page. Either the designer has no sense of how people scan web pages, or AquaPure&#8217;s marketing / branding leader [...]]]></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%2F06%2Fnav-gone-wild%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F06%2Fnav-gone-wild%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/5006859476/" title="Nav Gone Wild"><img src="http://farm5.static.flickr.com/4129/5006859476_35a5647202.jpg" alt="Nav Gone Wild by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/5006859476/">Nav Gone Wild</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>We have well water, so I was looking for aftermarket filters to fit our reverse osmosis filtration system. And then I found this gem of a home page. </p>
<p>Either the designer has no sense of how people scan web pages, or AquaPure&#8217;s marketing / branding leader decided to go crazy with the whole droplet theme. </p>
<p>Either way, this is visually excruciating. Which is quite impressive given that it&#8217;s shape and layout, not color, that&#8217;s causing your eyes to cross.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/06/nav-gone-wild/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>55 Page EULA: Yeah Right</title>
		<link>http://www.usabilityblog.com/2011/06/55-page-eula-yeah-right/</link>
		<comments>http://www.usabilityblog.com/2011/06/55-page-eula-yeah-right/#comments</comments>
		<pubDate>Thu, 23 Jun 2011 18:16:08 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/06/55-page-eula-yeah-right/</guid>
		<description><![CDATA[55 Page EULA: Yeah Right, a photo by pjsherman on Flickr. Insanely long EULAs must die. And on a phone, no less.]]></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%2F06%2F55-page-eula-yeah-right%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F06%2F55-page-eula-yeah-right%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/5499334229/" title="55 Page EULA: Yeah Right"><img src="http://farm6.static.flickr.com/5137/5499334229_27e8a2071e.jpg" alt="55 Page EULA: Yeah Right by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/5499334229/">55 Page EULA: Yeah Right</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>Insanely long EULAs must die. And on a phone, no less.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/06/55-page-eula-yeah-right/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Local News Site: My Eyes, They Burn&#8230;</title>
		<link>http://www.usabilityblog.com/2011/06/local-news-site-my-eyes-they-burn/</link>
		<comments>http://www.usabilityblog.com/2011/06/local-news-site-my-eyes-they-burn/#comments</comments>
		<pubDate>Thu, 23 Jun 2011 18:14:45 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/06/local-news-site-my-eyes-they-burn/</guid>
		<description><![CDATA[Local News Site: My Eyes, They Burn&#8230;, a photo by pjsherman on Flickr. Not much to say here except ouch. Design 101: Don&#8217;t mix saturated red and blue. Chromostereopsis FTL.]]></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%2F06%2Flocal-news-site-my-eyes-they-burn%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F06%2Flocal-news-site-my-eyes-they-burn%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/5499334785/" title="Local News Site: My Eyes, They Burn..."><img src="http://farm6.static.flickr.com/5019/5499334785_215fe5688b.jpg" alt="Local News Site: My Eyes, They Burn... by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/5499334785/">Local News Site: My Eyes, They Burn&#8230;</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>Not much to say here except ouch. Design 101: Don&#8217;t mix saturated red and blue. Chromostereopsis FTL.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/06/local-news-site-my-eyes-they-burn/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Impossible To Sign Design</title>
		<link>http://www.usabilityblog.com/2011/06/impossible-to-sign-design/</link>
		<comments>http://www.usabilityblog.com/2011/06/impossible-to-sign-design/#comments</comments>
		<pubDate>Wed, 22 Jun 2011 13:42:29 +0000</pubDate>
		<dc:creator>Paul Sherman</dc:creator>
				<category><![CDATA[Everything Else]]></category>

		<guid isPermaLink="false">http://www.usabilityblog.com/2011/06/impossible-to-sign-design/</guid>
		<description><![CDATA[Impossible To Sign Design, a photo by pjsherman on Flickr. I&#8217;m not sure you can tell from this picture. But the issue with this design is that the designer positioned the signature box at the top of the screen, which in combination with the raised area of the bezel makes it nearly impossible to sign. [...]]]></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%2F06%2Fimpossible-to-sign-design%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.usabilityblog.com%2F2011%2F06%2Fimpossible-to-sign-design%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/5499913350/" title="Impossible To Sign Design"><img src="http://farm6.static.flickr.com/5056/5499913350_73b2f15434.jpg" alt="Impossible To Sign Design by pjsherman" /></a><br /><span style="margin: 0;"><a href="http://www.flickr.com/photos/paulsherman/5499913350/">Impossible To Sign Design</a>, a photo by <a href="http://www.flickr.com/photos/paulsherman/">pjsherman</a> on Flickr.</span></div>
<p>I&#8217;m not sure you can tell from this picture. But the issue with this design is that the designer positioned the signature box at the top of the screen, which in combination with the raised area of the bezel makes it nearly impossible to sign. </p>
<p>The bezel immediately above the signature box is scored with gouges and scratches, testament to the failure of this design.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.usabilityblog.com/2011/06/impossible-to-sign-design/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 4.222 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-02-09 16:06:11 -->

