Draft a Zero-to-One Product Discovery Experiment Card

Generates a structured, one-page test card with a falsifiable hypothesis, cheap validation test, and numeric kill threshold for new features.

You getHypothesis, test Method & Setup and metric & Threshold

Prompt

Prompt
Act as a principal product manager specializing in lean discovery. Your job is to turn an unvalidated product or feature idea into a single-page discovery experiment card.

Ask me 3 brief questions first, one by one or together in a single numbered message, and wait for my response:
1. What is the target customer segment and the specific problem you want to solve?
2. What is the proposed solution or feature concept?
3. What resources or channels do you currently have access to for fast testing?

Rules:
- State the core falsifiable assumption as: "We believe [user segment] will [perform action] because [underlying motivation]."
- The test method must be runnable in under 10 business days with zero engineering code (e.g., painted-door test, manual concierge, customer calls, landing page).
- Specify exact numerical pass and fail criteria, including sample size.
- Identify one critical failure mode where false positives could mislead the team.

Output format:
- Hypothesis: (one sentence)
- Test Method & Setup: (bulleted steps, timeline, and tooling)
- Metric & Threshold: (target sample size, minimum viable success metric, kill trigger)
- Primary Risk & Mitigation: (bias or misleading signal to watch for)

End with one brief line on what technical or regulatory unknowns this test does not evaluate.

Example output

Example for: an automated recurring invoice chasing tool for freelance graphic designers.

Hypothesis:
We believe freelance designers with 3 or more active clients will connect their bank and email accounts to automate late-payment reminders because they feel uncomfortable confronting clients directly about overdue money.

Test Method & Setup:

  • Set up a single-page Carrd site explaining the automated payment chaser feature, highlighting hands-off client follow-up.
  • Route traffic by posting the offer in three verified Slack and Discord communities for freelance creatives with an introductory video walkthrough.
  • Add a primary CTA reading "Connect Bank & Schedule Follow-ups" that leads to a simulated connection modal, followed by a polite message: "We are onboarding beta users in cohorts. Enter your work email to get instant access in batch one."
  • Run the campaign for 7 calendar days with a $0 ad spend budget, relying on organic community engagement.

Metric & Threshold:

  • Sample size: 250 unique landing page visits from target freelancers.
  • Minimum viable success metric: At least 12% (30 users) click the primary connection CTA and enter a valid email.
  • Kill trigger: Less than 5% (12 users) complete the intent form, indicating polite interest without actual adoption urgency.

Primary Risk & Mitigation:

  • Risk: Upfront clicks might indicate interest in general cash-flow advice rather than willingness to surrender automated communication to clients.
  • Mitigation: Send an immediate automated follow-up survey asking respondents to upload an actual redacted unpaid invoice to qualify for priority access.

This experiment validates customer demand and emotional intent, but does not evaluate open-banking API reliability or regional payment compliance.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Enforces a standard falsifiable hypothesis structure rather than vague goals.
  • Bans engineering code to ensure the proposed test runs quickly and cheaply.
  • Requires explicit numerical kill triggers to eliminate confirmation bias.

Use this prompt in ChatGPT, Claude, or Gemini before writing code for an unverified feature idea. Have your rough customer segment and value hypothesis ready.

Common edits

  • Change the test timeline constraint from 10 days to 48 hours for ultra-rapid validation.
  • Add a constraint requiring a paid pre-order or deposit to test extreme monetization willingness.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Product Management