Skip to main content

More Is Not Always Better in Surveys

Having trouble getting responses to your survey?

In a MarketingProfs.com article, Dean Wiltse tells us seven rules for achieving higher online survey response rates. One of the rules is:
Rule #4: More is not always better

Many organizations believe the more questions they ask, the more measurable the results will be. However, the reality is the exact opposite. The more questions asked, the less focused and thoughtful survey responses are and the more survey takers rush to exit.

Instead of asking every possible question under the sun, survey designers should keep the survey focused and to the point.

Survey administrators should bear in mind that to get a solid response rate the number of questions should not exceed 30.
I'm even more radical. I recommend limiting the number of questions to 12 in most cases.

Comments

Joy said…
Good points Roger. I even suggest getting it down to 5 questions if you can.

Sadly, we've done some surveys that give us completely useless results. We could have cut 1/2 the questions and gotten just as much out of them. There is more on this here - (http://www.seilevel.com/messageboard/showthread.php?t=617)
Tue Dec 11, 11:47:00 AM 2007
Post a Comment

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos
32 comments
Read more

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware
8 comments
Read more