markdowneditor

Customer Discovery: [interview with] – YYYY-MM-DD

Customer interview – past behavior, not opinions

스타트업표준customerdiscovery

사용법: Validating problem hypotheses. Ask about the past, never the hypothetical future – people lie politely.

미리보기

Customer Discovery: [interview with] – YYYY-MM-DD

Interview notes – learn their problem, not pitch your solution. If you talked more than they did, redo it.

FieldValue
Interviewee[name / role / company type]
Interviewer@name
DateYYYY-MM-DD
Segment[which hypothesis segment]

Hypothesis being tested

We believe [segment] struggles with [problem] enough to [pay / switch].

Context

  • How they do [task] today: [current workflow]
  • Tools used: [list]
  • Time / money spent on the problem: [quantified]

Questions & answers (past behavior, not opinions)

Question askedWhat they actually said
Tell me about the last time [problem] happened
What did you do about it?
What did that cost you (time/money)?
What have you tried?
Who else cares about this?

Rules honored: asked about the past, not hypothetical futures; let silence work; never described our solution.

Pain intensity

  • Pain level: none / mild / strong / hair-on-fire
  • Evidence: [what they spend doing it manually]

Surprises

[Things we didn't expect to hear]

Signals

  • Would take a follow-up call
  • Would try an MVP
  • Would pay: $N / [unit]
  • Introduced us to [referral]

Learnings -> hypothesis update

  • Hypothesis: confirmed / weakened / killed
  • New insight: [what this changes]

관련 템플릿