Discovery Interview Basics

Warm-up: Learn, don't pitch

2 warm-up questions

• Have you ever been asked for your 'honest opinion' about something a friend made? Were you actually honest?
• First try: you have an idea for an app that helps freelancers with invoicing. I'm a freelancer. You have 30 seconds — start interviewing me. Go.

Reading: Discovery Interview Basics

Read a 250-word text about Discovery Interview Basics

Discovery Interview Basics Customer discovery interviews are structured conversations designed to validate your assumptions about your target market and their problems. Unlike sales calls, these interviews focus entirely on learning, not selling. The goal is to understand whether the problem you think exists actually matters to potential customers. The Purpose of Discovery Discovery interviews help you avoid building products nobody wants. Many startups fail because they build solutions to problems that don't exist or aren't painful enough for customers to pay to solve. By talking to potential users early, you can validate your assumptions before investing significant time and money into development. When to Conduct Discovery Interviews Run discovery interviews before building your product, when considering new features, or when entering a new market segment. These conversations should happen continuously throughout your startup journey. Even after launch, regular customer conversations keep you connected to evolving needs and pain points. The Discovery Mindset Approach discovery interviews with genuine curiosity and humility. You're not trying to convince anyone or validate your idea—you're trying to learn the truth. The best discovery interviewers are comfortable being proven wrong. They ask open-ended questions, listen carefully, and follow interesting threads even when they lead in unexpected directions. Setting Up Successful Interviews Schedule 30-45 minute conversations with people who match your target customer profile. Make it clear upfront that you're not selling anything—you're researching a problem area. Many people are willing to help entrepreneurs, especially if you're respectful of their time and genuinely interested in their perspective.

Vocabulary: Discovery Interview Vocabulary

7 items

Framework: The Mom Test

The Mom Test, 5 steps

The Mom Test: A framework for asking questions in customer discovery interviews that yield honest, useful answers—even from people who want to be polite (like your mom). The core principle: talk about their life, not your idea.

Reading: A model discovery interview

Read a 372-word text about A model discovery interview

A model discovery interview One complete interview sequence — the Mom Test performed, beginning to end, with a freelance designer. The five moves in bold: context, pain discovery, current solutions, impact, budget and timeline. Notice the interviewer never mentions their own idea once. The interview "Thanks for the time — to be clear, I'm not selling anything. I'm researching how freelancers handle the business side of their work, and I just want to learn how it really works for you. First, context: walk me through what happens after you finish a project — from 'work done' to 'money in your account'. ... So you write the invoice in a Word template, export to PDF, email it, and then... wait. Got it. What's the hardest part of that whole process? ... Chasing late payments — say more about that. Tell me about the last time an invoice went really late. ... Six weeks, and you sent four reminder emails you felt awkward writing. What happened then? What are you doing today to deal with this? Have you tried any tools or systems? ... A spreadsheet to track who owes what, calendar reminders to chase, and once you paid for an invoicing app but stopped using it. Why did you stop? ... Interesting — it didn't connect to your bank, so you still had to check payments manually. Let's put numbers on it: how much time does invoicing and chasing take in a normal month? And what's the worst it's cost you? ... About five hours a month, and one client who never paid at all — €1,200 written off. Last one: is this something you're actively trying to solve right now, or is it just background annoyance? ... You looked at two tools last month — that tells me a lot. What would a solution have to do for you to actually switch?" Why this works The interviewer's idea never appears — only the customer's past and present behaviour. Every claim gets pushed toward a story ("tell me about the last time") and a number (five hours, €1,200). And the abandoned app plus last month's tool search are evidence of real pain — far stronger proof than any polite 'yes, I'd use that'.

Practice: Practice: Discovery Interview Concepts

Gap-fill exercise, 5 items

• The purpose of a ____ is to learn about customer problems, not to sell your solution.
• Before building our MVP, we need to ____ that customers actually have this problem.
• We created a ____ describing marketing managers at mid-sized companies to guide our research.
• Ask ____ questions that encourage detailed responses, not just yes or no answers.
• Maintain a ____ during discovery interviews—focus on learning, not convincing.

Practice: Match the Mom Test step to its question

Matching exercise, 6 items

• Context
• Pain discovery
• Current solutions
• Impact and stakes
• Budget and timeline
• The golden rule

Dialogue: Role Play: Your First Customer Discovery Interview

Role-play: You are conducting your very first customer discovery interview with a potential customer to understand their workflow and challenges. (4 lines)

• customer: Sure, I have about 20 minutes. What exactly are you trying to learn from this conversation?
• customer: Okay, that makes sense. Where should we start?
• customer: We mostly use spreadsheets and email. It's not perfect, but we make it work. What else do you want to know?
• customer: Last week we missed a client deadline because updates were buried in an email thread. It was embarrassing honestly. Is that the kind of thing you're building a solution for?

Discussion: Your mission: run the interview

3 discussion questions

• Mission: rerun the warm-up interview properly. Your tutor plays the freelancer; you run a full discovery sequence — context walk-through, hardest part, a 'tell me about the last time' story, current workarounds, numbers, and the actively-solving test. Success = your idea never mentioned, at least one specific story collected, at least one number collected, no 'would you use...' questions. (Tutor: be politely vague until a question forces a story.)
• Second take: the customer says, mid-interview, 'so what's your app going to do?'. Deflect gracefully without pitching — and get back to their life.
• Compare with your first-try opening line. What did your first question assume that your new first question doesn't?