User interview

A user interview is a qualitative research method where a researcher conducts a one-on-one conversation with a user to understand their needs, behaviours, pain points, and perspectives. Rather than collecting quantitative data at scale, user interviews focus on depth - understanding the complete context of how someone works, what problems they face, and what solutions would genuinely help them.

User interviews typically follow a semi-structured format where the interviewer has prepared questions and topics but remains flexible to follow interesting threads. The goal is to have a natural conversation that reveals genuine insights rather than validating predetermined assumptions. Effective user interviews often discover unexpected pain points and needs that customers themselves had not fully articulated.

User interviews differ from surveys in that they enable follow-up questions and exploration. When a survey respondent selects an answer, you learn nothing about why they selected it. In an interview, you can ask why, probe deeper, and understand the complete context underlying their perspective.

User interview formats

• One-on-one phone or video interviews with individual customers
• In-person interviews observing how customers work
• Small group interviews or focus groups with similar customers
• Problem interviews exploring pain points in customer work
• Solution interviews evaluating prototypes or proposals

User interviews prevent building products nobody wants. Many companies fail because they assumed what customers needed without asking. User interviews surface real needs, real pain points, and real blockers. This grounding in customer reality prevents wasting development effort on features nobody needs or solving problems the wrong way.

For B2B growth teams, user interviews provide qualitative context that numbers alone cannot. Conversion rate data tells you what happened - 30% of prospects dropped at a specific point. User interviews reveal why - what specific objection or confusion caused them to leave. This understanding enables targeted solutions.

User interviews also build customer empathy across the organisation. Engineers and product managers who have conducted interviews develop a deeper understanding of customer context and constraints. This shifts perspective from building features to solving real problems. Teams working from interview insights tend to build products with better fit and stronger customer connection.

Conduct user interviews by recruiting 8-12 participants representative of your target customer. Create an interview guide with open-ended questions rather than yes/no questions. Start by understanding their role and current workflow before diving into specific problems. Ask them to describe a specific recent experience rather than generalising. For example, instead of asking "is reporting difficult?" ask them to walk through their last reporting process and describe specific challenges they encountered.

Record interviews (with permission) and take detailed notes. Focus on direct quotes and specific examples. After each interview, write up key insights and themes. After 5-8 interviews, patterns typically emerge. Synthesise interview findings into key themes and insights. Share these insights with product and marketing teams. The most valuable outcome is when team members understand customer context deeply enough to maintain customer focus even when customers are not directly present.

A B2B software company conducted problem interviews with 12 prospective customers before building a new product. They expected to focus on process automation but discovered that the core pain point was communication fragmentation - customers had customer conversations spread across email, messaging apps, and three different platforms. This discovery led the team to build a communication consolidation product rather than a process automation tool. Interviews prevented building the wrong product and instead informed a product strategy that matched actual customer needs.

A product team built prototypes of three proposed solutions to a problem identified in earlier interviews. They conducted solution interviews with customers, showing prototypes and asking which approach best matched their needs and how they would improve each one. Customer feedback was overwhelmingly aligned on one approach with specific improvement suggestions. This validation enabled the team to proceed with development confident they were building something customers wanted, and incorporated feedback ensured better product-market fit from launch.

A growth team was frustrated by losing deals at the final evaluation stage without clear understanding of why prospects were choosing competitors. They conducted interviews with 10 prospects who had chosen competitors, asking them to describe their decision process and what influenced their final choice. Interviews revealed that prospects perceived significant implementation risk because past experience suggested the product worked differently in different customer environments. This discovery led to creating case studies and implementation guides addressing implementation risk, a message that proved compelling in subsequent sales conversations.