<?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>UXbyDesign.org &#187; Test Script</title>
	<atom:link href="http://www.uxbydesign.org/tag/test-script/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uxbydesign.org</link>
	<description>A User Experience Blog by Bradley Hebdon</description>
	<lastBuildDate>Tue, 02 Mar 2010 06:16:56 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Caution: 5 Common Usability Testing Mistakes to Avoid</title>
		<link>http://www.uxbydesign.org/2009/07/15/5-common-usability-testing-mistakes-to-avoid/</link>
		<comments>http://www.uxbydesign.org/2009/07/15/5-common-usability-testing-mistakes-to-avoid/#comments</comments>
		<pubDate>Thu, 16 Jul 2009 05:55:56 +0000</pubDate>
		<dc:creator>Bradley Hebdon</dc:creator>
				<category><![CDATA[Features]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Mistakes]]></category>
		<category><![CDATA[Moderator Guide]]></category>
		<category><![CDATA[Participants]]></category>
		<category><![CDATA[Test Script]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Usability Testing]]></category>
		<category><![CDATA[User Interface]]></category>
		<category><![CDATA[UX]]></category>

		<guid isPermaLink="false">http://www.uxbydesign.org/?p=810</guid>
		<description><![CDATA[Usability testing is not an easy thing to perfect. However, a good starting point is to identify where most mistakes are made throughout the process. And through this awareness, you should fine-tune your approaches to planning, moderation and analysis, in order to attain truly insightful findings. 1. Recruiting Unsuitable Participants It&#8217;s vital that you validate a design through the eyes of [...]


Related posts:<ol><li><a href='http://www.uxbydesign.org/2009/07/23/amy-buckner-mobile-usability/' rel='bookmark' title='Permanent Link: Interview: Amy Buckner on Mobile Usability'>Interview: Amy Buckner on Mobile Usability</a></li>
<li><a href='http://www.uxbydesign.org/2009/06/29/usability-study-suggests-bing-beats-google/' rel='bookmark' title='Permanent Link: Usability Study suggests Bing topples Google?'>Usability Study suggests Bing topples Google?</a></li>
<li><a href='http://www.uxbydesign.org/2009/06/24/20-user-experience-books-you-should-own/' rel='bookmark' title='Permanent Link: 20 User Experience Books you should own'>20 User Experience Books you should own</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.uxbydesign.org/wp-content/uploads/2009/07/caution.jpg"><img class="aligncenter size-full wp-image-1005" title="caution" src="http://www.uxbydesign.org/wp-content/uploads/2009/07/caution.jpg" alt="caution" width="540" height="210" /></a>Usability testing is not an easy thing to perfect. However, a good starting point is to identify where most mistakes are made throughout the process. And through this awareness, you should fine-tune your approaches to planning, moderation and analysis, in order to attain truly insightful findings.</p>
<p><strong>1. Recruiting Unsuitable Participants<br />
</strong>It&#8217;s vital that you validate a design through the eyes of your user. But who are your users? Work with marketing folks to understand your target audience, and screen potential participants accordingly.  If you have recruited participants that are too advanced, they might not uncover usability issues that a more typical user might experience.  Regardless of how good the moderator might be, if you don&#8217;t have suitable and relevant participants, you won&#8217;t be getting an accurate usability assessment.</p>
<p><strong>2. Not identifying the Critical Tasks</strong><br />
Have you identified the primary use cases and goal-oriented tasks?  Really think critically here, and focus on the  most important ones only. Hopefully you have already designed the user interface around these tasks, so bring them into the test. Write a test script that includes a moderator guide, and provide context to the tasks. Make users feel like they are in a real-life situation by telling them a story.E.g. &#8220;It&#8217;s 5 days before Christmas and you need to buy your nephew in Germany a Nintendo Wii&#8221;. Critical tasks are not only a usability concern, they&#8217;re equally impactful on the business. </p>
<p><strong>3. Testing Too Much For Too Long</strong><br />
Don&#8217;t feel like you have to test every single aspect of a user interface, nor every single possible task. Focus on what&#8217;s critical and if necessary, break the test into multiple phases. After 45 minutes or so, most users will tire and will have trouble focusing. So keep the sessions to under an hour if possible.</p>
<p><strong>4. Allowing Participants to be Designers</strong><br />
As a general rule of thumb, you should be looking for what participants DO more than what they say. It&#8217;s OK to ask what their impressions are, especially when comparing a new design against an old one. Just be careful about taking their feedback literally.  E.g. A user may have a personal preference for red, and suggest that all buttons should be red and flashing. Now, taking this feedback literally could actually introduce usability issues. Observe, filter and interpret.</p>
<p><strong>5. Asking Too Many Questions</strong><br />
Keep in mind that a usability test should be focused primarily on task completion, navigation, comprehension, and interaction. While it&#8217;s OK to ask some questions to understand how satisfied they are with the experience, most of the findings should be derived through observation and not questioning.</p>
<p>While these are what I consider the top 5 mistakes made, there are many more to consider. What other common mistakes would you add to this list?</p>


<p>Related posts:<ol><li><a href='http://www.uxbydesign.org/2009/07/23/amy-buckner-mobile-usability/' rel='bookmark' title='Permanent Link: Interview: Amy Buckner on Mobile Usability'>Interview: Amy Buckner on Mobile Usability</a></li>
<li><a href='http://www.uxbydesign.org/2009/06/29/usability-study-suggests-bing-beats-google/' rel='bookmark' title='Permanent Link: Usability Study suggests Bing topples Google?'>Usability Study suggests Bing topples Google?</a></li>
<li><a href='http://www.uxbydesign.org/2009/06/24/20-user-experience-books-you-should-own/' rel='bookmark' title='Permanent Link: 20 User Experience Books you should own'>20 User Experience Books you should own</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://www.uxbydesign.org/2009/07/15/5-common-usability-testing-mistakes-to-avoid/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
