User interview

A user interview is a one-on-one conversation with a user (or potential user) designed to understand their experiences, needs, behaviors, and motivations. Unlike surveys that capture what people say at scale, interviews dive deep into why - exploring the context, reasoning, and emotions behind user behavior. Well-conducted interviews reveal insights that no amount of analytics or survey data can provide.

Why it matters

Numbers tell you what users do; interviews tell you why they do it. Analytics might show that 40% of users abandon the checkout flow, but interviews reveal whether they're confused, distracted, comparing prices elsewhere, or simply changed their mind. This depth of understanding enables better solutions.

Interviews also uncover problems you didn't know existed. Users adapt to friction, work around limitations, and find unexpected uses for your product - none of which appears in metrics. Direct conversation surfaces these hidden realities.

For product managers, interviews build empathy that informs every decision. When you've heard users describe their challenges in their own words, you make different choices than when users are abstract personas on a slide. Interviews connect abstract strategy to human reality.

Types of user interviews

Different interview formats serve different purposes:

Exploratory interviews investigate a problem space before solutions exist. The goal is understanding user needs, workflows, and pain points - not evaluating solutions.

Evaluative interviews gather feedback on specific designs, features, or prototypes. Users interact with something concrete while the interviewer probes their reactions.

Contextual interviews happen in the user's natural environment - their office, home, or wherever they actually use the product. Context reveals factors that disappear in artificial settings.

Job interviews focus on understanding what users are trying to accomplish (their "job to be done") and how they currently approach it.

Planning user interviews

Effective interviews require preparation:

Define objectives. What do you need to learn? Vague goals produce vague insights. "Understand user needs" is too broad. "Understand what triggers users to search for a tool like ours" is specific.

Identify participants. Who can provide the insights you need? Current users, potential users, churned users, and non-users offer different perspectives. Recruit participants who represent your target audience.

Prepare an interview guide. A list of topics and questions provides structure without forcing a rigid script. Organize from broad to specific, opening to probing.

Plan logistics. In-person, video call, or phone? How long? Where? Will you record? These decisions affect what you can learn and participant comfort.

Conducting the interview

The conversation itself requires skill:

Build rapport first. People share more when comfortable. Start with easy questions. Explain the process. Establish that you want honest feedback, not validation.

Ask open-ended questions. "What has your experience been with..." invites stories. "Did you like it?" invites yes/no answers that reveal little.

Follow the user's lead. The best insights often come from tangents. When users mention something unexpected, explore it. The interview guide is a tool, not a constraint.

Probe for specifics. When users say something interesting, dig deeper. "Can you tell me more about that?" "Can you give me an example?" "What do you mean by...?" Move from general to specific.

Avoid leading questions. "Don't you think this feature is useful?" guides the answer. "How have you used this feature?" allows genuine response.

Stay neutral. Your reaction to answers influences future answers. Don't defend the product when users criticize. Don't celebrate when they praise. Listen.

Listen more than you talk. The interviewer's job is to understand, not explain. Silence can be productive - it gives users space to think and share more.

Capture everything. Record if possible and permitted. Take notes on key quotes, surprising reactions, and themes to explore.

Interview questions

Effective questions open dialogue without leading:

Experience questions:

Probing questions:

Comparative questions:

Scenario questions:

Closing questions:

Analyzing interview data

Raw interview transcripts need systematic analysis:

Identify patterns. What themes appear across multiple interviews? What do different users say about similar topics?

Note unexpected findings. The most valuable insights often aren't what you expected to learn. Pay attention to surprises.

Preserve nuance. Resist premature summarization. Keep track of the different perspectives users shared, not just the consensus.

Use quotes. Actual user language is more compelling than researcher paraphrase. "I want to throw my laptop" conveys something different than "User expressed frustration."

Synthesize into insights. Patterns become insights: "Users don't notice the save button because they expect changes to save automatically." Insights lead to recommendations.

Common mistakes

Several patterns undermine interview effectiveness:

Asking about future behavior. "Would you use this feature?" produces unreliable answers. People are poor predictors of their own future behavior. Ask about past behavior instead.

Pitching instead of listening. If you spend the interview explaining your product, you're not learning anything.

Asking leading questions. "How much did you like the new design?" presumes they liked it. "What was your reaction to the design?" doesn't.

Taking feedback literally. Users describe symptoms, not solutions. "I need an export button" might mean "I need to use this data elsewhere." Understand the underlying need.

Interviewing the wrong people. Convenience samples of friends and colleagues rarely represent real users.

Too few interviews. One or two interviews provide anecdotes, not patterns. Most topics need 5-10 interviews before themes stabilize.

Tools like Klero help connect interview insights to broader user feedback, showing whether themes from qualitative interviews match patterns in feedback at scale. When interview findings align with systematic feedback analysis, confidence in insights increases.