User Interviews: How to Run Them and Learn What Matters

1What Are User Interviews?

A user interview is a structured, one-on-one conversation designed to understand a person's real problems, current workflows, and motivations, rather than asking them to rate a feature or guess what they'd want.

They're used across product, design, and research roles to validate whether a problem is real before building a solution for it, and to check whether an existing product actually fits how people work.

2Why User Interviews Matter

Surveys and analytics tell you what happened; interviews tell you why. That why is what turns a data point into a decision a team can act on.

Teams that skip interviews often build features based on assumptions or the loudest customer request, only to find the underlying problem was different from what they assumed.

3Preparing Good Questions

The strongest interview questions ask about specific past behavior and real situations, not hypothetical future preferences.

Asking would you use a feature that does X tends to produce polite, unreliable answers; asking walk me through the last time you tried to solve this problem surfaces what actually happens.

• Tell me about the last time you ran into this problem - what did you do?
• What tools are you using today to handle this, and where do they fall short?
• What made you decide to look for a different way of doing this?
• If you could change one thing about your current process, what would it be?

4Running the Interview

During the conversation, the interviewer's job is to talk as little as possible and let the participant do most of the talking.

It's tempting to explain or pitch a solution mid-interview when a participant mentions a frustration, but doing so shuts down the conversation and biases everything the participant says afterward.

5Recruiting the Right Participants

Recruiting quality matters more than recruiting quantity - a handful of interviews with people who genuinely experience the problem beats a large batch of loosely relevant participants.

Screening questions before scheduling help confirm a participant actually has the relevant experience, rather than relying on a job title or demographic alone.

6Synthesizing Findings

After a batch of interviews, look for patterns that repeat across multiple sessions rather than acting on any single strong opinion.

A common approach is to write each notable quote or observation on its own note, then group similar notes together to see which themes come up most often across participants.

7Common Mistakes in User Interviews

A few recurring mistakes reduce how useful an interview program actually is.

• Asking leading questions that hint at the answer you want to hear.
• Pitching or defending a product feature instead of listening.
• Treating a single vivid quote as representative of all users.
• Skipping a discussion guide and improvising questions inconsistently across sessions.

8Next Steps

Write a short discussion guide with five to seven open-ended questions before your next interview, and practice staying quiet after asking each one.

User interview skills are valuable across product, UX, and technical roles - exploring a structured career path on SkillVeris can help map where this skill fits into a broader role.