<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Usability Test Results Too Diverse?</title>
	<atom:link href="http://justaddwater.dk/2007/02/16/usability-test-results-too-diverse/feed/" rel="self" type="application/rss+xml" />
	<link>http://justaddwater.dk/2007/02/16/usability-test-results-too-diverse/</link>
	<description>Instant Usability &#38; Web Standards</description>
	<lastBuildDate>Sat, 28 Jan 2012 13:44:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: sloan</title>
		<link>http://justaddwater.dk/2007/02/16/usability-test-results-too-diverse/comment-page-1/#comment-93242</link>
		<dc:creator>sloan</dc:creator>
		<pubDate>Wed, 28 Feb 2007 05:56:03 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2007/02/16/usability-test-results-too-diverse/#comment-93242</guid>
		<description>It always depends on the project. Sometimes 5 people is all you need because it isn&#039;t a critical application roll out anyway. What I find really effective as an additional kind of testing is having the application reviewed by another designer that is not part of the project and given only the context a user would have. As you design your system, you come to accept some weird business rules or get too close, having another designer go through it can help you challenge yourself on those points.</description>
		<content:encoded><![CDATA[<p>It always depends on the project. Sometimes 5 people is all you need because it isn&#8217;t a critical application roll out anyway. What I find really effective as an additional kind of testing is having the application reviewed by another designer that is not part of the project and given only the context a user would have. As you design your system, you come to accept some weird business rules or get too close, having another designer go through it can help you challenge yourself on those points.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://justaddwater.dk/2007/02/16/usability-test-results-too-diverse/comment-page-1/#comment-87545</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Tue, 20 Feb 2007 01:21:49 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2007/02/16/usability-test-results-too-diverse/#comment-87545</guid>
		<description>&quot;Many of the usability problems we have seen should have not occurred on the website in the first place&quot;  Agreed completely.  Usability test your prototypes and you could probably just get by with 5 people.   iRise, Axure, Lucid Spec, and GUI Design Gallery are some great higher fidelity prototyping tools out there.

Most of my 30 or so usability test have had 3-6 people.  The one that had 12 ended up seeing the same usability problems after about 5 people (this had a diverse user group too).</description>
		<content:encoded><![CDATA[<p>&#8220;Many of the usability problems we have seen should have not occurred on the website in the first place&#8221;  Agreed completely.  Usability test your prototypes and you could probably just get by with 5 people.   iRise, Axure, Lucid Spec, and GUI Design Gallery are some great higher fidelity prototyping tools out there.</p>
<p>Most of my 30 or so usability test have had 3-6 people.  The one that had 12 ended up seeing the same usability problems after about 5 people (this had a diverse user group too).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Szuc</title>
		<link>http://justaddwater.dk/2007/02/16/usability-test-results-too-diverse/comment-page-1/#comment-86065</link>
		<dc:creator>Daniel Szuc</dc:creator>
		<pubDate>Sun, 18 Feb 2007 03:26:10 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2007/02/16/usability-test-results-too-diverse/#comment-86065</guid>
		<description>Evaluate with key flows and iterate. Its impossible to evaluate everything, but you can determine the parts of the product that will determine its success. For example, if people are not registering to use your product - this may have to be addressed before looking at other functions.</description>
		<content:encoded><![CDATA[<p>Evaluate with key flows and iterate. Its impossible to evaluate everything, but you can determine the parts of the product that will determine its success. For example, if people are not registering to use your product &#8211; this may have to be addressed before looking at other functions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

