Customer Discovery: Talking to Users Before You Build

1. Why Talk to Customers *Before* You Build

Most startup ideas fail not because the tech is bad, but because nobody actually wants what’s being built.

Customer discovery is the process of talking to potential customers and observing their behavior before you build a full product. It comes from the Lean Startup / Customer Development approach popularized in the 2010s and is still the standard in 2026.

In previous modules, you:

• Learned what entrepreneurship is and how ideas become businesses.
• Chose a problem worth solving.

Now you’ll learn how to test your assumptions about that problem by:

1. Running customer discovery interviews.
2. Focusing on the problem first, not pitching your solution.
3. Turning raw notes into insights and updated assumptions.

Key mindset shift:

You are not trying to convince people you’re right.

You are trying to discover whether you are right.

> Visualize this: Instead of a straight line from “idea → app”, imagine a loop: idea → talk to users → learn → adjust idea → talk again. That loop is customer discovery.

2. Hypotheses & Assumptions: What Are You Actually Testing?

Before you talk to anyone, you need to know what you’re testing.

In customer discovery, you write down hypotheses: structured guesses you can test with real people.

Common types of assumptions

For an early-stage idea, you usually have assumptions about:

1. Customer – Who has the problem?

• Example: “Busy university students who have part-time jobs.”

1. Problem – What is painful or frustrating?

• Example: “They struggle to keep track of assignment deadlines across multiple platforms.”

1. Current behavior – How they deal with it now.

• Example: “They use a mix of calendar apps, sticky notes, and screenshots.”

1. Motivation / intensity – How much they care.

• Example: “They are stressed enough about this to try new tools.”

Write them as testable statements:

```text

Customer hypothesis: First- and second-year university students with part-time jobs feel overwhelmed by managing deadlines.

Problem hypothesis: They lose track of at least one important deadline per month because their tools are scattered.

Behavior hypothesis: They currently use at least two different tools (e.g., Google Calendar + notes app) to manage deadlines.

```

You’ll use interviews to see which of these are confirmed, modified, or disproved.

3. Problem Interviews vs. Solution Interviews

A major mistake beginners make is pitching their solution too early. That turns a discovery interview into a sales meeting.

Problem Interviews

You focus on:

• The person’s context (who they are, what their day looks like).
• Their current behavior.
• Their problems, pains, and workarounds.

You do not describe your app/idea in detail (or at all, if you can avoid it).

Goal: Validate that the problem is real, painful, and frequent.

Solution Interviews

You focus on:

• A specific concept or prototype.
• How they react to it.
• Whether it fits into their real behavior.

Goal: Validate how to solve the problem and whether your proposed solution is desirable and usable.

For this module, we are mostly in problem interview mode.

> Think of it like medicine: A problem interview is the doctor asking questions and understanding symptoms. A solution interview is when the doctor suggests a treatment and asks what you think about it. You don’t prescribe before you diagnose.

4. Activity: Turn Vague Ideas into Clear Hypotheses

Use this as a quick thought exercise.

Your task

Pick one idea you’re considering (or imagine one). Then, write three hypotheses:

1. One about the customer
2. One about the problem
3. One about current behavior

Use this template:

```text

Customer hypothesis:

People who

Problem hypothesis:

Struggle with / are frustrated by

Current behavior hypothesis:

Right now, they handle this by

```

Example

Idea: A tool to help roommate groups split groceries fairly.

```text

Customer hypothesis:

People in shared apartments (2–5 roommates) who buy groceries together.

Problem hypothesis:

They feel that grocery costs are unfairly distributed or hard to track.

Current behavior hypothesis:

Right now, they use informal methods like group chats, random paybacks, or no tracking at all.

```

Do this now:

• Fill in the template for your own idea.
• Keep it nearby; you’ll use it to design your interview questions in the next steps.

5. Designing Good Customer Discovery Questions

Your questions should help you observe reality, not confirm your fantasy.

Principles of strong questions

1. Ask about the past, not the future

People are bad at predicting their future behavior.

• Better: “Tell me about the last time you missed an important deadline.”
• Worse: “Would you use an app that sends deadline reminders?”

1. Be concrete and specific

• Better: “Walk me through how you planned your last exam week.”
• Worse: “How do you usually stay organized?”

1. Avoid leading questions

• Leading: “How annoying is it when you lose track of deadlines?” (assumes it’s annoying)
• Neutral: “What’s challenging about managing your deadlines, if anything?”

1. Start broad, then go deep

• Start: “What does a typical week look like for you?”
• Then: “Where do deadlines and scheduling fit into that?”

1. Ask for examples and stories

• “Can you give me an example?”
• “What happened then?”
• “How did you handle it?”

Visualize a good interview

Picture sitting with a student in a campus café. Instead of a slide deck, you have a notebook. You say:

• “Tell me about the last week of last semester.”
• “When did you feel most stressed about deadlines?”
• “What did you do at that moment?”

You’re collecting real stories, not hypothetical opinions.

6. Example: Weak vs. Strong Interview Questions

Let’s compare weak (leading or vague) questions with strong (neutral, concrete) ones for the student deadlines idea.

| Goal | Weak Question | Why It’s Weak | Strong Question | Why It’s Better |

|------|---------------|---------------|-----------------|-----------------|

| Understand if the problem exists | “Deadlines are really stressful, right?” | Assumes stress; pushes them to agree. | “How do you feel about managing your assignment deadlines?” | Open, allows any answer. |

| Learn current behavior | “Would you use an app that organizes all your deadlines?” | Hypothetical; about future behavior. | “What tools do you currently use to keep track of your deadlines?” | Focuses on real, past behavior. |

| Measure intensity | “On a scale of 1–10, how much do you need my app?” | Assumes they need it; about your solution. | “Tell me about the last time a deadline caused a serious problem for you.” | Surfaces real consequences and intensity. |

| Discover alternatives | “My app is better than using a calendar, don’t you think?” | Biased comparison. | “If you lost your current way of tracking deadlines, what would you do instead?” | Reveals real alternatives and attachment to current tools. |

Use this as a reference when drafting your own questions.

7. Quiz: Spot the Leading Question

Check your understanding of leading vs. neutral questions.

8. Recruiting and Running Simple Interviews

You don’t need hundreds of interviews. For early discovery, 5–10 well-run interviews with your target segment can reveal patterns.

Who to talk to

• People who match your customer hypothesis (e.g., undergrads with part-time jobs, not just any friend).
• Avoid only talking to friends who want to be nice; they’re more likely to tell you what you want to hear.

How to recruit (simple methods for students)

• Ask classmates or lab mates who fit your criteria.
• Post in relevant student groups (course chats, clubs, Discord, Slack).
• Approach people in context (e.g., library, study spaces) and politely ask if they have 10–15 minutes for a research chat.

Basic structure of a 15–20 minute problem interview

1. Introduction (2–3 min)

• Who you are, why you’re doing this.
• Emphasize: “I’m not selling anything; I’m just trying to understand your experience.”

1. Context questions (5 min)

• “What year are you in? What’s your course load like?”
• “What does a typical week look like for you?”

1. Deep dive into the problem area (8–10 min)

• “Tell me about the last time you felt overwhelmed by deadlines.”
• “What did you do? What tools did you use?”
• “What was the impact when things went wrong?”

1. Wrap-up (2–3 min)

• “Is there anything I didn’t ask that you think is important?”
• Optional: very brief mention of your idea and ask, “Based on what you said, does something like this sound aligned with your needs, or not really?” (Keep it short; don’t pitch.)

Always ask permission to take notes or record (if allowed by your institution’s ethics rules and local privacy laws).

9. Activity: Draft Your First Interview Script

Now, turn your hypotheses into an interview script. This is a guide, not a rigid checklist.

Step 1: Copy this template

```text

Intro (1–2 questions)

• Thanks for taking the time. I’m exploring how people like you handle _.
• I’m not selling anything; I just want to understand your experience.

Context

• Can you tell me a bit about yourself? (role, year, major, etc.)
• What does a typical week look like for you?

Problem area

• When do you usually deal with _?
• Tell me about the last time _ was frustrating or time-consuming.
• What did you do then? Walk me through it step by step.
• What tools or methods did you use?
• What, if anything, was particularly annoying or stressful about it?
• How often does this kind of situation happen?

Current alternatives & intensity

• If you couldn’t use your current method, what would you do instead?
• Have you tried anything else in the past? What happened?
• How big of a deal is this for you compared to other problems in your life/studies/work?

Wrap-up

• Is there anything I didn’t ask that you think is important about this?
• Would you be open to me following up later as I learn more?

```

Step 2: Customize

• Replace the blanks (`_`) with your problem area.
• Add 1–2 specific questions tied to your hypotheses.

Do this now in a separate document or notes app. You now have a usable script for your first 3–5 interviews.

10. From Raw Notes to Insights: Synthesizing What You Learned

After a few interviews, the value comes from making sense of your notes.

Step 1: Capture key data right after each interview

Right after each conversation, quickly write:

• 3 main problems they mentioned.
• Their current workaround(s).
• Any strong emotion (frustration, stress, indifference).
• 1–2 direct quotes that stood out.

Step 2: Look for patterns across interviews

After 5–10 interviews, scan your notes and ask:

• Which problems keep repeating across people?
• Which problems seem minor or one-off?
• What tools/behaviors show up again and again?
• Are there segments (e.g., first-years vs. final-years) who experience the problem differently?

You can visualize this as a simple table:

```text

Interview | Biggest problem mentioned | Current workaround | Emotion (1–5) | Quote

----------|---------------------------|--------------------|---------------|------

#1 | | | |

#2 | | | |

#3 | | | |

...

```

Step 3: Update your assumptions

Rewrite your hypotheses as “updated beliefs”:

• Original: “Students lose track of at least one important deadline per month.”

Updated: “Most students don’t forget deadlines; they remember them late and then rush, causing stress.”

• Original: “They use a mix of tools and want one unified app.”

Updated: “They already use one main tool (calendar) but don’t enter all deadlines because it feels time-consuming.”

These updated beliefs guide what to test next and whether to move toward solution interviews or even pivot your idea.

11. Activity: Turn Notes into Updated Assumptions

Imagine you interviewed 5 students about deadline management. Across interviews, you noticed:

• All 5 use some form of digital calendar.
• 4 out of 5 said the real issue is “I only add some deadlines, not all of them.”
• 3 mentioned procrastination and avoiding looking at their planner when stressed.
• 4 said they don’t want another app, but would like their existing tools to be easier to keep up-to-date.

Your task

Write two updated assumptions based on these patterns:

1. An updated problem assumption:

```text

Updated problem assumption:

```

1. An updated behavior/solution direction assumption:

```text

Updated behavior/solution assumption:

```

Example answers (compare after you try)

• Updated problem assumption:

“The main pain isn’t forgetting that deadlines exist; it’s the stress of last-minute rushes because students don’t consistently enter all deadlines into their calendar.”

• Updated behavior/solution assumption:

“Students prefer improving their existing tools (e.g., automating calendar entries) rather than adopting a completely new app.”

The exact wording doesn’t matter; what matters is that your original beliefs changed because of what you heard.

12. Flashcards: Key Terms Review

Flip these cards (mentally or with your own notes) to review the core concepts from this module.