<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: UIE Tips: Starting Your User Research</title>
	<atom:link href="http://www.uie.com/brainsparks/2012/04/18/uietips-starting-user-research/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2012/04/18/uietips-starting-user-research/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Thu, 23 May 2013 10:02:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Etan</title>
		<link>http://www.uie.com/brainsparks/2012/04/18/uietips-starting-user-research/comment-page-1/#comment-215370</link>
		<dc:creator>Etan</dc:creator>
		<pubDate>Thu, 19 Apr 2012 20:12:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=6923#comment-215370</guid>
		<description>Thanks for the article outlining some user research style projects. 

I find myself wanting a little more detail on the &quot;Interview-based usability test&quot; technique. 

Spending time in advance to formulate tasks with the participant, and then in that same session conduct a usability test would seem really time consuming to me. Even with pre-defined tasks, I find usability studies are typically about an hour or 1.5 hours long. A participant usually gets pretty exhausted past 1.5 hours. I suppose you could limit to two tasks, but that probably wouldn&#039;t suffice for more complex &quot;enterprise&quot; type products

Do you have a recommendation on how to keep a session like that contained? Also, how do you report your findings at the end? If you test 6 users, but they all have vastly different tasks, it&#039;s difficult to quantify in aggregate across all of your participants (despite collecting a good deal of handy qualitative feedback / observations).

Any pointers elaborating on that technique would be much appreciated!

Cheers,
Etan</description>
		<content:encoded><![CDATA[<p>Thanks for the article outlining some user research style projects. </p>
<p>I find myself wanting a little more detail on the &#8220;Interview-based usability test&#8221; technique. </p>
<p>Spending time in advance to formulate tasks with the participant, and then in that same session conduct a usability test would seem really time consuming to me. Even with pre-defined tasks, I find usability studies are typically about an hour or 1.5 hours long. A participant usually gets pretty exhausted past 1.5 hours. I suppose you could limit to two tasks, but that probably wouldn&#8217;t suffice for more complex &#8220;enterprise&#8221; type products</p>
<p>Do you have a recommendation on how to keep a session like that contained? Also, how do you report your findings at the end? If you test 6 users, but they all have vastly different tasks, it&#8217;s difficult to quantify in aggregate across all of your participants (despite collecting a good deal of handy qualitative feedback / observations).</p>
<p>Any pointers elaborating on that technique would be much appreciated!</p>
<p>Cheers,<br />
Etan</p>
]]></content:encoded>
	</item>
</channel>
</rss>
