Feature Prioritization Interview: Guide and Questions for Customers
Use this guide with current customers before you plan the roadmap. It turns feature requests into problems, finds how often and how much each problem hurts, and asks for trade-offs.
- Length
- 30 min
- Questions
- 13
- People
- 10 to 15
- Sections
- 5
What this guide finds out
- Which problems customers have with the product, with real examples.
- How often each problem happens and what it costs the customer.
- The problem behind each feature request.
- Which problem customers would choose if the team could fix only one.
When to use it
- Your backlog has more requests than the team can build this quarter.
- Loud customers drive the roadmap, and you want to hear from the quiet ones.
- You must choose between two large projects and want evidence from customers.
Who to talk to
Customers who used the product in the last 30 days, from more than one plan or company size. Talk to 10 to 15 people. Each interview takes about 30 minutes.
Screener for this guideSaaS Admin Screener: Find the People Who Manage Software ToolsUse this screener to find the people who add users, set permissions and change settings in company software. It includes accidental admins, who often own a tool without an IT title.The discussion guide
Each question has a probe note. The note tells the moderator, a person or an AI, what to do with the answer.
Current use
4 minLearn how the customer uses the product now.
Which tasks do you use the product for most often?
ProbeAsk for the top two or three tasks. Ask how often they do each one.
Which recent change to the product helped you the most?
ProbeAsk what it changed in their work. This shows what kind of change has value for them.
Problems and workarounds
9 minFind the problems, how often they happen and what they cost.
Which task in the product takes you longer than it should?
ProbeAsk about the last time they did it. Ask for each step and which step was slow.
What do you do outside the product to finish your work?
ProbeAsk about spreadsheets, other tools and manual steps. Ask why they do that step outside the product.
Tell me about a recent time when the product could not do what you needed.
ProbeAsk what they did then and what it cost: time, money, a delay or an angry customer.
How many times did that happen in the last month?
ProbeAsk for a number. If they say "often", ask for the last two dates.
Requests
6 minTurn each feature request into the problem behind it.
Is there a feature you asked for, or wanted to ask for? What problem would it solve?
ProbeSeparate the solution from the problem. Ask what they would do with the feature on the first day.
What would you do differently if that feature existed?
ProbeListen for a change in behavior. If nothing would change, record the request as low impact.
Trade-offs
8 minForce a choice between problems.
Here are three problems that other customers told us about. Which one costs you the most?
ProbeShow the three problems as an on-screen choice. Ask why they chose it, and why they chose the last one last.
If the team could fix only one thing in the next three months, what should it be?
ProbeIf they name a feature, ask which problem it fixes. Accept one answer only.
What would you accept to wait for, so that the team can fix that first?
ProbeThis question shows the true priority. If they will wait for nothing, ask which item is the least important.
Close
3 minProtect what works and collect questions for the team.
What should the team keep exactly as it is?
ProbeAsk why. Changes that remove valued parts cause churn.
Do you have a question for the product team?
ProbeRecord the question. Do not answer it and do not promise dates. Thank them and end the interview.
Example finding
Customers who asked for a better export used it to build one weekly report for their manager.
“I do not want the export. I want the chart my boss asks for every Monday, and the export is how I make it.”
Mistakes to avoid
- Do not ask people to rank a list of features. They rank what sounds good, not what they need.
- Do not promise that a feature will be built. It changes the answers and makes trouble later.
- Do not give each request the same weight. Weigh it by how often the problem happens and what it costs.
- Do not interview only your largest accounts. Their problems are not the problems of most customers.
Analyze the answers
Analysis templateOpportunity Solution Tree Template: From Interviews to ExperimentsUse this template to connect a product outcome to what you heard in interviews. Each node type has a rule for what belongs in it, so opportunities do not turn into solutions in disguise.Questions
Customers know their problems well, but they are not the best judges of the solution. Ask about the problem, how often it happens and what it costs.
Use the interviews to find and explain problems. Use usage data to check how many customers do the task where the problem happens.
Once before each planning cycle is a good habit. Keep the guide the same so that you can compare results between cycles.
Let the AI moderator ask these questions
The AI moderator interviews screened people by voice or text. Each claim in the study report links to its clip. The first 3 interviews are free.