brainstorm-experiments-new
This skill generates quantified XYZ hypotheses and designs minimal-effort pretotype experiments to validate new product concepts using lean startup methodology. Use it when testing whether a target market will actually engage with a product idea, creating experiments like landing pages, explainer videos, or pre-order campaigns that measure real behavior rather than stated interest.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/brainstorm-experiments-new && cp -r /tmp/brainstorm-experiments-new/pm-product-discovery/skills/brainstorm-experiments-new ~/.claude/skills/brainstorm-experiments-newSKILL.md
## 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 - [How to Build the Right Product with Alberto Savoia (ex-Innovator at Google)](https://www.productcompass.pm/p/how-to-build-the-right-product-with) - [Testing Product Ideas: The Ultimate Validation Experiments Library](https://www.productcompass.pm/p/the-ultimate-experiments-library) - [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.