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

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

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio

Cauvin

Search This Blog