User interview

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.

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.

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 user interview is a structured one-on-one conversation with a real customer to understand how they actually work, what hurts, and how they decide. It's qualitative research: instead of counting answers at scale like a survey does, you go deep with a handful of people to understand the full context behind their behaviour.

Most interviews are semi-structured. You prepare your questions and topics, but you stay loose enough to chase the interesting threads when they appear. The whole point is a natural conversation that surfaces genuine insight, not a script that confirms what you already believed. The best interviews uncover pain points the customer themselves hadn't fully put into words.

The difference from a survey is the follow-up. When someone ticks a box, you learn nothing about why. In an interview you ask why, you probe, and you understand the reasoning underneath.

A few common formats:

• One-on-one phone or video interviews with individual customers
• In-person sessions where you watch how someone actually works
• Small group interviews or focus groups with similar customers
• Problem interviews exploring pain points in their day-to-day
• Solution interviews where you put a prototype in front of them

Why it matters

User interviews stop you building things nobody wants. Plenty of companies die because they assumed a need instead of checking it. Interviews ground you in customer reality: the real blockers, the real objections, the real workarounds people have quietly built.

For a B2B growth team, they give you the why behind the numbers. Your analytics tell you 30% of prospects drop at a certain step. An interview tells you it's because the pricing page implies a contract they can't sign without legal sign-off. One is a fact; the other is something you can act on.

They also build empathy across the team. An engineer who has sat through five interviews builds differently from one who has only read a spec.

How to apply it

Recruit 8 to 12 people who genuinely match your target customer, and make booking them painless. Drop a single Cal.com link in your outreach so a prospect picks a slot without the email ping-pong, and they'll actually show up. Write an interview guide built from open questions, not yes/no ones. Start with their role and current workflow before you go anywhere near your solution.

Ask for specifics, not generalities. Instead of "is reporting difficult?", ask them to walk you through their last reporting cycle and where it bit them. Record the call so you can stay present instead of scribbling. If you're running these on video, Fireflies.ai sits in the meeting, transcribes it, and pulls out the moments worth revisiting, so you're listening properly rather than typing.

After each session, write up the themes while it's fresh. By interview five to eight, patterns start repeating. Synthesise everything into a handful of clear insights in a shared space like Notion so product and marketing work from the same quotes, not a half-remembered summary in one person's head. The real win is when the whole team understands the customer well enough to keep them in mind even when there's no customer in the room.

Examples

Problem discovery interviews for a new product

A B2B software company ran problem interviews with 12 prospects before writing a line of code. They went in expecting to build process automation, but discovered the actual pain was fragmentation: customer conversations scattered across email, messaging apps, and three separate platforms. That sent them to build a consolidation product instead. The interviews saved them from shipping the wrong thing.

Solution interviews validating direction

A product team built prototypes of three possible solutions to a problem earlier interviews had surfaced. They showed each one to customers and asked which fit best and how they'd improve it. The feedback landed overwhelmingly on one approach, with sharp suggestions attached. They proceeded confident they were building something wanted, and shipped with better fit because the feedback was baked in from the start.

Sales objection discovery

A growth team kept losing deals at the final stage without knowing why. They interviewed 10 prospects who'd picked a competitor and asked them to walk through the decision. The interviews revealed a shared fear of implementation risk: past experience told these buyers the product behaved differently in different environments. That led to case studies and implementation guides built specifically to defuse that fear, and the message proved compelling in the deals that followed.

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.

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.