Feature validation interview questions
Questions that pressure-test a feature idea against real behavior — so you learn whether people actually need it before it goes on the roadmap.
Product managers deciding what to build next — they spend their days triaging feature requests, arbitrating between stakeholders, and trying to tell the difference between a loud request and a real need.
- What they're trying to learn
- validate that a proposed feature solves a real, frequent problem before committing engineering time.
- Who they interview
- users who would (and wouldn't) use the feature
Use this when a feature idea is on the table and you want evidence before committing. Especially valuable for high-cost bets and loud-but-unproven requests.
Feature validation questions to copy & run
The underlying problem
- 1.Tell me about the last time you ran into [the problem this feature would solve].
- 2.How do you handle that today?
- 3.How often does it come up, and how much does it cost you?
Current workarounds
- 1.What have you tried to make it better?
- 2.How well does that work? Where does it break down?
- 3.Have you looked for another tool to solve it? What did you search for?
Testing the solution
- 1.If [the feature] existed, walk me through how you imagine using it.
- 2.What would it need to do to be genuinely useful — not just nice?
- 3.What would you stop doing if you had it?
- 4.Would you use this instead of your current workaround? What would make you hesitate?
Tips for better answers.
- Validate the problem before describing the feature — enthusiasm for an idea is not evidence of need.
- Weight behavior over opinion. Someone already hacking a workaround is a stronger signal than someone who 'would love that'.
- Ask what they'd give up to get it. Real need survives a trade-off; polite interest doesn't.
- Talk to people who wouldn't use it too — knowing who it's not for keeps scope honest.
Questions about this template.
How do I validate a feature before building it?
Confirm the underlying problem is real and frequent, check whether people already work around it, and only then test the concept. Look for behavioral evidence — existing workarounds, time or money spent — rather than stated interest.
Why do users ask for features they won't use?
People suggest solutions to problems they feel, and they agree to be helpful or polite. The request points at a real problem, but the specific feature they name may not be the right fix — so validate the problem, not just the feature.
How do I prioritize validated features?
Score them by how real and frequent the problem is, how much value the fix delivers, and how much effort it takes. Intervool links every feature idea back to the interviews and quotes behind it and helps rank them by impact versus effort.
Don't just ask the questions — synthesize the answers.
Save these questions as a template in Intervool, capture the interview, and let AI turn every conversation into insights, personas, and a prioritized roadmap. Free for 30 days.