A/B Testing for Product Managers
Before You Build: Deciding Whether to Test
Before You Build: Writing and Stress-Testing a Hypothesis
Before You Build: Choosing Your Metrics
Before You Build: Sample Size and Duration
Running It: Pre-Launch Review
Reading It: Reading a Result Honestly
Reading It: Auditing for the Six Lies
Afterwards: The Test Readout
Checking Yourself: Is Testing Right for Your Situation?
Lesson 9
Afterwards: The Test Readout
Write up my result as a one-page record. [paste hypothesis, decision table, result,
guardrails]. Structure: WHAT WE TESTED AND WHY (the change and the evidence); WHAT WE
EXPECTED (hypothesis including predicted effect size); WHAT HAPPENED (result with range,
guardrails, duration, sample, state plainly whether we detected an effect); WHAT WE
DECIDED AND WHY (referenced to the pre-declared table, noting any departure); WHAT WE
LEARNED ABOUT OUR USERS (the most valuable section, what belief has changed?); WHAT THIS
DOESN'T TELL US (honest limitations); WHAT WE'D DO DIFFERENTLY. One page. Written so
someone finding it in a year understands the reasoning, not just the number.