Customer Discovery Interviews

Customer Discovery Interviews là gì?

Customer discovery interview là cuộc trò chuyện có cấu trúc để hiểu đời sống, workflow, pain, workaround, motivation, constraint và buying behavior của customer trước khi team commit vào solution. Mục tiêu không phải là hỏi customer có thích ý tưởng của mình không. Mục tiêu là giảm product uncertainty bằng evidence từ hành vi thật.

Discovery interview tốt giúp PM/BA trả lời: problem này có thật không, ai đau nhất, họ giải quyết hiện nay bằng gì, pain có đủ lớn để đổi behavior không, decision criteria là gì, và insight này nên dẫn đến build, test, pivot, park hay kill.

Roadmap keyword coverage: User Research, UX research, User Interviews

Customer discovery khác gì survey, sales call và usability test?

Template 1: Research plan trước khi recruit

Template 2: Recruit screener

Recruit đúng người quan trọng hơn interview thật nhiều người. Nếu recruit sai segment, synthesis sẽ cho insight sai.

Question ladder: hỏi thế nào để ra insight thật

Template 3: 45-minute interview script

Mom Test principles - dùng đúng cách

• Talk about their life, not your idea: đừng pitch solution sớm. Khi bạn pitch, người nghe chuyển sang mode lịch sự hoặc phản biện giả định.
• Ask about specifics in the past: hành vi quá khứ đáng tin hơn intention tương lai. “Lần gần nhất...” tốt hơn “Bạn có muốn...”.
• Talk less, listen more: người interview nên nói dưới 30% thời lượng. Im lặng 3-5 giây sau câu trả lời thường mở ra insight sâu hơn.
• Ask for commitment only after evidence: nếu cần validate willingness-to-pay, ask for concrete next step: intro, pilot, deposit, calendar hold, data sample.

Note-taking template: quote, behavior, evidence, interpretation

Synthesis: từ raw notes thành insight và opportunity

1. Clean notes: tách raw quote, observed behavior, interpretation. Không trộn observation với conclusion.
2. Tag evidence: pain, trigger, workaround, tool, buyer, blocker, metric, emotion, quote.
3. Cluster themes: gom notes giống nhau theo problem/job, không gom theo feature idea.
4. Score themes: frequency x intensity x strategic fit x solvability x willingness-to-change.
5. Write insight statements: “For [segment], [problem] happens when [context], causing [impact]. Today they [workaround], but [gap].”
6. Decide next step: build, prototype test, concierge test, pricing test, pivot, park or kill.

Template 4: Insight statement và opportunity memo

Case study 1: Hiring tool - AI candidate fit score

Business context: Team wants to build AI fit scoring for recruiters. Initial assumption: recruiters want automation to save time. Discovery shows the stronger pain is not only speed; it is trust and explainability.

Lesson: Discovery prevented a ranking-only feature. The better opportunity was explainable shortlist support.

Case study 2: B2B SaaS analytics dashboard

Problem: Leadership asks for a “better dashboard”. Discovery interviews reveal that managers do not need more charts; they need early warning when renewals are at risk and a clear owner for next action.

• Observed behavior: CSMs export data weekly, then manually tag risky accounts in a spreadsheet.
• Pain: Account risk is discovered after renewal conversation has already gone badly.
• Workaround: Weekly Slack thread asking “any accounts we should worry about?”
• Opportunity: Surface account health changes and assign action owner before renewal window.
• Decision: Prototype account risk digest before redesigning full dashboard.
• Success metric: 80% of risk digests result in owner action or explicit “no action needed” decision within 48 hours.

Case study 3: Consumer e-commerce returns

Problem: Customers complain return process is confusing. Business thinks user wants “faster refund”. Interviews show the biggest anxiety is uncertainty: customers do not know whether their request was accepted, where the package is, or when money returns.

Lesson: Discovery changed the product from “refund faster” to “make return status trustworthy and visible”.

Common pitfalls và no-nos

• Pitching too early: Khi bạn show solution, user sẽ react to your idea instead of their real workflow.
• Asking future hypotheticals: “Would you use/pay?” yếu hơn “What did you do/pay last time?”.
• Recruiting friendly users only: Friends, existing fans, or internal teammates create flattery bias.
• Overweighting one loud user: Một quote mạnh không đủ. Look for pattern across segment.
• No segment discipline: Mixing students, enterprise buyers, freelancers and admins in one synthesis destroys signal.
• Skipping synthesis: Raw transcript is not insight. Insight needs pattern, evidence, impact and decision.
• Ignoring buying process: B2B user pain is not enough if buyer, budget and approval are unclear.
• No consent or privacy hygiene: Always ask before recording and anonymize sensitive data.

Tools and artifacts to use

30-day practice plan

• Week 1: Pick one product uncertainty. Write research plan, screener and 10-question interview guide.
• Week 2: Recruit and interview 5 users in one clear segment. Record with consent and capture raw quotes.
• Week 3: Synthesize into themes. Score frequency, intensity, strategic fit and confidence.
• Week 4: Write opportunity memo and recommend one next step: build, prototype, concierge test, survey, pivot, park or kill.

Definition of done for strong discovery interviews

• Learning goal maps to a real product decision.
• Participants match target segment and screener criteria.
• Questions focus on past behavior, workflow, pain, workaround and impact.
• Interview notes separate raw quote, observed behavior and interpretation.
• Insights include evidence, frequency, intensity and segment.
• Decision or next experiment is explicit.
• Stakeholders can see why the recommendation follows from evidence.
• Privacy, consent and anonymization are handled responsibly.