<?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"
	>
<channel>
	<title>Comments on: Research on the Quick</title>
	<atom:link href="http://triux.org/2006/09/28/research-on-the-quick/feed/" rel="self" type="application/rss+xml" />
	<link>http://triux.org/2006/09/28/research-on-the-quick/</link>
	<description>User Experience news and events from North Carolina</description>
	<pubDate>Sun, 06 Jul 2008 19:07:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>By: Sam</title>
		<link>http://triux.org/2006/09/28/research-on-the-quick/#comment-2375</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Wed, 04 Oct 2006 16:18:11 +0000</pubDate>
		<guid isPermaLink="false">http://triux.wordpress.com/2006/09/28/research-on-the-quick/#comment-2375</guid>
		<description>We are ramping up direct observation and I got a reminder just today that _sometimes_ users can tell you exactly what they need. After a recent observation and task analysis session I walked back to the users' work area and saw a wishlist on a whiteboard that echoed my own conclusions.  

So while I don't like to rely on interviews, I think they should be done at some point.  The information gathered can't be allowed to steer the rest of the requirements gathering, but it can be good for fleshing out details and as a sanity check.  

Dealing with conflicts between user interview material and contextual analysis is probably a good topic for a broader discussion.</description>
		<content:encoded><![CDATA[<p>We are ramping up direct observation and I got a reminder just today that _sometimes_ users can tell you exactly what they need. After a recent observation and task analysis session I walked back to the users&#8217; work area and saw a wishlist on a whiteboard that echoed my own conclusions.  </p>
<p>So while I don&#8217;t like to rely on interviews, I think they should be done at some point.  The information gathered can&#8217;t be allowed to steer the rest of the requirements gathering, but it can be good for fleshing out details and as a sanity check.  </p>
<p>Dealing with conflicts between user interview material and contextual analysis is probably a good topic for a broader discussion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
