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
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
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.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Reframe a feature request into a core user problem
Break down prescriptive feature requests into underlying user motivations, workflow bottlenecks, and testable problem statements.
Write a Customer Interview Script That Validates a Problem with Past-Behavior Questions
Get a 30-minute problem-discovery interview script with past-behavior questions, two follow-up probes each, banned-question rewrites and evidence signals.
Draft Multi-Tier SaaS Product Packaging and Feature Matrix
Generate a clear, competitive feature matrix for your SaaS product that aligns tiered capabilities with specific user upgrade triggers.
Transform Customer Interview Transcripts into Ranked Pain-Point Matrix
Turn raw interview notes into a structured matrix that ranks customer pain points by frequency and business impact to guide your product roadmap.
Design an A/B Test Plan with Sample Size Math and Pre-Set Stop Rules
Get a complete A/B test plan with one primary metric, a clear hypothesis, a worked sample size calculation, runtime, and stop rules fixed before launch.
Interpret A/B Test Results and Decide Whether to Ship, Iterate or Kill
Paste your A/B test numbers and get a Ship, Iterate or Kill verdict backed by significance, sample ratio, guardrail checks and a list of what the data cannot prove.
- Analyze customer feedback using Jobs to Be Done
- Draft a working-backwards press release and FAQ
- Synthesize User Interview Notes into Counted Themes and Insights
- Define beta cohorts and launch exit metrics
- Schedule phased customer communications for feature sunsetting
- Construct a quarterly product review executive narrative