Roadmap questions that show what users would build first
Ask users what happened to their requests, how well your roadmap matches their priorities and where you should spend next. Each question below comes with when to ask it and what the answer tells you.
What feature request and roadmap survey questions tell you
Feature request and roadmap survey questions ask users whether they have sent you a request, what happened after, how heard they feel, how well your roadmap matches their priorities and where they would spend your next year. Requests arrive one at a time through support and sales. A survey puts them side by side, along with the users who care enough to test them.
Ask active users once or twice a year by email, before your planning cycle, and ask the follow-up questions after you ship something users requested. Pick five or six: whether they sent a request, what happened, how heard they feel, the points split and what they would move to the top.
Written answers get a theme and a type, so requests group by theme and complaints about unanswered requests can be read apart. Each response gets an owner and a status in the inbox, and workflows can send ideas to Jira or Linear, or to HubSpot next to the account.
- Questions
- 14
- Best asked
- Before your planning cycle, once or twice a year
- Industry
- SaaS
- Where to find them
- From library in the Usertick survey editor, on every plan
The 14 roadmap and requests questions, with when to ask each
Grouped by what they tell you. Use them as they are or change the wording.
Sending requests and what happened
Start with whether users asked and what came of it, which shows whether your request channel works.
- 01Yes / No
Have you ever sent us a feature request?
Asks whether the user has ever sent a feature request. Add logic so users who say No skip the follow-up about what happened.
- 02Multiple choice
What happened after you sent it?
One choice for what happened after the request, from built to nothing the user saw. A large Nothing that I saw share shows requests disappear without a reply.
- 03Customer effort
How easy is it to tell us what you need?
A customer effort score for telling you what the user needs. Low scores point to a request channel that is hard to find or slow to answer.
- 06Big scale
How much do you feel heard when you give us input?
How heard users feel, on a ten-step scale. Low scores from users who got no reply show what silence after a request costs you.
How users want to follow plans
These set where and how far ahead you publish what is planned.
- 04Multiple choice
How would you like to follow what is planned?
Lets users pick every way they would follow plans, from a public roadmap to email updates. The bars show where to publish what is planned.
- 10Dropdown
How far ahead should a public roadmap look?
How far ahead a public roadmap should look, from the next month to the whole year. The share of each answer sets how far ahead to publish.
What users want next
The rating, the top request, the points split and the trade-off give your planning a clear set of priorities.
- 05Stars
How well does our roadmap match your priorities?
Five stars for how well the roadmap matches the user's priorities. Results shows the average and the share who rated 4 or higher, so compare it each round.
- 07Text
What would you move to the top of our list?
An open question for what the user would move to the top of the list. Filter the answers by theme to see which requests repeat across accounts.
- 08Points allocation
Split 100 points across where we should spend next year
Users split 100 points across core features, speed and reliability, integrations, reporting and design. Results shows the average points per item, a clear input for yearly planning.
- 13This or that
You would rather we
One pair: polish what exists or ship something new. The split bar gives you a plain answer when the team debates the next quarter.
Workarounds and deadlines
Ask what users do without the feature today and when they need it, which shows how urgent each request is.
- 09Text
What are you working around today because we do not support it?
An open question for what the user works around today. The workarounds show what a missing feature costs, which says more about urgency than the request alone.
- 12Date
By when do you need the thing you asked for?
The date by which the user needs the requested feature, picked on a calendar. Results shows the picked dates, so you can see which requests have a deadline.
Users who want to help
End with the people willing to shape and test new features, a panel for your next round of research.
- 11Yes / No
Would you join a call to shape a feature before it is built?
Asks whether the user would join a call to shape a feature. Select Yes in Results and read it with the contact question to build a research panel.
- 14Contact
Leave your details if you want to test new things early
Collects the names and emails of users who want to test new things early. Results lists them in a table, a ready list for your next beta.
Tips for asking about roadmap and requests
Small choices that get honest, useful answers.
- 01
Reply to every request
Give each request an owner and a status in the inbox, so users hear what happened even when the answer is no.
- 02
Ask again after you ship
When you ship a requested feature, ask the users who wanted it whether it meets the need.
- 03
Plan with points
Use the points split for planning. It asks users to give something up, which shows priorities better than a list of wishes.
- 04
Build a testing panel
Keep the contacts of users who want to test early, and invite them before each beta.
Add these questions to a survey
From the library to the first answers.
- 1
Open the library
In the Usertick survey editor, choose From library, filter by industry and topic, and add several questions at once.
- 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
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
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 roadmap and requests
Full surveys that ask about the same things, and neighboring topics in the library.
Templates
Browse all templatesFrequently asked questions
Once or twice a year, before your planning cycle, by email to active users. Ask the follow-up questions after you ship something users requested.
Five or six. Start with whether they sent a request and what happened, add the points split, and end with what they would move to the top.
Yes, on every plan. Workflows can also post each response to Slack or Microsoft Teams, add rows to Google Sheets or call a webhook.
Yes. The contact question collects the names and emails of users who want to test early, and Results lists them in a table.
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.
- 150 responses a month on Free
- Every channel and AI analysis
- No card needed