Market & Customer Discovery Kit

Welcome — what this kit helps you do

This kit helps small teams and innovators quickly find real customer problems that are worth solving and that can scale. Use it to run short, focused discovery interviews, capture consistent notes, identify repeatable patterns, and prioritize opportunities by frequency and impact.

What’s included

• 30-minute interview guide — a timed script that keeps conversations productive while leaving room to follow surprises.
• Persona sketch template — a concise one-page persona to focus who you’re validating.
• Note-taking template — structured fields for context, verbatim quotes, observed behavior, pain points, and potential value signals.
• Segmentation template — a simple canvas to map segments by need, behavior, or context so you can see where problems cluster.
• Synthesis heatmap — a frequency × impact matrix and scorecard to turn raw notes into prioritized opportunities.
• Quick analysis checklist — checks to avoid common discovery mistakes and verify repeatability before investing in a solution.

How to use the kit — a practical flow

1. Choose a target persona or context using the persona sketch. Keep it narrow: a clear who + when produces clearer signals.
2. Run 5–12 short interviews with the 30-minute guide. Early learning comes fast; look for repeating problems, language customers use, and how they prioritize tradeoffs.
3. Capture consistent notes with the note-taking template immediately after each interview so comparisons are reliable.
4. Synthesize into the heatmap — log each problem, estimate frequency across interviews, and rate typical customer impact. Use this to highlight high-frequency, high-impact problems.
5. Segment — map problems onto the segmentation template to see which groups share which problems and which are most underserved.
6. Validate repeatability — run a quick follow-up or micro-survey focused on the top 2–3 problems before designing a solution.

30-minute interview plan (timeboxed)

1. Intro & consent (2–3 min) — explain purpose: learning, not a sales call. Ask permission to record or take notes.
2. Context & routine (5 min) — ask about their typical day, tools, workflows, and context around the topic.
3. Specific recent example (8–10 min) — get a concrete story of a recent time they experienced the problem.
4. Probe consequences (5 min) — what did they do, how did it affect them, what was the cost/time/annoyance?
5. Prioritization & alternatives (5 min) — how do they currently cope? What tradeoffs would they accept?
6. Close (1–2 min) — ask if they’d try a prototype or answer a short follow-up; thank them and confirm contact details.

Sample open questions (use, don’t read like a script)

• Tell me about the last time you tried to [do the task]. What happened?
• How often does that happen? Can you walk me through what you did step-by-step?
• What about that was most frustrating or costly for you?
• What do you do instead when this happens? Why that way?
• If we could remove the hardest part, what would that be worth to you or your team?

Note-taking structure (why it matters)

Each interview note should include: context (who, when), a short narrative of the event, verbatim quotes (language customers use), observable behavior, explicit unmet need, and any strength-of-signal indicators (frequency mentioned, emotional intensity, willingness to pay or change behavior).

Synthesis heatmap — frequency × impact

For each problem, estimate two things across your interviews:

1. Frequency — how many interviewees experienced this problem (low / medium / high).
2. Impact — how severely it affects outcomes, time, cost, or emotions (minor / moderate / major).

Plot problems into a 3×3 grid (low/medium/high). Prioritize problems in the high-frequency, high-impact cell for initial experiments. Use supporting evidence (quotes, behaviors) to justify placement.

Segmentation tips

Segment by the dimension that matters to the problem (role, purchase behavior, context, company size, regulatory constraint). A good segmentation splits where solutions would differ; a bad segmentation is demographic-only if demographics don’t change the problem or buying behavior.

Common mistakes (mal hungers) and how to avoid them

• Building for an assumed problem — always ask for recent concrete examples rather than opinions about hypothetical situations.
• Overweighting a single enthusiastic customer — require repeat signals across multiple conversations or channels before prioritizing.
• Leading questions — avoid asking if they’d pay; instead ask what they currently pay or what they would stop doing.

Quick checklist before you build

• Do 5–12 interviews that match your persona.
• Have at least two independent signals that a problem is both frequent and impactful.
• Confirm existing workarounds and willingness to change behavior.
• Map top problems to segments — does one segment clearly benefit more?

Files & naming conventions included

• Persona-Sketch-Template.docx
• 30min-Interview-Guide.pdf
• Note-Taking-Template.xlsx
• Segmentation-Canvas.xlsx
• Synthesis-Heatmap-Template.xlsx

Adaptation and reuse

This kit is intentionally modular. Teams can adopt individual templates, copy and tailor them to local language and context, or incorporate them into an organizational discovery domain that tracks validated problems over time.

Where this kit can be made even more useful (capability opportunities)

Interactive interview forms, saved note submissions, and a small dashboard that aggregates frequency/impact scores would help teams scale discovery and preserve organizational memory. The current kit is a strong starting point for packaging into an ownable toolkit that teams can copy and tailor.

Use this kit to keep discovery practical, evidence-focused, and repeatable. The clearer your notes and synthesis, the less likely you are to build vanity features that don’t move outcomes.