Product Manager interview question
How do you use user research in product decisions?
Use research to answer a specific product uncertainty, recruit relevant participants, combine observed behavior with interviews and quantitative evidence, separate findings from interpretation, and connect insights to a reversible decision.
Direct answer
What a strong answer covers
How it works
Research is useful when it answers a question the team must decide on. The question comes first, then the method that can answer it: interviews and observation for why and how, surveys for how many, usage data for what actually happens, usability tests for whether people can. Participants match the segment the decision is about, not whoever is available. Observed behaviour is weighted above stated preference. Findings are recorded separately from interpretation so others can check the reasoning, and every study ends with a decision it changed or confirmed, otherwise it was not research but reassurance.
Example
Deciding whether to build a mobile app or improve the mobile web experience, the team combined analytics showing 40 percent of sessions on mobile with eight observed sessions where users struggled with a specific form, and a survey of 300 customers about where they used the product. The evidence pointed at the form rather than a native app; fixing it raised mobile conversion by 18 percent, and the app decision was deferred with a dated review.
Common mistakes
- Asking users whether they would use a feature and treating yes as demand.
- Recruiting internal staff or power users for a study about newcomers.
- Running research with no decision attached and filing the report.
A useful answer structure
Answer from your own work.
Do not memorise a script: use only examples you can explain honestly in follow-up questions.
Open the desktop workspace and rehearse a clear answer in your own words.