<?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: Using Customer Feedback to Inform Product Design Decisions</title>
	<atom:link href="http://www.researchrockstar.com/using-customer-feedback-to-inform-product-design-decisions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.researchrockstar.com/using-customer-feedback-to-inform-product-design-decisions/</link>
	<description>Research Rockstar for Market Research, that Rocks. Online Training for Market Research.</description>
	<lastBuildDate>Wed, 01 Feb 2012 08:24:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Kathryn</title>
		<link>http://www.researchrockstar.com/using-customer-feedback-to-inform-product-design-decisions/comment-page-1/#comment-57</link>
		<dc:creator>Kathryn</dc:creator>
		<pubDate>Sat, 19 Sep 2009 13:50:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.researchrockstar.com/?p=754#comment-57</guid>
		<description>I had an interesting conversation with someone who asked, &quot;We did a study like this last year, and the results seemed a little obvious. The features we expected to be tops, were tops. Getting my team to fund this kind of research again will be hard now.&quot;  Look, it can happen. Sometimes research just confirms what you already suspected. Also, if you are developing a product that only has, say, 2 or 3 possible/realistic variations--this kind of approach (MaxDiff or conjoint) can be overkill. There are simpler (and less expensive) options in those cases. BUT sometimes confirming your own suspicions can be valuable, sometimes you do get surprised, and sometimes being able to look for variations by subgroup (&quot;Aha, feature combo A is much more attractive to this segment; feature combo B really appeals mostly to that segment) can be very useful.</description>
		<content:encoded><![CDATA[<p>I had an interesting conversation with someone who asked, &#8220;We did a study like this last year, and the results seemed a little obvious. The features we expected to be tops, were tops. Getting my team to fund this kind of research again will be hard now.&#8221;  Look, it can happen. Sometimes research just confirms what you already suspected. Also, if you are developing a product that only has, say, 2 or 3 possible/realistic variations&#8211;this kind of approach (MaxDiff or conjoint) can be overkill. There are simpler (and less expensive) options in those cases. BUT sometimes confirming your own suspicions can be valuable, sometimes you do get surprised, and sometimes being able to look for variations by subgroup (&#8220;Aha, feature combo A is much more attractive to this segment; feature combo B really appeals mostly to that segment) can be very useful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

