<?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 tasks to avoid</title>
	<atom:link href="http://www.goodusability.co.uk/2008/10/usability-test-tasks-to-avoid/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.goodusability.co.uk/2008/10/usability-test-tasks-to-avoid/</link>
	<description></description>
	<lastBuildDate>Wed, 28 Jul 2010 11:54:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: David Hamill</title>
		<link>http://www.goodusability.co.uk/2008/10/usability-test-tasks-to-avoid/comment-page-1/#comment-718</link>
		<dc:creator>David Hamill</dc:creator>
		<pubDate>Tue, 03 Mar 2009 19:58:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=111#comment-718</guid>
		<description>Hi Alice, I would recommend some interview based tasks instead. So before they even see the website, you interview the participant about the subject matter. You want to find out from them what they would want to do with the site. This becomes your first task. Be sure to agree with them beforehand what needs to happen for the task to be a success. You can usually create a few tasks like this that have the benefit of being more real for the participant. 

If you want to follow up the first task by asking the participant what they would want to do next, then this is fine. But you need to agree a purpose or they will go into play mode. It&#039;s a good idea to quickly switch the monitor of when creating that follow up task. Otherwise they might just aimlessly create fantasy tasks based on what&#039;s in front of them.</description>
		<content:encoded><![CDATA[<p>Hi Alice, I would recommend some interview based tasks instead. So before they even see the website, you interview the participant about the subject matter. You want to find out from them what they would want to do with the site. This becomes your first task. Be sure to agree with them beforehand what needs to happen for the task to be a success. You can usually create a few tasks like this that have the benefit of being more real for the participant. </p>
<p>If you want to follow up the first task by asking the participant what they would want to do next, then this is fine. But you need to agree a purpose or they will go into play mode. It&#8217;s a good idea to quickly switch the monitor of when creating that follow up task. Otherwise they might just aimlessly create fantasy tasks based on what&#8217;s in front of them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alice</title>
		<link>http://www.goodusability.co.uk/2008/10/usability-test-tasks-to-avoid/comment-page-1/#comment-716</link>
		<dc:creator>alice</dc:creator>
		<pubDate>Tue, 03 Mar 2009 19:40:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=111#comment-716</guid>
		<description>Re your comment on free browse as first task, what would you think if I have my first specific task for the user, and upon completion, i allow him to spend a couple of minutes to &#039;explore&#039; the site? My key objective is to observe how a user will be more inclined to do next - whether he will sign up, read FAQ, go homepage again to read about the service etc. every act and how he gets there is a learning point for us.</description>
		<content:encoded><![CDATA[<p>Re your comment on free browse as first task, what would you think if I have my first specific task for the user, and upon completion, i allow him to spend a couple of minutes to &#8216;explore&#8217; the site? My key objective is to observe how a user will be more inclined to do next &#8211; whether he will sign up, read FAQ, go homepage again to read about the service etc. every act and how he gets there is a learning point for us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Kennedy</title>
		<link>http://www.goodusability.co.uk/2008/10/usability-test-tasks-to-avoid/comment-page-1/#comment-227</link>
		<dc:creator>Ryan Kennedy</dc:creator>
		<pubDate>Mon, 23 Feb 2009 23:11:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=111#comment-227</guid>
		<description>Do people really do these in tests? How pointless. Set them to work! Tasks, tasks, tasks!</description>
		<content:encoded><![CDATA[<p>Do people really do these in tests? How pointless. Set them to work! Tasks, tasks, tasks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
