<?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: Low Response Rates? The Answer Lurks in The Shadows</title>
	<atom:link href="http://www.researchrockstar.com/low-response-rates-the-answers-lurks-in-the-shadows/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.researchrockstar.com/low-response-rates-the-answers-lurks-in-the-shadows/</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 Korostoff</title>
		<link>http://www.researchrockstar.com/low-response-rates-the-answers-lurks-in-the-shadows/comment-page-1/#comment-1486</link>
		<dc:creator>Kathryn Korostoff</dc:creator>
		<pubDate>Thu, 12 Jan 2012 17:58:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.researchrockstar.com/?p=1471#comment-1486</guid>
		<description>Thanks! Glad you liked it!</description>
		<content:encoded><![CDATA[<p>Thanks! Glad you liked it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tracking Participant Engagement &#124; Future of Insight</title>
		<link>http://www.researchrockstar.com/low-response-rates-the-answers-lurks-in-the-shadows/comment-page-1/#comment-1485</link>
		<dc:creator>Tracking Participant Engagement &#124; Future of Insight</dc:creator>
		<pubDate>Tue, 10 Jan 2012 13:57:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.researchrockstar.com/?p=1471#comment-1485</guid>
		<description>[...] another solid take on this topic, I recommend Research Rockstar&#8217;s thoughts on matching methodology sample universe to project ob.... The survey instrument itself is just one element of the [...]</description>
		<content:encoded><![CDATA[<p>[...] another solid take on this topic, I recommend Research Rockstar&#8217;s thoughts on matching methodology sample universe to project ob&#8230;. The survey instrument itself is just one element of the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kathryn</title>
		<link>http://www.researchrockstar.com/low-response-rates-the-answers-lurks-in-the-shadows/comment-page-1/#comment-279</link>
		<dc:creator>Kathryn</dc:creator>
		<pubDate>Sun, 17 Jan 2010 17:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.researchrockstar.com/?p=1471#comment-279</guid>
		<description>Thanks Ed--I&#039;ve also had a lot of tech clients try to target folks who were just too senior for their product category. Usually they listen to reason, though I have seen some folks need to learn the hard way....</description>
		<content:encoded><![CDATA[<p>Thanks Ed&#8211;I&#8217;ve also had a lot of tech clients try to target folks who were just too senior for their product category. Usually they listen to reason, though I have seen some folks need to learn the hard way&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed Erickson</title>
		<link>http://www.researchrockstar.com/low-response-rates-the-answers-lurks-in-the-shadows/comment-page-1/#comment-274</link>
		<dc:creator>Ed Erickson</dc:creator>
		<pubDate>Wed, 13 Jan 2010 22:52:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.researchrockstar.com/?p=1471#comment-274</guid>
		<description>Your post highlights another issue that I&#039;ve seen frequently, which is a mismatch of objective to target audience.

A critical aspect of research/survey design is to ask questions that the respondent can/will answer.  A big part of getting this right is talking to the people with the answers to your questions.  This goes a long way to improving data quality and engagement - after all, who is going to want to spend much time answering questions that aren&#039;t really relevant to them?

From the way you described the example, it sounds like a big part of the problem was asking questions of senior execs instead of the mid-level, technical people who could better provide the answers.  

In many years of conducting B2B research, I&#039;ve noticed a tendency among marketers to think that decisions about their product or service are made at the highest levels, when most of the time this just isn&#039;t the case.  To be sure, the C-suite is the decision-maker in some cases, but for the large majority of products and services sold to businesses, the real purchase decisions are made much lower on the ladder.  It&#039;s up to the research consultant to address issues like this upfront, while the research is being designed, to avoid an outcome as you described.</description>
		<content:encoded><![CDATA[<p>Your post highlights another issue that I&#8217;ve seen frequently, which is a mismatch of objective to target audience.</p>
<p>A critical aspect of research/survey design is to ask questions that the respondent can/will answer.  A big part of getting this right is talking to the people with the answers to your questions.  This goes a long way to improving data quality and engagement &#8211; after all, who is going to want to spend much time answering questions that aren&#8217;t really relevant to them?</p>
<p>From the way you described the example, it sounds like a big part of the problem was asking questions of senior execs instead of the mid-level, technical people who could better provide the answers.  </p>
<p>In many years of conducting B2B research, I&#8217;ve noticed a tendency among marketers to think that decisions about their product or service are made at the highest levels, when most of the time this just isn&#8217;t the case.  To be sure, the C-suite is the decision-maker in some cases, but for the large majority of products and services sold to businesses, the real purchase decisions are made much lower on the ladder.  It&#8217;s up to the research consultant to address issues like this upfront, while the research is being designed, to avoid an outcome as you described.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

