Survey Tips from Brian Henderson

Brian Henderson offers us twelve tips on crafting market surveys:

Define the survey's purpose
Keep it short and sweet
Keep it simple
Save demographic questions for last
Keep it specific
Make it consistent
Follow logic
Do a test
Avoid weekends
Send reminders
Entice
Share

Overall, sound advice. I don't completely agree with Henderson about open-ended questions, however:

If you are conducting surveys of large audiences, don't ask open-ended questions that will give you a wide range of answers. That will make it difficult to analyze the results. Questions should be either yes/no or multiple choice.

At Cauvin, Inc., we developed and use our own survey analysis tool that makes it easy to analyze the responses to open-ended questions and correlate them with the answers respondents give to other questions in the survey.

Another tip you need to apply carefully is offering enticements to respondents:

Give your customers a good reason to answer your survey. Offer them a discount or give them a gift certificate. You're asking them to do you a favor, so show your appreciation. Make sure the incentive is somewhat relevant to the customer's interests. You wouldn't give away an extreme-sports vacation to someone who would rather watch them on TV.

The enticement will appeal to certain types of respondents more than others, thereby biasing results. You may think you have a thorough enough understanding of the potential respondents to know that the enticement won't cause significant bias. But then why bother even conducting a survey?

Comments

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

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the four problems that companies face, or are trying to overcome, as they make product decisions . Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions. They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem

Cauvin

Search This Blog