measure-experiment-design

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# Experiment Design
3 
4An experiment design document defines all parameters needed to run a rigorous A/B test or controlled experiment. It ensures the team aligns on what you're testing, how you'll measure success, and how long to run the test before drawing conclusions. Good experiment design prevents common pitfalls: underpowered tests, unclear success criteria, and decisions based on noise rather than signal.
5 
6## When to Use
7 
8- Before launching an A/B test to validate a product change
9- When testing a hypothesis that requires quantitative validation
10- After solution design to validate assumptions before full rollout
11- When stakeholders want data-driven evidence for a decision
12- To establish a culture of experimentation and learning
13 
14## When NOT to Use
15 
16- The hypothesis itself is not yet articulated -> use `define-hypothesis` first; this skill designs the test for a claim you already have
17- You are analyzing a completed experiment -> use `measure-experiment-results`
18- You need the event tracking that will measure the experiment -> use `measure-instrumentation-spec`
19- You are gathering opinions rather than running a controlled test -> use `measure-survey-analysis`
20 
21## Instructions
22 
23When asked to design an experiment, follow these steps:
24 
251. **Articulate the Hypothesis**
26…