---
title: "Product survey questions: 24 question-and-follow-up pairs"
description: "Ask these 24 survey questions about a product, from first use to cancellation, each with an open follow-up. Interview when the answers leave out the reason."
url: "https://raconte.ai/en/blog/product-survey-questions"
---

# Product survey questions: 24 question-and-follow-up pairs

Ask these 24 survey questions about a product, from first use to cancellation, each with an open follow-up. Interview when the answers leave out the reason.

November 2, 2026

Godefroy

Updated on November 18, 2026

Key takeaways

*   A product survey counts answers to questions you chose in advance. It can show how often a problem occurs, but it cannot discover a problem missing from the list.
*   Ask about a specific recent action, not whether someone likes the product or might use a feature later.
*   Pair one closed question with one open follow-up when the number needs an explanation. Keep the follow-up optional and tied to the answer.
*   Use a survey to measure a known pattern. Use an interview when you need to understand the steps, context or reason behind it.
*   Raconte runs asynchronous voice interviews for the follow-up. It is not a survey builder.

A product survey can tell you how many people completed setup, which task they came to do, or how often a known problem occurs. It cannot tell you what happened outside the answers you chose. The best product survey questions begin with one product decision, ask about a real moment, and leave room for a follow-up when a score needs an explanation. Below are 24 survey questions about a product, grouped by four moments in the customer’s journey: first use, a blocked task, recurring use and cancellation. Each closed question comes with an open follow-up that asks for the story behind the answer.

## What a product survey can and cannot tell you

A survey is useful when you already know what to measure. A closed question gives people the same set of answer choices, so you can count the responses and compare them across groups or over time. For example, “Did you complete your first project?” is easy to count. It does not tell you whether someone completed it by following the intended workflow, by asking a colleague for help, or by giving up on a feature they did not need.

An open question lets people answer in their own words. That can uncover a reason you did not think to include in a list, though it takes longer to answer and harder to summarize. Nielsen Norman Group makes the same distinction: closed questions work well for quantitative analysis, while [open-ended questions in user research](https://www.nngroup.com/articles/open-ended-questions/) can surface unexpected motivations and experiences.

So decide what you need before you write questions. If the team needs a reliable count, use answer options. If the team needs to find out why a task failed, ask for a story. When both matter, pair the two formats instead of asking a rating to do both jobs.

A short survey also has a boundary. It captures what people report at one moment, not every step they took. Product analytics can answer some factual questions more accurately, such as whether someone used a feature. Ask people when you need the context behind that action, or when the action itself is not recorded.

## Survey questions about a product, moment by moment

The same question means different things depending on when you ask it. In the first week, the answer to “Where did you stop?” names a setup step. Six months later, it more often describes a task that stopped working. So the 24 pairs are grouped by the moment you send the survey: first use, a blocked task, recurring use and cancellation.

### Product survey questions for first use

Ask these after someone has had a chance to try the product. A question sent before the first task can only measure expectations. Pick the questions that connect to a decision your team can still change.

What you want to learn

Closed question

Open follow-up

The person’s first goal

Which task brought you to \[product\]? Choose one: \[task A\], \[task B\], \[task C\], another task.

Tell me about the first thing you tried to do after signing in.

Whether they reached the goal

Have you completed \[task\] in \[product\]? Yes / Partly / No / I have not tried.

What happened the last time you tried to complete it?

A step where people stop

Where did you stop? \[Step A\] / \[Step B\] / \[Step C\] / I completed it.

What were you looking for at that point?

Missing information

Did you find the instructions you needed? Yes / Partly / No / I did not look for instructions.

What did you search for, and where did you look?

A first useful result

Have you used the result of \[task\] in your work? Yes / Not yet / The result was not useful.

What did you do with the result after you got it?

Permission to follow up

May we contact you about this answer? Yes / No.

If yes: what would be useful for us to understand?

The answer options need to fit your product and your decision. If people can do two tasks at once, let them select more than one. Include “another task” when the list might miss a real use case, and offer “I have not tried” when the question assumes an action that some people have not taken.

Avoid “Was setup easy?” as your only onboarding question. A “no” records difficulty, but a “yes” can hide an awkward workaround. “What did you try to do first?” invites a concrete account. If you need a score as well, ask it separately, then show the open follow-up only to people whose answer needs explanation.

### Product survey questions for a blocked task

A task failure gives you a useful moment to ask, but the wording should not blame the person or tell them what the product did wrong. Start by asking what they were trying to do. Then find the step and the workaround.

What you want to learn

Closed question

Open follow-up

The task behind the failure

Were you trying to \[task A\], \[task B\] or something else?

What were you trying to get done when you got stuck?

Whether the person reached a result

Did you finish the task? Yes / Partly / No.

Walk me through what happened from the moment you started.

The point of friction

Where did you stop? \[Step A\] / \[Step B\] / \[Step C\] / Somewhere else.

What did you expect to happen at that step?

The workaround

Did you find another way to finish? Yes / No / I am still trying.

What did you do instead?

The consequence

Did the problem delay or change your work? Yes / No / Not sure.

What did you have to postpone, change or ask someone else to do?

Whether the issue repeated

Has this happened before? This is the first time / Once before / Several times.

Tell me about the last other time it happened.

Ask about one thing at a time. “Did you find the feature and was it easy to use?” combines discovery and usability, so a single answer cannot tell you which one failed. Separate the questions if each answer would lead to a different product change.

A survey can count how many people pick each failure point. If the answer is “somewhere else,” read the written response before adding another choice. A single unusual answer may be a one-off, or it may reveal a missing step in the workflow. Check the event data when it can confirm whether the task succeeded, and use the answer to understand what the product log cannot show.

### Product survey questions for recurring use

When a person returns to a product, ask about the job they came back to do. A general satisfaction score can track a trend, but the score alone does not name the feature or circumstance behind it. The [customer satisfaction survey example](/en/blog/customer-satisfaction-survey) explains what those scores measure and where they stop being useful.

What you want to learn

Closed question

Open follow-up

The job behind repeat use

What did you use \[product\] for most recently? \[Task A\] / \[Task B\] / \[Task C\] / Another task.

Tell me about the last time you used it for that task.

Whether a feature is part of the workflow

Have you used \[feature\] in the past \[period\]? Often / Sometimes / Once / Never.

What were you trying to do the last time you used it?

A measure of satisfaction

How satisfied were you with \[specific task\] today? 1 (very dissatisfied) to 5 (very satisfied).

What is the main reason for that score?

A recurring obstacle

How often does \[specific obstacle\] happen? Never / Once / Monthly / Weekly or more.

Think of the most recent time. What happened?

A change in behaviour

Compared with \[period\], do you use \[product\] more often, less often or about as often?

What changed in the way you use it?

A choice between known priorities

Which improvement would help your work most? \[A\] / \[B\] / \[C\] / None of these.

What would that improvement let you do that is hard today?

Use a fixed time frame in every option. “Often” means something different to each person, while “three or more times in the past month” gives respondents the same reference. Keep the wording and scale stable when you intend to compare results over time.

Be careful with feature-request questions. “What feature should we build next?” asks people to design the solution. Ask about the work instead: “What were you trying to do?” and “What did you do when that failed?” If several requests point to the same obstacle, the team can compare the proposed solutions against the problem people actually experienced.

A list of priorities only ranks the options you supplied. Include “none of these” when it is a valid answer, and do not treat the leading option as a roadmap order without checking who answered and why. The [customer feedback form templates](/en/blog/customer-feedback-form) show how to keep a short form tied to one specific moment.

### Product survey questions for cancellation

A cancellation survey should take little effort. The decision to leave may have built up over weeks, so the final click is only one point in the story. Ask for a broad reason first, then invite a follow-up with people who agree to share more.

What you want to learn

Closed question

Open follow-up

The main reason

What is the main reason you are cancelling? Price / Missing capability / Hard to use / No longer needed / Another reason.

What happened that made this the main reason?

The first moment of doubt

When did you first consider leaving? This week / This month / Earlier.

Tell me about the first time you thought the product might not work for you.

A specific turning point

Did one event lead to your decision? Yes / No / Not sure.

What happened around the time you decided to cancel?

The alternative

Are you moving to another product? Yes / No / I have not decided.

What will you use instead, and what made you choose it?

A possible change

Would a change to \[specific issue\] affect your decision? Yes / No / Not sure.

What would have needed to happen for you to stay?

Permission to follow up

May we contact you about your experience? Yes / No.

What part of your experience would you like us to understand?

Do not promise that a requested feature would have kept the customer. The answer describes what the person says now, after deciding to leave. Compare several answers with product usage and support history, then look for repeated moments rather than treating one response as the whole explanation.

## How to write product survey questions people can answer

Start with the decision, not a list of interesting topics. If your team cannot name what it would do differently for each possible answer, remove the question. This keeps a survey from becoming a catch-all form that collects feedback nobody has time to read.

Use these checks before sending it:

*   Ask about one task, one moment or one judgement in each question.
*   Use neutral language. “What was frustrating about our new dashboard?” assumes the dashboard frustrated the respondent. “How did you use the dashboard?” leaves room for a different answer. A leading question is only one of the [six kinds of biased survey question to rewrite before sending](/en/blog/biased-survey-questions).
*   Prefer something recent and specific to a prediction. “What did you do the next time?” gives you a past action. “Would you use this feature?” records an intention.
*   Keep answer choices mutually exclusive and cover the cases people can reasonably give. Add “other” or “not applicable” when the list needs it.
*   Use a scale only when you need a comparable measure, and label its ends. Do not ask someone to rate several unrelated things in one question.
*   Make every open text field optional when a person can complete the survey without it. Say why you ask and who will read the answer.
*   Check the survey on a phone and ask a few people to complete it before you send it widely. Watch for questions they interpret differently than you intended.

Open text boxes are not a reliable substitute for a conversation. People can skip them, give a short answer, or name a concern that needs another question. Nielsen Norman Group recommends open-ended questions when researchers want participants to explain an experience, and closed questions when they need limited responses to count ([NN/g](https://www.nngroup.com/articles/open-ended-questions/)). PostHog also advises product teams to avoid leading wording and make each question specific to a goal in its [product survey question-writing advice](https://posthog.com/product-engineers/product-survey-questions).

![Examples of follow-up questions that turn a closed answer into a concrete story](/.netlify/images?url=_astro%2Fclosed-to-open-en.Cqbi0XhX.jpg&w=1376&h=768&dpl=6b031bf5959953076155d961)

## When a product survey needs an interview

Use the survey when you have a known question and need to measure how often a response occurs. Use an interview when the team cannot yet explain the response, needs to follow the sequence of a task, or wants to hear about a case it did not anticipate.

Need

Survey

Interview

Count a known behaviour or rating

A good fit

Useful for context, not the fastest way to count a large group

Find an unexpected reason

Limited by the options and answers people choose

A good fit, because the interviewer can ask what happened next

Compare the same measure across releases

A good fit when wording and sample stay stable

Harder, because conversations vary

Watch someone use a product

Not enough on its own

A moderated usability test is a better fit

Hear from many people asynchronously

Short forms are efficient

Voice interviews can add depth when calendar scheduling is the bottleneck

An interview does not replace product analytics or every survey. Use analytics for recorded actions, a survey for a comparable measure, and an interview for the explanation or context. For questions about a new problem rather than a known product journey, [customer discovery interviews](/en/blog/customer-discovery-interviews) help teams test what customers do before they build a solution.

```mermaid
graph TD
  A["A question has a known answer set"] --> B["Use a survey to count it"]
  B --> C{"Does the result need an explanation?"}
  C -->|"No"| D["Compare the measure over time"]
  C -->|"Yes"| E["Invite a follow-up interview"]
  E --> F["Ask what happened, then probe for an example"]
```

Raconte runs asynchronous voice interviews. You write an interview brief, send people a link and receive transcripts, audio, summaries and sentiment by message. It is a voice interview tool for follow-up research, while product surveys need a separate survey platform. When the open answer on a product survey leaves out the reason, or a team needs to hear how a task unfolded, [Raconte](/en) gives you a way to ask follow-up questions without coordinating a live meeting. Every organisation can start with 60 interview minutes each month at no cost.

Ready to launch your first interview?

Describe your interview, share the link: an AI agent runs it by voice with each participant. You get back the transcript and analysis.

[Try for free](/login)

## Continue reading

[![Customer feedback form: 4 templates by moment](/.netlify/images?url=_astro%2Fthumbnail.BylD6fd7.jpg&w=1200&h=630&dpl=6b031bf5959953076155d961)

September 27, 2026

## Customer feedback form: 4 templates by moment

Four customer feedback form templates to copy, for after a purchase, a support ticket, onboarding and a cancellation, with the reason for every question.



](/en/blog/customer-feedback-form)[![Customer satisfaction survey: an example and its limits](/.netlify/images?url=_astro%2Fthumbnail.BVaPkpjh.jpg&w=1376&h=768&dpl=6b031bf5959953076155d961)

August 19, 2026

## Customer satisfaction survey: an example and its limits

A customer satisfaction survey template you can copy, what every question tells you, and the four blind spots of a score out of 10.



](/en/blog/customer-satisfaction-survey)[![Customer discovery interviews: method and 15 questions](/.netlify/images?url=_astro%2Fthumbnail.w6TuGzWB.jpg&w=1376&h=768&dpl=6b031bf5959953076155d961)

September 24, 2026

## Customer discovery interviews: method and 15 questions

What customer discovery is, its four phases, 15 questions that keep people on facts, and how to hold a weekly interview cadence without drowning in logistics.



](/en/blog/customer-discovery-interviews)
