<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>CTC Research &#187; client</title>
	<atom:link href="http://ctcresearch.com/wordpress/tag/client/feed/" rel="self" type="application/rss+xml" />
	<link>http://ctcresearch.com/wordpress</link>
	<description>Qualitative Research by a Focus Group Moderator</description>
	<lastBuildDate>Tue, 10 Feb 2009 06:20:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>How to Deal with a Domineering Focus Group Participant</title>
		<link>http://ctcresearch.com/wordpress/2009/02/how-to-deal-with-a-domineering-focus-group-participant/</link>
		<comments>http://ctcresearch.com/wordpress/2009/02/how-to-deal-with-a-domineering-focus-group-participant/#comments</comments>
		<pubDate>Tue, 10 Feb 2009 06:20:42 +0000</pubDate>
		<dc:creator>Carol</dc:creator>
				<category><![CDATA[Focus Group]]></category>
		<category><![CDATA[Focus Group Moderator]]></category>
		<category><![CDATA[Qualitative Research]]></category>
		<category><![CDATA[authority]]></category>
		<category><![CDATA[client]]></category>
		<category><![CDATA[control]]></category>
		<category><![CDATA[doctor focus groups]]></category>
		<category><![CDATA[domineering]]></category>
		<category><![CDATA[medical]]></category>
		<category><![CDATA[respondents]]></category>

		<guid isPermaLink="false">http://ctcresearch.com/wordpress/?p=12</guid>
		<description><![CDATA[A recurring problem in focus groups is the tendency of one person to dominate the discussion. If the moderator doesn’t get control of the situation quickly, she loses authority and the client loses the insights of all the other respondents. It is the job of the focus group moderator to establish dominance over the group [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-family: Times New Roman; font-size: medium;">A recurring problem in focus  groups is the tendency of one person to dominate the discussion. If  the moderator doesn’t get control of the situation quickly, she loses  authority and the client loses the insights of all the other respondents.</span></p>
<p><span style="font-family: Times New Roman; font-size: medium;">It is the job of the focus  group moderator to establish dominance over the group while encouraging  all of the participants to speak up and share. </span></p>
<p><span style="font-family: Times New Roman; font-size: medium;">Here is an example of an introduction  I use as a focus group moderator: </span></p>
<p><span style="font-family: Times New Roman; font-size: medium;"><br />
<em>The rule in this group is that everybody participates and nobody  dominates. So if you’re the kind of person who always speaks up right  away, that’s great – I like it when people aren’t afraid to speak  up – but you need to give everyone else a chance to talk. My goal  is to have a balanced discussion so I’m going to make sure the quiet  people speak up and the talkative people back off a little. Please don’t  take this personally as my job is to move the discussion along and get  everybody’s opinion.</em></span></p>
<p><span style="font-family: Times New Roman; font-size: medium;">This kind of introduction is  very effective with professional groups – like doctors – because  it establishes the focus group moderator as an expert and sets the stage<em> </em> for intervention if a respondent tries to dominate. A firm hand from  the beginning sets the stage for a great focus group. </span></p>
]]></content:encoded>
			<wfw:commentRss>http://ctcresearch.com/wordpress/2009/02/how-to-deal-with-a-domineering-focus-group-participant/feed/</wfw:commentRss>
		<slash:comments>384</slash:comments>
		</item>
	</channel>
</rss>

