brainstorm-experiments-existing
This skill helps product teams design low-effort experiments to validate assumptions about existing product features before full implementation. Use it when you need to test feature ideas cheaply, choose between design approaches, or plan product experiments through methods like prototypes, A/B tests, fake door tests, technical spikes, or behavioral surveys. The skill structures validation work by clarifying assumptions, suggesting appropriate experiment methods, and defining success metrics that focus on measuring actual user behavior rather than opinions.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/brainstorm-experiments-existing && cp -r /tmp/brainstorm-experiments-existing/pm-product-discovery/skills/brainstorm-experiments-existing ~/.claude/skills/brainstorm-experiments-existingSKILL.md
## Design Experiments (Existing Product) Design low-effort experiments to test product assumptions before committing to full implementation. ### Context You are helping a product team design experiments for **$ARGUMENTS**. The team has a feature idea and assumptions that need validation. If the user provides files (PRDs, assumption lists, designs), read them first. ### Instructions The user will describe their idea and assumptions. Work through these steps: 1. **Clarify the idea and assumptions**: Confirm what the team wants to build and what they need to validate. 2. **Suggest experiments** for each assumption. Consider methods like: - First-click testing or task completion with a prototype - Feature stubs or fake door tests - Technical spikes - A/B tests on production (with risk mitigation) - Wizard of Oz approaches - Survey-based validation (behavioral, not opinion-based) 3. **Key principles to follow**: - Measure actual behavior, not users' opinions - Test responsibly — don't put users or the business at risk - For production tests (e.g., A/B tests), explain risk mitigation strategies - Aim for maximum validated learning with minimal effort 4. **For each experiment**, specify: - **Assumption**: What do we believe? - **Experiment**: What exactly will we do to validate it? - **Metric**: What will be measured? - **Success threshold**: The expected value if we are right Think step by step. Present experiments in a clear table or structured format. Save as markdown if substantial. --- ### Further Reading - [Testing Product Ideas: The Ultimate Validation Experiments Library](https://www.productcompass.pm/p/the-ultimate-experiments-library) - [Assumption Prioritization Canvas: How to Identify And Test The Right Assumptions](https://www.productcompass.pm/p/assumption-prioritization-canvas) - [What Is Product Discovery? The Ultimate Guide Step-by-Step](https://www.productcompass.pm/p/what-exactly-is-product-discovery) - [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 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.
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.