Usertick
Start free
Product survey questions

Product questions that tell you what to build and what to fix

Ask users how the product fits their work, from what they use it for to what breaks and what they would build next. Each question below comes with when to ask it and what the answer tells you.

Get started freeAll topics

What product feedback survey questions tell you

Product feedback survey questions ask users how the product works for them: what they use it for, what they like, what confuses them, what breaks and what is missing. Usage data shows what people click, and these answers show why, which is what a roadmap needs.

Ask inside the product with a popup or side button once a user has worked with it for a while, or by email to active accounts. Pick four to six questions built around one goal, such as product fit, quality or the next feature, and keep the rest for another round.

Each written answer gets a type such as bug, idea or complaint, plus a category, a theme and a sentiment, so bug reports and feature ideas separate on their own. On every plan, workflows post to Slack or Microsoft Teams, and they can create issues in Jira or Linear.

TextStarsYes / NoDropdownMultiple choice
Questions
18
Best asked
After a week or two of regular use
Industry
Any business
Where to find them
From library in the Usertick survey editor, on every plan

The 18 product questions, with when to ask each

Grouped by what they tell you. Use them as they are or change the wording.

Product fit and value

Start here to learn how much the product matters to users and whether it delivers what they expected for the price.

  1. 11Multiple choice

    How would you feel if you could no longer use this product?

    The product fit question. Results shows each share in a donut, so follow the share who would be very disappointed over time and read what those users like most.

  2. 02Yes / No

    Did the product work the way you expected?

    A quick check on expectations. Add logic so only users who answer No see the question on what was confusing, and read those answers first.

  3. 03Stars

    How would you rate the value you get for the price?

    Value for money in five stars. Choose the lighter users in the usage question to see whether their rating differs from the rating of daily users.

  4. 10Stars

    How would you rate the quality of the product?

    Rates the quality of the product in five stars. Follow it release by release, and compare it with the stability rating to separate polish from reliability.

  5. 12Text

    What is the main benefit you get from the product?

    The main benefit in the user's own words. Ask it of users who would be very disappointed without the product, and reuse their wording on your website.

How people use it

These describe how often people use the product and what they use it for, so you can read every other answer by type of user.

  1. 04Dropdown

    How often do you use the product?

    How often a user opens the product. Results shows the share of each answer, and selecting one filters the whole page, so you can read every other answer from daily users alone.

  2. 05Text

    What do you mainly use the product for?

    What users mainly rely on the product for. The themes show the main jobs people do with it, which are the ones to protect when you change things.

  3. 06Text

    Which part of the product do you like most?

    The part of the product users like most. Keep it next to the improvement question, so a redesign doesn't remove what people value.

  4. 09Text

    What were you using before you found us?

    What users had before they found you. The answers name your real competitors and the habits users bring with them, which helps both onboarding and positioning.

  5. 13Text

    Who else on your team would benefit from this?

    Who else on the team could use the product. Ask it once a user is active, and pass the teams or roles they name to whoever handles account growth.

What gets in the way

Ask about confusion, gaps and bugs together, and send what users report to the team that fixes it.

  1. 07Text

    Which part of the product is confusing?

    Names the part that confuses users. Ask it inside the product near the feature in question, and pass recurring themes to design and to whoever writes your help pages.

  2. 08Text

    What is missing that you expected to find?

    What users expected to find and didn't. Each answer gets a type, so missing features show up as ideas you can count by theme before a planning meeting.

  3. 14Yes / No

    Did you run into anything broken today?

    A same-day check for broken things. Ask it in a popup at the end of a session, and add logic so only a Yes leads to the screenshot question.

  4. 15Stars

    How stable has the product been for you?

    How stable the product has been, in five stars. A drop right after a release points to a problem before support tickets pile up.

  5. 16Screenshot

    Take a screenshot of the bug and circle what looks wrong

    Lets users capture the screen and mark what looks wrong, so a bug report arrives with its context. Results shows the screenshots in a gallery. Screenshot is on every plan, 1 per survey on Free.

What to build next

Use these before roadmap planning, since ranking and points show what users would give up to get something else.

  1. 01Text

    What is the one thing we could improve?

    The single improvement a user would make. Ask it at the end of any product survey, and read the themes to see which request comes up most across accounts.

  2. 17Ranking

    Pick the three improvements you want most

    Users pick and order their top three from a fixed list. Results shows the average place per item, a clearer signal than open requests when you choose between known options.

  3. 18Points allocation

    Spread 100 points across what we should work on next

    Users spread 100 points over five areas, so every extra point for new features costs a point somewhere else. Results shows the average points per item.

Tips for asking about product

Small choices that get honest, useful answers.

  1. 01

    Ask inside the product

    Show product questions to signed-in users in your web app once they have used it for a while. Target by pages so each question appears next to the feature it asks about.

  2. 02

    Give each survey one goal

    Ask about fit, quality or the roadmap in separate rounds. A survey that tries to cover everything gets short answers to all of it.

  3. 03

    Send bugs to the right team

    Give each bug report an owner in the inbox the same day. On every plan, workflows can create the issue in Jira or Linear for you.

  4. 04

    Read answers by type of user

    Select an answer in the usage or fit question to filter the page, and compare what daily users want with what occasional users want.

Any business templatesAll topics

Add these questions to a survey

From the library to the first answers.

  1. 1

    Open the library

    In the Usertick survey editor, choose From library, filter by industry and topic, and add several questions at once.

  2. 2

    Or paste your own list

    Paste questions reads up to 10 questions from any text on Free, 100 on Starter and 200 on Pro and above, keeps your wording and picks an answer type for each.

  3. 3

    Choose where it runs

    Show the survey on your website, send it by email, share its link and QR code, or switch it to a conversation.

  4. 4

    Read the answers

    Results counts every score and choice, and Usertick reads each written answer and files it by topic, on every plan.

Templates and more questions about product

Full surveys that ask about the same things, and neighboring topics in the library.

Templates

Browse all templates
PricingPrice sensitivity meter (Van Westendorp)Find an acceptable price range with the Van Westendorp method: four price questions that show where your product starts to feel too cheap or too expensive. Send it to customers and prospects before you set or change a price.
ResearchMarket researchLearn how people in your market buy today: how often, where and from whom, what decides it, what they miss and what would make them switch. Send it to a panel or a mailing list before you enter a market or plan a launch.
ProductFeature satisfactionRate satisfaction across the main parts of your product and see where users would spend your next improvement. Send it to active users twice a year.
ResearchProblem validationFind out how often people face a problem, how they solve it today and what they would pay to solve it better, before you build anything. Send it to people in your target market and replace the example problem with your own.

Frequently asked questions

Four to six in one survey. Pick one fit or value question, one or two about what gets in the way and one open question, and save the roadmap questions for a separate round.

After a user has worked with the product for a week or two, and again after major releases. On your website, triggers such as pages viewed or time on site wait until a user has done enough to answer.

Usertick surveys run on websites and in web apps. Native phone apps aren't supported, but a phone app can open the survey's link.

The question on how users would feel if they could no longer use the product. Follow the share who answer very disappointed, and read what those users say they like most.

Yes. The question library comes with every plan, the free plan included, and the free plan covers 150 responses a month across your surveys.

Yes. Once a question is in your survey, reword it, change its options or its answer type, and add logic to skip it for some answers.

Yes. The library is translated into Usertick's built-in languages, and in any other language it shows in English for you to translate.

Listen better, act faster, and build what truly matters.

Start free, see what your customers mean, and get each answer to the person who can act on it.

Get started freeTalk to sales
  • 150 responses a month on Free
  • Every channel and AI analysis
  • No card needed