<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Would You Bet Your Life Savings On It?</title>
	<atom:link href="http://www.uie.com/brainsparks/2007/05/11/would-you-bet-your-life-savings-on-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2007/05/11/would-you-bet-your-life-savings-on-it/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<pubDate>Wed,  3 Dec 2008 23:51:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Benjamin Ho</title>
		<link>http://www.uie.com/brainsparks/2007/05/11/would-you-bet-your-life-savings-on-it/#comment-77157</link>
		<dc:creator>Benjamin Ho</dc:creator>
		<pubDate>Thu, 24 May 2007 13:42:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/05/11/would-you-bet-your-life-savings-on-it/#comment-77157</guid>
		<description>What I do is "let the data/evidence speak for itself".  (Taken from CSI.)  If I don't have it on video or on a survey from user feedback, then there's no proof.  Every problem needs to be substantiated by some sort of proof.  If there isn't any of that, then the problem doesn't really exist - only in our heads.  Sometimes even when a user complains about something, it's not necessarily a big issue - only a preference issue.

I think a usability practitioner must be able to use discernment, and practice it with every point of data that may affect the overall design of the user experience or interface.  Without discernment, there's no prioritizing.  Without prioritizing, there's no focus.</description>
		<content:encoded><![CDATA[<p>What I do is &#8220;let the data/evidence speak for itself&#8221;.  (Taken from CSI.)  If I don&#8217;t have it on video or on a survey from user feedback, then there&#8217;s no proof.  Every problem needs to be substantiated by some sort of proof.  If there isn&#8217;t any of that, then the problem doesn&#8217;t really exist - only in our heads.  Sometimes even when a user complains about something, it&#8217;s not necessarily a big issue - only a preference issue.</p>
<p>I think a usability practitioner must be able to use discernment, and practice it with every point of data that may affect the overall design of the user experience or interface.  Without discernment, there&#8217;s no prioritizing.  Without prioritizing, there&#8217;s no focus.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zephyr</title>
		<link>http://www.uie.com/brainsparks/2007/05/11/would-you-bet-your-life-savings-on-it/#comment-77062</link>
		<dc:creator>Zephyr</dc:creator>
		<pubDate>Fri, 18 May 2007 23:11:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/05/11/would-you-bet-your-life-savings-on-it/#comment-77062</guid>
		<description>I understand the goal behind the question, but, primarily, usability tests identify obstacles, not solutions. When you know the problem, you can start thinking of a solution, but that solution hasn't actually been tested at that point. Nevertheless, it seems like a good question to make you look critically at your recommendations.

Unfortunately, many companies don't seem very critical when judging the validity of recommendations. I've seen reports by reputable consultancy companies where some recommendations could not be connected to the data measured.</description>
		<content:encoded><![CDATA[<p>I understand the goal behind the question, but, primarily, usability tests identify obstacles, not solutions. When you know the problem, you can start thinking of a solution, but that solution hasn&#8217;t actually been tested at that point. Nevertheless, it seems like a good question to make you look critically at your recommendations.</p>
<p>Unfortunately, many companies don&#8217;t seem very critical when judging the validity of recommendations. I&#8217;ve seen reports by reputable consultancy companies where some recommendations could not be connected to the data measured.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.uie.com/brainsparks/2007/05/11/would-you-bet-your-life-savings-on-it/#comment-76925</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Fri, 11 May 2007 18:07:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/05/11/would-you-bet-your-life-savings-on-it/#comment-76925</guid>
		<description>Love the idea because many of the improvement ideas literally cost that much do.  Planning, developement , testing, and installation have a lot of costs associate with it.  You need a quick way to chose which improvements you need to do over others.</description>
		<content:encoded><![CDATA[<p>Love the idea because many of the improvement ideas literally cost that much do.  Planning, developement , testing, and installation have a lot of costs associate with it.  You need a quick way to chose which improvements you need to do over others.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
