<?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>Good Usability &#187; tasks</title>
	<atom:link href="http://www.goodusability.co.uk/tag/tasks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.goodusability.co.uk</link>
	<description></description>
	<lastBuildDate>Fri, 20 Apr 2012 09:11:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Usability tests and the effect of learning</title>
		<link>http://www.goodusability.co.uk/2008/10/06/usability-tests-and-the-effect-of-learning/</link>
		<comments>http://www.goodusability.co.uk/2008/10/06/usability-tests-and-the-effect-of-learning/#comments</comments>
		<pubDate>Mon, 06 Oct 2008 22:58:04 +0000</pubDate>
		<dc:creator>David Hamill</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[tasks]]></category>
		<category><![CDATA[Usability testing]]></category>

		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=169</guid>
		<description><![CDATA[During usability tests participants will learn how to use the website during the session. This can have an affect on the accuracy of your results. Simulating reality Usability tests attempt to discover what people really do when they use websites. Essentially we&#8217;re trying to simulate situations that occur in real life. Good test facilitators try [...]]]></description>
			<content:encoded><![CDATA[<p>During usability tests participants will learn how to use the website during the session. This can have an affect on the accuracy of your results.</p>
<h3>Simulating reality</h3>
<p>Usability tests attempt to discover what people really do when they use websites. Essentially we&#8217;re trying to simulate situations that occur in real life. Good test facilitators try to preserve this reality as much as they can. However in reality, participants do not spend an hour or so carrying out a handful of different tasks on a website.</p>
<h3>Learning effect</h3>
<p>As the participant attempts each task, they (hopefully) learn a little more about the site. So in subsequent tasks you don&#8217;t get to observe how truly new users will perform the task. This is why you should be <a href="http://www.goodusability.co.uk/2008/10/usability-test-tasks-to-avoid/">careful about the tasks you include</a> in your study. In reality people might attempt only one task on your site, so this learning effect can be artificial.</p>
<h3>Randomising tasks</h3>
<p>One option is to randomise the tasks. So no participant does the tasks in the same order. This balances the effect of learning across the tasks. If you&#8217;re timing tasks, using eye tracking or are specifically interested in success metrics, then this is the way to go.</p>
<h3>Prioritising tasks</h3>
<p>If you have a clear idea of the key tasks for your site and they have an obvious priority order then you can order them by priority. So your top task gets to go first. The rest follow in priority order. However you have to accept that your completion levels are a little flawed.</p>
<h3>Prioritise then randomise</h3>
<p>Some sites have a single task that is significantly more important than all of the others. Take for instance an airline. Booking a flight is easily the top task. There are lots of other tasks but none of them come close in terms of importance. In cases like this you can start every participant with your key task. After this the following tasks are randomised.</p>
<p>So you get the benefit of having no learning effect on your number one task. On all the others the learning effect is distributed across the tasks.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.goodusability.co.uk/2008/10/06/usability-tests-and-the-effect-of-learning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Usability test tasks to avoid</title>
		<link>http://www.goodusability.co.uk/2008/10/03/usability-test-tasks-to-avoid/</link>
		<comments>http://www.goodusability.co.uk/2008/10/03/usability-test-tasks-to-avoid/#comments</comments>
		<pubDate>Fri, 03 Oct 2008 22:26:33 +0000</pubDate>
		<dc:creator>David Hamill</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[eyetracking]]></category>
		<category><![CDATA[tasks]]></category>
		<category><![CDATA[tips]]></category>
		<category><![CDATA[Usability testing]]></category>

		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=111</guid>
		<description><![CDATA[Whether you&#8217;re carrying out your own test or a specialist is doing it for you, there are a few tasks I that recommend you avoid. Free browse The free browse task is when the facilitator just asks the participant to just spend a few minutes looking around the site. People often make it the first [...]]]></description>
			<content:encoded><![CDATA[<p>Whether you&#8217;re carrying out your own test or a specialist is doing it for you, there are a few tasks I that recommend you avoid.</p>
<h3>Free browse</h3>
<p>The free browse task is when the facilitator just asks the participant to just spend a few minutes looking around the site. People often make it the first task in the test. But it&#8217;s a waste of valuable lab time.</p>
<p><strong>It&#8217;s totally artificial.</strong> In a usability test you&#8217;re trying to simulate reality. You want to see how people are actually using your site out there in the real world. Nobody is going to just browse around your site<strong> </strong>without purpose. It&#8217;s tempting just to get their impressions of the site but it&#8217;s of no real value. If you start off with a free browse task you&#8217;re basically giving the user the opportunity to teach themselves how to use your site.</p>
<p><strong>It&#8217;s a waste of your first task. </strong>There is naturally going to be some learning that takes place during a usability test. So your first task is the most real. It is the one that the participant attempts fresh. This is the moment when you get to see how people use your site when they&#8217;ve never used it before. If you use this opportunity to let participants have a quick browse around then you&#8217;re throwing away the most useful part of the session.</p>
<h3>Homepage review</h3>
<p>The homepage review task is when the facilitator walks the participant through each part of the homepage and ask for their impressions.</p>
<p><strong>It too is artificial.</strong> Like the free browse task, the homepage review does not simulate reality. You can get a bit of useful information from it, but at the cost of making the rest of your tasks unreal.</p>
<p><strong>You help the participant decide where to click.</strong> When people attempt to find information on a website they don&#8217;t look at every link on the homepage. They often follow the first appropriate looking link.</p>
<p>If you&#8217;ve previously walked them through every aspect of the site&#8217;s homepage you are giving them an insight that they will not get in reality. Instead of following the first link that looks appropriate, they can use the knowledge from the homepage review to decide which of all the options is the best. They are then performing a scenario that bares little resemblance to the experience real users will have.</p>
<h3>Eyetracking the homepage</h3>
<p>Eyetracking is a bit of a touchy subject in usability at present. It is only really helpful in very specific studies but usability companies are finding that it wins business. But that&#8217;s the topic for about a dozen other posts.</p>
<p>The results of just eyetracking participants looking at the homepage are totally useless without giving<strong> </strong>them a task to do. I&#8217;ll explain this with an example.</p>
<p>If I were to ask you to look at a door without any other instruction you would probably stare blankly at it. If you knew I was eyetracking, you might feel obliged to look around different bits of the door.</p>
<p>However if I were to ask you to open the door then you would most likely look at the door handle. If I were to ask you to remove the door, you&#8217;d probably look at the hinges. You see the areas you look at will depend on the task you are trying to complete.</p>
<p>It&#8217;s a totally useless exercise to just show a participant a page and then track their eyes while they do it. Nobody will ever visit your site to just stare blankly at the page. You might end up with a pretty picture to pass around the office. But that&#8217;s all it is, a pretty picture.</p>
<p>The results of eyetracking a page will differ widely depending on the task that the participants are asked to complete.</p>
<h3>Try to simulate reality</h3>
<p>Usability testing is about trying to simulate what&#8217;s happening in the real world and benefit from the observations. The tasks above are vanity tasks that remove an element of reality from the session. You will get more realistic results if you avoid using them.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.goodusability.co.uk/2008/10/03/usability-test-tasks-to-avoid/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

