Growth experiment review

Growth Experiment Team

A growth analyst prepares plans and readbacks while an independent reviewer reproduces the evidence and gates the decision.

Growth decisions backed by completed experiments

Turn approved growth tests into timely, reproducible decisions without losing negative or inconclusive evidence.

growth-experiment-review

Pre-registers a cross-channel growth experiment, validates its fixed measurement contract, reads source-backed results, and prepares a bounded human decision without changing live work.

Review due growth experiments

Review Growth Experiment Register rows whose fixed readback date is due and whose status is approved, running, or due. Run the Growth experiment review workflow with the Growth Analyst assigned. The run must use each row's pre-registered windows, primary outcome, downstream business signal, diagnostics, guardrails, sample, duration, attribution, decision rule, and named sources. Missing access, immature signals, tracking changes, low volume, or confounders remain visible and can produce keep testing or unproven. The Experiment Reviewer independently reproduces material evidence before the packet reaches human approval. The run succeeds only when it produces a source-backed decision packet or a clear blocked-evidence report. It never launches, promotes, pauses, rolls back, publishes, sends, edits, retargets, changes a budget, or updates either ledger without the explicit approvals in the workflow. ## Professional quality control Objective: complete the recurring Growth experiment review operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Verify audience, offer, substantiation, platform limits, configuration, attribution readiness, and worst-case spend against the approved cap. Public copy must be specific and on-voice, with no generic AI phrasing, filler, hype, fake urgency, unsupported superlatives, repetitive cadence, or claims that exceed the evidence. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.

Growth experiments