Summary of "How to conduct User Interviews?"

High-level summary

Purpose: A step-by-step how-to for running customer/user interviews to validate a business idea before investing time/money or quitting a job.
Core message: Use customer interviews as the primary research method to surface real user pain, test assumptions, and validate whether a problem is worth building for. Iterate until you get clear signals.

Create a simple acceptance test for validation.
Example: interview N people and require at least M to report the problem as a top problem. (Video example: 20 interviews with a threshold of 15.)

Actively find and talk to target users in the places they frequent (online and offline).

Open with casual chitchat and empathy; explicitly avoid pitching the product.
Use two-person interview teams: one interviewer + one note-taker.
Ask about present and past behaviors (not hypothetical future intentions).
Ask for contact details at the end (email/phone) to build a recruitment/follow-up list.

Sample use case: a laundry app idea used as a running example.

Problem: People who use laundry services find it annoying to drop off and collect clothes.
Customer segment: 35–50 year-old businesspeople who wear formal clothes.
Example assumptions to test:
- Going to the laundry shop is annoying.
- Users are dissatisfied with the current experience.
- Users frequently use laundry services.
- Users don’t have other people help them drop/collect laundry.
- Users would be comfortable handing clothes to an unknown laundry service.

“Tell me a story about the last time you had [problem].”
“When was the last time you went to a laundry shop and had to wait long to drop your laundry?”
“What was the hardest part? Why was that hard?”
“How do you solve it now?”
“Why is the current solution not awesome?”

Avoid asking:

“Would you use this in the future?” or “What do you think about this idea?” — these are leading/hypothetical.

Two-person interviews: one asks questions, the other takes detailed notes.
Focus on:
- Observable behavior (past/present).
- Emotional intensity (things the interviewee spoke passionately about).
- Concrete workarounds the person currently uses.
Capture contact info as early-stage currency for follow-up / user panel.
Synthesize interviews back at the office: summarize insights, highlight repeated/passionate mentions, and refine assumptions/interview script.
Expect multiple iterations to converge on answers.

Interview volume target: example target = 20 interviews.
Validation threshold: example = at least 15/20 must call it a top problem (75%).
Implied metrics to capture during interviews:
- Prevalence of the problem among the target segment (percentage).
- Frequency of the behavior (e.g., how often they use laundry services).
- Satisfaction with current solutions (qualitative score or NPS-style proxy).
- Willingness to adopt or hand over items to a new service (behavioral signal).
- Contact capture rate (emails/phones collected per interviews).

Define your problem statement, customer segment, and list top assumptions.
Set validation criteria (e.g., 20 interviews; 15 confirm problem).
Recruit users from relevant channels (LinkedIn, Meetups, physical locations).
Run interviews with a two-person team; start with chitchat; never pitch.
Ask for past/present behavior stories and the “why” behind pain points.
Collect contact details for follow-up and build a user pool.
Synthesize insights, highlight recurring passionate comments, update assumptions/scripts, iterate.

This material focuses on interview methodology and validation.
It does not cover surveys (promised in the next video), pricing experiments, quantitative KPIs like CAC/LTV, or broader go-to-market planning beyond recruiting sources.