measure-experiment-results

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# Experiment Results
3 
4An experiment results document captures what happened when you tested a hypothesis, including statistical outcomes, segment analysis, learnings, and clear recommendations. Good results documentation turns individual experiments into organizational knowledge that improves future decision-making.
5 
6## When to Use
7 
8- After an A/B test or experiment reaches statistical significance
9- When an experiment is ended early (for any reason)
10- To communicate findings to stakeholders who weren't involved
11- During decision-making about whether to ship, iterate, or kill a feature
12- To build a repository of learnings that inform future experiments
13 
14## When NOT to Use
15 
16- The experiment is not designed or run yet -> use `measure-experiment-design`
17- The results demand a direction decision -> use `iterate-pivot-decision`; this skill reports the evidence, that one decides
18- You want the transferable learning banked for the organization -> follow up with `iterate-lessons-log`
19- Your data is survey responses, not a controlled experiment -> use `measure-survey-analysis`
20 
21## Instructions
22 
23When asked to document experiment results, follow these steps:
24 
251. **Summarize the Experiment**
26   Provide context: what was tested, when it ran, how much traffic it received. Link to the original experiment design document if one exists.
27 
282. **Restate the Hypothesis**
29…