User interview questions
Behavioral, non-leading user interview questions that reveal how people actually work and where your product helps or gets in the way — grounded in real tasks, not opinions.
UX researchers, designers, and product managers — they spend their days between Figma, research repositories, and stakeholder reviews, translating messy user reality into designs and decisions the team can act on.
- What they're trying to learn
- understand users' mental models, goals, and friction so the team designs for real behavior instead of assumptions.
- Who they interview
- current users of your product or people who do the relevant task
Use this for generative UX research — understanding users before or alongside design. Pair it with a usability test template when you want to evaluate a specific flow.
User interview questions to copy & run
Background & goals
- 1.What's your role, and how does [product / task] fit into your work?
- 2.What are you ultimately trying to get done when you use it?
- 3.How did you end up using [product] in the first place?
Real usage
- 1.Walk me through the last time you used it. What were you trying to do?
- 2.Show me, if you can — where do you start?
- 3.What did you expect to happen there? What actually happened?
- 4.Where do you spend the most time? Where do you get stuck?
- 5.Is there anything you avoid doing because it's too painful?
Gaps & workarounds
- 1.What do you do outside the product to get the job done — spreadsheets, other tools, asking a colleague?
- 2.What's missing that would make this easier?
- 3.If you could change one thing, what would it be?
Tips for better answers.
- Ask people to show you, not just tell you. Watching reveals friction they've stopped noticing.
- Separate the goal from the feature. Users describe solutions; your job is to find the underlying need.
- Note the workarounds — spreadsheets and copy-paste are a map of your product's gaps.
- Keep questions neutral. 'How was that?' invites honesty; 'Was that easy?' invites a polite yes.
Questions about this template.
What's the difference between a user interview and a usability test?
A user interview is generative — it explores goals, context, and behavior to inform what to build. A usability test is evaluative — it watches someone attempt specific tasks to find where a design breaks down. You often use both: interviews to decide direction, usability tests to refine execution.
How long should a user interview be?
30–45 minutes is the sweet spot. Long enough to get past surface answers and into real stories, short enough to keep the participant engaged and to keep your synthesis manageable.
How do I recruit users for interviews?
Pull from your existing users (in-app prompts, email, support conversations), your CRM, or a recruiting panel. Screen for people who actually do the task you're researching — a small, well-targeted sample beats a large, random one.
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.