When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
Expert guidance for designing statistically valid A/B tests and experiments.
Provides a structured hypothesis framework, sample size calculations, and metrics selection (primary, secondary, guardrail) to ensure rigorous test design Covers test types (A/B, A/B/n, MVT, split URL), traffic allocation strategies, and implementation approaches (client-side vs. server-side) Includes pre-launch checklists, guidance on avoiding common pitfalls like early peeking, and frameworks for analyzing results with statistical significance Helps determine baseline requirements, minimum detectable effect, and test duration based on traffic volume and conversion rates
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
