Skip to content

phuryn/pm-skills / pm-product-discovery/skills/brainstorm-experiments-new

brainstorm-experiments-new

Verified

Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.

Design Lean Startup Experiments (New Product)

Create XYZ hypotheses and design pretotype experiments to validate a new product concept with minimal effort.

Context

You are helping validate a new product concept: $ARGUMENTS using lean startup methodology.

If the user provides files (market research, landing page mockups), read them first.

Instructions

  1. Create an XYZ Hypothesis in the form: "At least X% of Y will do Z"

    • X%: The percentage of the target market expected to engage
    • Y: The specific target market (e.g., "mid-size luxury sedan buyers")
    • Z: How they will engage with the product
  2. Suggest 2-3 pretotype experiments to test the hypothesis with minimal effort. Consider:

    • Landing Page: Test interest by measuring sign-ups or clicks
    • Explainer Video: Test understanding and appeal through engagement metrics
    • Email Campaign: Test demand through response and click-through rates
    • Pre-Order / Waitlist: Test willingness to pay through skin-in-the-game commitment
    • Concierge / Manual MVP: Deliver the service manually to test value
  3. Key principles (Alberto Savoia, The Right It):

    • Skin-in-the-Game: Test willingness to pay — not just interest. Real commitment (time, money, reputation) is the only reliable signal.
    • Your Own Data (YODA): Collect your own data through experiments rather than relying on Others' Data (ODP) like market reports or analogies. "The market for your idea does not care about the market for someone else's idea."
    • Measure actual behavior, not users' opinions
  4. For each experiment, specify the hypothesis being tested, the method, the metric, and the success threshold.

Think step by step. Save as markdown if substantial.


Further Reading

finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 197kUpdated Claude CodeCodexVerifiedInstall