Product research survey: write the result sentence before the questions

A product research survey counts how many people think something. Write the sentence you want to prove first, then the questions, then call people about the answers.

Instant Expert EditorialPublished Updated 5 min read

Write a product research survey only after you can write the sentence it should prove, with a number in it. A product research survey asks the people you want to serve about their needs, how they solve the problem today, which features matter most and what they would pay. It counts opinions and explains little about why, so run it between two sets of conversations: one that tells you what to ask, and one that explains the answers.

If you already have users and want to know whether the product has found its market, use the product-market fit survey instead.

1. Check that your question is about how many

The Nielsen Norman Group describes surveys as the one common research method that is both quantitative and attitudinal: good for measuring how many people hold a view, not for observing what they do. "What percentage of users feel confident their tax return is correct?" suits a survey. "Why are people abandoning their carts?" is better answered by watching people use the product.

Write your sentence first, for example: "Most shop owners who track inventory in spreadsheets rank supplier reordering above sales reports." If you cannot write that sentence, start with interviews.

2. Pick questions by what you want to learn

What you want to learnExample questionWatch out for
How people handle the problem today"How do you currently reorder stock from suppliers?" (list built from interviews, plus "Other")Answer lists invented before any interviews
How often the problem occurs"In the last month, how many times did you run out of a best-selling item?"Vague periods, or asking people to predict the future
Which features matter mostShow a few features at a time and ask which matters most and least (a MaxDiff exercise)Rating every feature "very important" on a 1-5 scale
Reaction to a conceptShort description, then "How well does this fit how you work?"Describing the concept in glowing terms
PriceWhat they pay today, and at what price the idea would seem too expensiveAsking "Would you pay $X?" and trusting the yes
Who they areRole, business size, current toolsPutting these first; Pew advises against demographics near the start unless needed for screening

Price questions need extra care: saying yes to a price in a survey costs the respondent nothing. Researching willingness to pay covers better approaches.

3. Write questions people can answer accurately

Pew Research Center's questionnaire guidance covers most of the rules:

  • Ask one thing at a time. "How satisfied are you with the speed and accuracy of the app?" gives answers you cannot interpret. (Somebody always loves the speed and hates the accuracy.)
  • Keep answer lists short and complete. Pew suggests four or perhaps five choices for most questions, with options that don't overlap and that cover every reasonable answer.
  • Build lists from real answers. Pew notes that researchers sometimes run an open-ended pilot and turn the most common answers into the options.
  • Avoid agree-disagree statements. People tend to agree with any statement (Pew calls it acquiescence bias), so offer a choice between alternatives.
  • Randomize lists without a natural order. People completing surveys themselves tend to pick options near the top.
  • Pretest. Pew calls pretesting essential, especially for new questions. Watch three or four people take the survey and ask what they thought each question meant.

4. Here is a made-up example: bike shops

A company is building inventory software for independent bike shops. It starts with six calls to shop owners and learns that reordering from suppliers causes more trouble than tracking stock.

The survey goes to 150 shop owners. It asks how they reorder today (options taken from the calls), how many times in the past month they ran out of a top seller, a MaxDiff exercise across eight possible features, and what they pay for current tools. The result: a ranked feature list and a count of how common stock-outs are. The team then calls five owners whose answers surprised them.

5. Send it beyond your own customers

Send it to people who match your target customer, including non-users. Existing customers are the easiest to reach but will not tell you why others chose something else.

For consumer products, a panel is the quickest route. Pollfish lists responses from $0.95 each for a short survey, with add-ons in its calculator: $0.50 per response for one screening question, $1.00 for a MaxDiff or conjoint exercise and $0.50 for a price-sensitivity module. It says final pricing varies with length and targeting.

For business products with small, specialized audiences, panels often can't reach enough of the right people. Send it to your own list and pair it with interviews. Validating feature requests covers how to test demand for a specific feature.

6. Call people about the numbers before you build

A survey might show that most respondents rank one feature first. It won't tell you what they would stop using to adopt it, or who signs off on the purchase. Call a few people like your respondents first.

Instant Expert finds people who match a description you write, such as "product managers at B2B software companies who ran a pricing change in the last year." You review who it finds, it sends your invitations and you pay only for calls that get booked. The directory page for product professionals in enterprise SaaS shows the kind of people you can reach.