Turn discovery call notes into testable product hypotheses

Transform messy customer feedback into structured, prioritized product hypotheses with clear validation tests and metrics.

You getObserved Evidence, proposed Solution Concept and validation Metric & 2-Week Test

Prompt

Prompt
Act as a principal product manager. Analyze the provided user discovery call notes to extract unmet user problems and convert them into rigorous, testable product hypotheses.

Rules:
- Focus strictly on recurring friction, unprompted complaints, and stated workarounds.
- Frame each hypothesis using the standard format: "Because we observed [evidence], we believe [action] will result in [measurable outcome]."
- Include one fast, non-code experiment to validate or invalidate each hypothesis within two weeks.
- Explicitly state what qualitative data should be verified with quantitative analytics.

Output format:
Present a numbered list of hypotheses. Under each hypothesis, include:
- Observed Evidence
- Proposed Solution Concept
- Validation Metric & 2-Week Test
- Data to Verify

Discovery notes are below:

Example output

Example for: discovery notes from five B2B billing software user calls

  1. Automated Invoice Discrepancy Flagging
  • Observed Evidence: Four of five finance managers spend the first Monday of every month comparing spreadsheet exports against ERP data line by line to catch invoice mismatches.
  • Proposed Solution Concept: A scheduled ingestion webhook that flags line-item discrepancies between billing and ERP records automatically.
  • Validation Metric & 2-Week Test: Offer five interviewed customers a manual spreadsheet reconciliation check run through an internal script; measure if at least four upload their files within 48 hours.
  • Data to Verify: Check product logs for monthly export volume spikes on the 1st through 4th calendar days.
  1. Role-Based Invoice Approval Routing
  • Observed Evidence: Two administrators noted that invoices over $10,000 get delayed by an average of 9 days because approvals require an email chain rather than in-app triggers.
  • Proposed Solution Concept: Conditional routing rules for invoices exceeding custom dollar thresholds.
  • Validation Metric & 2-Week Test: Create a clickable Figma prototype showing automated multi-tier approval setups and test usability with six finance leads; pass criteria is five completing setup in under three minutes without guidance.
  • Data to Verify: Verify the average time-to-paid metric on invoices above $10,000 versus those below $10,000 across your active customer base.
Written by AI from this prompt. Your results will vary.

Paste your raw call notes or synthesis document into Claude, Gemini, or ChatGPT. If you have analytics data, follow up by asking which hypothesis carries the highest commercial risk.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Meetings & Notes