<?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: Ask a Stupid Question</title>
	<atom:link href="http://blog.crowdflower.com/2009/12/ask-a-stupid-question/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.crowdflower.com/2009/12/ask-a-stupid-question/</link>
	<description></description>
	<lastBuildDate>Wed, 07 Dec 2011 22:49:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Ben Hyde</title>
		<link>http://blog.crowdflower.com/2009/12/ask-a-stupid-question/#comment-2079</link>
		<dc:creator>Ben Hyde</dc:creator>
		<pubDate>Fri, 08 Jan 2010 19:39:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2009/12/ask-a-stupid-question/#comment-2079</guid>
		<description>I always harbored a suspicion that survey respondents apply one of four heuristics.  Pick randomly, pick min or max, and the cognitively expensive option being authentic.

Then there is the eternal authentic/strategic problem.  If the survey respondent knows that his votes have an effect then he spend his tokens very differently.   I had a small survey, designed to pick a winning paper, blow up on me once because one of the respondents was brilliantly strategic - turning all the dials to max for his preference and to min for the others.

The error I find most frustrating though is when the survey designer lacks a model of what the distribution of is, so his multiple choice is unable to capture a good signal for the parameters of the actual distribution.  e.g. is distirbution zip or normal</description>
		<content:encoded><![CDATA[<p>I always harbored a suspicion that survey respondents apply one of four heuristics.  Pick randomly, pick min or max, and the cognitively expensive option being authentic.</p>
<p>Then there is the eternal authentic/strategic problem.  If the survey respondent knows that his votes have an effect then he spend his tokens very differently.   I had a small survey, designed to pick a winning paper, blow up on me once because one of the respondents was brilliantly strategic &#8211; turning all the dials to max for his preference and to min for the others.</p>
<p>The error I find most frustrating though is when the survey designer lacks a model of what the distribution of is, so his multiple choice is unable to capture a good signal for the parameters of the actual distribution.  e.g. is distirbution zip or normal</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eliot</title>
		<link>http://blog.crowdflower.com/2009/12/ask-a-stupid-question/#comment-2077</link>
		<dc:creator>Eliot</dc:creator>
		<pubDate>Fri, 08 Jan 2010 14:52:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2009/12/ask-a-stupid-question/#comment-2077</guid>
		<description>Norbert Schwarz (survey research expert at Univ. of Michigan) has published a number of scientific papers documenting this effect.  People do use the response scale as a cue indicating what is typical or normal, and place themselves accordingly.  The same effect holds for relatively objective questions (hours per day online, number of headaches in an average month) and subjective questions (how satisfied are you with your life).</description>
		<content:encoded><![CDATA[<p>Norbert Schwarz (survey research expert at Univ. of Michigan) has published a number of scientific papers documenting this effect.  People do use the response scale as a cue indicating what is typical or normal, and place themselves accordingly.  The same effect holds for relatively objective questions (hours per day online, number of headaches in an average month) and subjective questions (how satisfied are you with your life).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mikael M</title>
		<link>http://blog.crowdflower.com/2009/12/ask-a-stupid-question/#comment-2071</link>
		<dc:creator>Mikael M</dc:creator>
		<pubDate>Thu, 07 Jan 2010 20:47:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2009/12/ask-a-stupid-question/#comment-2071</guid>
		<description>Interesting experiment! How much did it cost?</description>
		<content:encoded><![CDATA[<p>Interesting experiment! How much did it cost?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michael</title>
		<link>http://blog.crowdflower.com/2009/12/ask-a-stupid-question/#comment-1867</link>
		<dc:creator>michael</dc:creator>
		<pubDate>Wed, 23 Dec 2009 03:15:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2009/12/ask-a-stupid-question/#comment-1867</guid>
		<description>Would there really be that many problems with questions like this:

How many time do you spend online per weekday?
___ hours and ___ minutes online on weekdays

And how many time do you spend online per day on weekends?
___ hours and ___ minutes online per days on weekends

I really can’t imagine that. Throw up an error if the participant enters any letters. If the value is bigger than 24 hours or 60 minutes you can throw it out right away. (You have to be a bit careful with the minutes because from my experience some like to leave the hours blank and enter something like 90 minutes or 120 minutes.) All an easy enough fix.

If those open ended questions get any more complicated you will get into trouble, that’s for sure. But as long as it’s as easy as this, I doubt there will be many problems. And from what I know – talking to other communication studies researchers (who ask these types of questions all the time) – you actually get very accurate time estimates. No even asking for minutes is a fruitless exercise. Measurements of time spent online or in front of the TV match up pretty good to the self reported data (i.e. less than one hour difference, hence minutes matter, but you could probably leave them out if you wanted to make it easier).

Still, I can see you point about complexity. But that also depends on the respondents. I’ve seen people answering this question and some think long and hard and really try to come up with an accurate estimate. Others will just pull a number out. I would guess that scales are easier for the second group. But not exactly for the first. Scales might be even harder for them: they can’t just write their estimate in but have to fit it into categories.

(I like you point that scales help quantify things. But open ended questions can help there, too, albeit in a bit more subtle and maybe a bit less helpful way. When asking how often the participants go to the cinema or opera the researcher should first get a feeling for the average in the population and then decide whether to ask for visits per week, month or year.)</description>
		<content:encoded><![CDATA[<p>Would there really be that many problems with questions like this:</p>
<p>How many time do you spend online per weekday?<br />
___ hours and ___ minutes online on weekdays</p>
<p>And how many time do you spend online per day on weekends?<br />
___ hours and ___ minutes online per days on weekends</p>
<p>I really can’t imagine that. Throw up an error if the participant enters any letters. If the value is bigger than 24 hours or 60 minutes you can throw it out right away. (You have to be a bit careful with the minutes because from my experience some like to leave the hours blank and enter something like 90 minutes or 120 minutes.) All an easy enough fix.</p>
<p>If those open ended questions get any more complicated you will get into trouble, that’s for sure. But as long as it’s as easy as this, I doubt there will be many problems. And from what I know – talking to other communication studies researchers (who ask these types of questions all the time) – you actually get very accurate time estimates. No even asking for minutes is a fruitless exercise. Measurements of time spent online or in front of the TV match up pretty good to the self reported data (i.e. less than one hour difference, hence minutes matter, but you could probably leave them out if you wanted to make it easier).</p>
<p>Still, I can see you point about complexity. But that also depends on the respondents. I’ve seen people answering this question and some think long and hard and really try to come up with an accurate estimate. Others will just pull a number out. I would guess that scales are easier for the second group. But not exactly for the first. Scales might be even harder for them: they can’t just write their estimate in but have to fit it into categories.</p>
<p>(I like you point that scales help quantify things. But open ended questions can help there, too, albeit in a bit more subtle and maybe a bit less helpful way. When asking how often the participants go to the cinema or opera the researcher should first get a feeling for the average in the population and then decide whether to ask for visits per week, month or year.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Petti</title>
		<link>http://blog.crowdflower.com/2009/12/ask-a-stupid-question/#comment-1860</link>
		<dc:creator>Bill Petti</dc:creator>
		<pubDate>Tue, 22 Dec 2009 19:34:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2009/12/ask-a-stupid-question/#comment-1860</guid>
		<description>One major advantage that comes immediately to mind is that scale questions don&#039;t require analysts to spend additional time coding answers before commencing with their analysis. While open-ended questions may avoid the issue of satisficing (which I am not convinced they do--respondents could easily reference their own subjective scale or notions), they do place an additional burden on the analyst.  For short, small-n surveys this isn&#039;t that big of an issue.  However, once you start scaling up in terms of n and the number of questions it can become problematic.  Once you get into coding there are all sorts of issues that can arise (issues of subjectivity and bias, data entry errors, etc). Some crowdsourcing applications like Crowdflower may provide a convenient and reliable platform for coding, but at some level researchers will always have to make an intelligent trade-off between scale and open-ended questions.</description>
		<content:encoded><![CDATA[<p>One major advantage that comes immediately to mind is that scale questions don&#8217;t require analysts to spend additional time coding answers before commencing with their analysis. While open-ended questions may avoid the issue of satisficing (which I am not convinced they do&#8211;respondents could easily reference their own subjective scale or notions), they do place an additional burden on the analyst.  For short, small-n surveys this isn&#8217;t that big of an issue.  However, once you start scaling up in terms of n and the number of questions it can become problematic.  Once you get into coding there are all sorts of issues that can arise (issues of subjectivity and bias, data entry errors, etc). Some crowdsourcing applications like Crowdflower may provide a convenient and reliable platform for coding, but at some level researchers will always have to make an intelligent trade-off between scale and open-ended questions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aaron</title>
		<link>http://blog.crowdflower.com/2009/12/ask-a-stupid-question/#comment-1854</link>
		<dc:creator>aaron</dc:creator>
		<pubDate>Mon, 21 Dec 2009 18:07:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2009/12/ask-a-stupid-question/#comment-1854</guid>
		<description>Thanks for the feedback, everyone!

Michael - your comment illustrates a great point that deserves a lot more discussion: scale response questions may &lt;strong&gt;not&lt;/strong&gt; be the best way to get the information you want on a given topic. That said, there are a few reasons I can think of why you still might want to use scales in certain situations:


&lt;blockquote&gt;(1) They&#039;re fast for respondents. Every question you put on a survey is a demand on your respondents&#039; time and patience. A multiple choice scale makes life a tiny bit easier and quicker for respondents, therefore making a tiny bit more likely that they will answer the question and complete the rest of your survey.&lt;/blockquote&gt;

&lt;blockquote&gt;(2) They eliminate a lot of data entry errors. If you leave a text box in your survey, somebody will invariably tell you that they spend &quot;1q0&quot; hours online per day. Was that supposed to be 10? Did they accidentally hit 1 instead of the tab key and therefore intend to enter a zero? If you don&#039;t know for sure, you (the survey administrator) will need to throw out their response. Depending on the study, missing data may raise really big problems with your sample and your ability to generalize about the population you&#039;re researching.&lt;/blockquote&gt;

&lt;blockquote&gt;(3) They help respondents quantify things: the fact that people can use scales to dis-orient themselves in relation to a range of responses (as the people with the low scale did in my experiment) implies that they can also use scales to orient themselves accurately. For example, I don&#039;t regularly quantify the amount of time I spend on public transportation each week. Assuming that a researcher has done his/her homework in designing the scale responses, the scale may actually help me provide a more accurate answer than I would have on my own.&lt;/blockquote&gt;

&lt;blockquote&gt;(4) They make impolite questions or unusual responses seem safe. Your example about the impropriety of asking people about their income or age in Germany is exactly what I have in mind here. In addition, a well-designed scale can sometimes help people feel more comfortable identifying themselves as outliers on a sensitive issue. Again, this may help more people respond to a question and give accurate answers.&lt;/blockquote&gt;


I think these are all great reasons why the particulars of the study, the population, and the topics of interest should drive the research design process. Every type of question has characteristics that may look like limitations in a given set of circumstances, but strengths in another.</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback, everyone!</p>
<p>Michael &#8211; your comment illustrates a great point that deserves a lot more discussion: scale response questions may <strong>not</strong> be the best way to get the information you want on a given topic. That said, there are a few reasons I can think of why you still might want to use scales in certain situations:</p>
<blockquote><p>(1) They&#8217;re fast for respondents. Every question you put on a survey is a demand on your respondents&#8217; time and patience. A multiple choice scale makes life a tiny bit easier and quicker for respondents, therefore making a tiny bit more likely that they will answer the question and complete the rest of your survey.</p></blockquote>
<blockquote><p>(2) They eliminate a lot of data entry errors. If you leave a text box in your survey, somebody will invariably tell you that they spend &#8220;1q0&#8243; hours online per day. Was that supposed to be 10? Did they accidentally hit 1 instead of the tab key and therefore intend to enter a zero? If you don&#8217;t know for sure, you (the survey administrator) will need to throw out their response. Depending on the study, missing data may raise really big problems with your sample and your ability to generalize about the population you&#8217;re researching.</p></blockquote>
<blockquote><p>(3) They help respondents quantify things: the fact that people can use scales to dis-orient themselves in relation to a range of responses (as the people with the low scale did in my experiment) implies that they can also use scales to orient themselves accurately. For example, I don&#8217;t regularly quantify the amount of time I spend on public transportation each week. Assuming that a researcher has done his/her homework in designing the scale responses, the scale may actually help me provide a more accurate answer than I would have on my own.</p></blockquote>
<blockquote><p>(4) They make impolite questions or unusual responses seem safe. Your example about the impropriety of asking people about their income or age in Germany is exactly what I have in mind here. In addition, a well-designed scale can sometimes help people feel more comfortable identifying themselves as outliers on a sensitive issue. Again, this may help more people respond to a question and give accurate answers.</p></blockquote>
<p>I think these are all great reasons why the particulars of the study, the population, and the topics of interest should drive the research design process. Every type of question has characteristics that may look like limitations in a given set of circumstances, but strengths in another.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michael</title>
		<link>http://blog.crowdflower.com/2009/12/ask-a-stupid-question/#comment-1853</link>
		<dc:creator>michael</dc:creator>
		<pubDate>Mon, 21 Dec 2009 03:31:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2009/12/ask-a-stupid-question/#comment-1853</guid>
		<description>Why use a scale at all? I would make those types of questions always open ended. Anyone who takes the survey has to think about how many hours they spend online anyway. That’s the first step. The second is fitting their estimate in one of the categories. Seems like unnecessary work for the participants.

(Well, actually I would also make it two questions. One for weekdays, another for weekends. Otherwise the participants might be forced to do averaging in their heads – something which our programs are much better at.)

Pretty much the only time where I would use a scale in a case where the participant could also just give a number is income. And that’s only because asking directly for the income is considered very impolite (in Germany). A few years ago you would have to add age to that, but that has already changed and the thing with the income will, too.</description>
		<content:encoded><![CDATA[<p>Why use a scale at all? I would make those types of questions always open ended. Anyone who takes the survey has to think about how many hours they spend online anyway. That’s the first step. The second is fitting their estimate in one of the categories. Seems like unnecessary work for the participants.</p>
<p>(Well, actually I would also make it two questions. One for weekdays, another for weekends. Otherwise the participants might be forced to do averaging in their heads – something which our programs are much better at.)</p>
<p>Pretty much the only time where I would use a scale in a case where the participant could also just give a number is income. And that’s only because asking directly for the income is considered very impolite (in Germany). A few years ago you would have to add age to that, but that has already changed and the thing with the income will, too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete Michaud</title>
		<link>http://blog.crowdflower.com/2009/12/ask-a-stupid-question/#comment-1841</link>
		<dc:creator>Pete Michaud</dc:creator>
		<pubDate>Wed, 16 Dec 2009 13:33:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2009/12/ask-a-stupid-question/#comment-1841</guid>
		<description>Interesting work. I&#039;m about to implement product satisfaction surveys across multiple markets, and this was good food for thought. Keep it up 8)</description>
		<content:encoded><![CDATA[<p>Interesting work. I&#8217;m about to implement product satisfaction surveys across multiple markets, and this was good food for thought. Keep it up 8)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

