User interview questions for UX researchers
A rigorous, non-leading question set for generative UX research — built to surface mental models, goals, and friction without contaminating the data.
UX researchers and research-led designers — they spend their days planning studies, moderating sessions, and synthesizing findings into insights the product team will actually use — while defending research rigor against 'just ship it'.
- What they're trying to learn
- produce trustworthy, actionable insight about users' needs, mental models, and behavior.
- Who they interview
- target users recruited to match the study's criteria
Use this for generative and exploratory research. Adapt the probes to your study goals, and pair with a usability test protocol when you move from 'what to build' to 'does it work'.
For UX researchers questions to copy & run
Grand tour
- 1.Tell me about your role and how [topic area] fits into it.
- 2.Walk me through a recent, specific time you did [the task]. Start from the beginning.
- 3.What were you trying to accomplish? What happened?
Probing deeper
- 1.You mentioned [X] — tell me more about that.
- 2.Why did you do it that way?
- 3.How did that make you feel?
- 4.What would have made that easier?
- 5.Can you give me an example?
Mental models & expectations
- 1.How would you describe how [system / process] works to a colleague?
- 2.When you did that, what did you expect to happen?
- 3.Where did reality differ from what you expected?
Tips for better answers.
- Keep questions open and neutral; the moment you signal a 'right' answer, you've biased the data.
- Master the silent probe and the echo ('You said it was frustrating…') to go deeper without leading.
- Anchor to specific past events; generalizations are where accuracy goes to die.
- Separate observation from interpretation in your notes so synthesis stays honest.
Questions about this template.
What makes a user interview question non-leading?
It doesn't hint at a desired answer or embed an assumption. 'How did you find that step?' is neutral; 'Was that step confusing?' plants the idea. Open, past-tense, behavior-focused questions keep the data clean.
How do I probe without biasing the participant?
Use silence, echo their own words back ('You mentioned it was slow…'), and ask for specific examples. These invite elaboration without introducing your own framing or leading them toward a conclusion.
How can I speed up synthesis without losing rigor?
Tag observations as you go, keep quotes verbatim, and separate what you saw from what you think it means. Intervool transcribes each session and extracts structured, quote-linked insights, so you spend synthesis time interpreting patterns instead of re-reading transcripts.
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.