Customer discovery survey template: 12 questions to use
A copyable customer discovery survey template focused on recent behavior, current workflows, pain severity, workarounds, and switching evidence.
A useful customer discovery survey collects evidence of recent behavior, not votes for an idea. It asks respondents to reconstruct a real event, explain their current workflow, and show whether the problem has been costly enough to prompt a workaround, purchase, or attempted change.
The 12-question template below is designed as a mixed conversational survey. Structured questions make responses comparable; open questions preserve the details that explain the numbers. Replace the bracketed text before launch, then pilot the survey with two or three people from the intended audience.
Customer discovery survey template
Use one specific process or task throughout the survey. "Approving vendor invoices over $5,000" will produce better recall than a broad phrase like "financial operations."
| # | Type | Question | Setup |
|---|---|---|---|
| 1 | Multiple choice | In the past 30 days, which best describes what you personally did in [specific process or task]? | Offer: completed it myself; completed it with someone; reviewed or approved it; managed but did not take part; received the output only; did not encounter it. Qualify only roles with the firsthand experience your study needs. |
| 2 | Multiple choice | In the past 30 days, on about how many days did you personally do this task? | Offer: 0; 1; 2–3; 4–7; 8 or more. Screen out 0; consider whether one instance is enough for the research goal. |
| 3 | Open text or AI question | Think about the most recent time you did this task. What were you trying to accomplish, and what happened step by step? | Ask at most two follow-ups about actors, tools, handoffs, duration, and outcome. Stay with the specific incident. |
| 4 | Multiple choice, select all | Which of these were part of how you completed the task? | Include manual documents or email, third-party products, internal tools, outside services, help from another person, and no consistent approach. Enable Other. |
| 5 | Open text or AI question | Which parts, if any, required the most effort, created uncertainty, or had to be repeated? What happened at those points? | Permit a genuine "none" answer. Do not ask what was frustrating, because that presumes frustration. |
| 6 | Multiple choice | In the past 30 days, how often did that issue occur when you performed the task? | Offer: never; rarely; sometimes; most times; every time; not sure. Skip issue-specific questions when the respondent answers never. |
| 7 | Rating scale | Over the past 30 days, how much did issues with this process interfere with getting the intended result? | Use a 1–5 scale from Not at all to Completely, with Moderately at the midpoint. |
| 8 | Open text or AI question | When did the issue occur, and when did it not? What was different? | Use one follow-up to identify conditions, exceptions, or frequency without asking the respondent to invent a cause. |
| 9 | Open text or AI question | In the past six months, what, if anything, have you changed, bought, built, or asked for to improve this process? What happened with the most recent attempt? | Probe for effort and outcome. A search, trial, budget request, or workaround is stronger evidence than stated interest alone. |
| 10 | Open text | The most recent time the issue occurred, what consequences followed, if any? | Ask for observed time, delay, rework, money, or risk. Do not ask the respondent to estimate hypothetical value. |
| 11 | Multiple choice | In the past six months, which best describes whether you considered changing how you handle this task? | Offer a ladder from did not consider through researched, tried, requested budget, purchased, or implemented. Allow Not applicable. |
| 12 | Open text plus contact permission | Is there anything else about how you handle this task that would help us understand your day-to-day? May we contact you for a follow-up conversation? | Keep the research response separate from optional contact details and state how contact information will be used. |
Copy the question wording, but adapt the qualification rule, recall window, answer choices, and terminology to the audience. A weekly task may need a 30-day window; an annual procurement process may need 12 months.
Logic to add before launch
The first two questions should qualify recent, firsthand experience. Someone who only manages a team may be the right respondent for an approval workflow and the wrong respondent for hands-on usability research. Decide that before collecting data.
If a respondent reports no issue in question 5 or selects Never in question 6, skip the detailed issue questions and keep their workflow response. A painless workflow is useful evidence. It shows the conditions under which the problem does not appear and protects the study from forcing every answer into the problem hypothesis.
Keep follow-ups limited. Two probes on the recent event and one on a high-value workaround answer usually produce more useful detail than turning every open response into a long exchange. AI follow-up questions explains how to set that depth in Versive.
For more on qualification rules, read how to write screener questions that actually screen.
Why these questions work
The template moves from evidence with the least interpretation to evidence with more interpretation:
- Recent participation: did this person actually perform the task?
- A specific event: what did they do, in what order, and with which tools?
- Observed friction: where did effort, repetition, or uncertainty occur?
- Frequency and severity: is the issue recurring and does it interfere with the outcome?
- Action already taken: has the respondent spent time, money, or political capital trying to change it?
- Consequences: what followed when the issue occurred?
This order avoids asking a participant to agree that a problem is important before they have described any evidence for it. It also separates a frequent annoyance from a rarer problem with serious consequences.
Questions to leave out
Avoid questions that produce enthusiasm without behavioral evidence:
- "Would you use a product that solved this?"
- "How much would you pay for this idea?"
- "Do you think this is a major problem?"
- "Which of these features would you want?"
- "Would an AI-powered solution make your work easier?"
Respondents can answer all five without having the problem, owning the budget, or changing their behavior. If you need to test a specific solution, finish discovery first and run a separate concept test with realistic alternatives, trade-offs, and pricing context.
Survey or interview?
Use this survey when you already know the process you need to study and want the same core evidence from a broader group. Use an interview when the workflow is still poorly understood, the participant segment is narrow, or unexpected details are more valuable than consistent measurement.
A conversational survey is a practical middle ground. Everyone receives the same structured questions, while an AI moderator can probe a recent incident or workaround without requiring a researcher to attend every session. Keep the probes bounded so one expressive participant does not receive a substantially different study from everyone else.
If depth matters more than survey consistency, use the complete customer discovery interview template.
How to analyze the responses
First, separate respondents by relevant segment: role, company size, frequency of the task, or another attribute chosen before analysis. Averages across two different workflows can hide the pattern in both.
Then connect the structured answers to the open evidence. Compare severity and frequency with the described event, attempted solutions, and consequences. A high rating with no recalled example is weaker evidence than a moderate rating paired with repeated workarounds and a recent failed purchase.
Code the open responses into workflows, friction points, triggers, workarounds, and consequences. Keep every theme linked to the source response and inspect contradictory cases before summarizing. How to analyze open-ended survey responses with AI covers that workflow in detail.
Build it in Versive
In Versive, combine Multiple Choice, Rating Scale, Open Text, and AI Questions in one study. Use screen-out logic on the qualification questions, skip logic around issue-specific follow-ups, and a small follow-up cap on the conversational questions. Participants can answer by text, voice, or video, and the results combine charts for structured questions with themes and attributed quotes for open responses.
Start from the customer discovery interview template when you want the longer conversational version, or paste the research goal and this question structure into the study assistant to create a shorter survey draft. Review every screen-out rule and answer option before launching.
Frequently asked questions
What questions should a customer discovery survey ask?
Ask about a recent instance of the problem, the steps and tools involved, where effort or uncertainty appeared, how often it happens, what consequences followed, and what the respondent has already tried to change. Ask about a proposed solution only at the end, if at all.
How long should a customer discovery survey be?
Aim for about 10 minutes for a mixed survey with structured and open-ended questions. If AI follow-ups or voice answers make the study more interview-like, 12 to 15 minutes can be reasonable when participants know the expected time before starting.
Is a customer discovery survey the same as an interview?
No. A survey applies a consistent structure across more people, while an interview can follow unexpected details in depth. A conversational survey sits between them by keeping the same core questions and using limited follow-ups on open answers.
Should a customer discovery survey describe the product idea?
Usually not until the end. Describing a solution early can make participants speculate about your idea instead of reporting what they currently do, what breaks, and whether the problem has been important enough for them to act on.
How many customer discovery survey responses do I need?
There is no useful universal number. Analyze one well-defined segment at a time, watch whether new workflows and workarounds are still appearing, and use a larger sample when you need stable comparisons between subgroups or quantitative estimates.
Full reference
Versive study templates
Keep reading
Card sorting: a practical guide
A practical guide to card sorting for UX research: open vs. closed sorts, card and participant counts, and how to analyze the results.
Concept testing methods, compared
Concept testing methods compared: monadic vs. sequential monadic vs. comparative, qualitative vs. quantitative, and how to run each.
Moderated vs. unmoderated usability testing
Moderated vs. unmoderated usability testing: the classic trade-offs, and how AI moderation now blurs the line between them.
