CRO Glossary
Experiment Decision Log
A running record that captures not just experiment results but the reasoning and decisions made based on them.
An experiment decision log is distinct from raw experiment documentation in that it focuses on the judgment calls teams make around a test: why a test was launched, what tradeoffs were debated, why a borderline result was shipped or killed, and what assumptions informed the final call. While metadata and read-outs capture what happened statistically, a decision log captures the human reasoning layer that often gets lost once a test concludes.
This matters because experimentation programs accumulate institutional knowledge slowly, and without a decision log, teams tend to relitigate the same debates — for instance, repeatedly testing a similar urgency message because nobody remembers it was already tried and rejected for ambiguous results. A good decision log prevents redundant testing and helps new team members understand not just outcomes but the philosophy behind past calls.
For example, if a test shows a 2% lift that falls just short of the pre-registered significance threshold, the decision log would record whether the team shipped it anyway due to low implementation cost, held off pending a follow-up test, or deprioritized the idea — along with the stated rationale, so future analysts understand the context rather than just the number.
Over time, a well-maintained decision log becomes a valuable input to experiment prioritization frameworks, since it surfaces patterns in what kinds of hypotheses tend to pay off and which types of borderline results the organization has historically treated as ship-worthy or not.
Related terms
Shrinkage Estimator
A statistical adjustment that pulls noisy per-variant or per-segment estimates toward an overall average to reduce overfitting to randomness.
Flicker Test
A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.
Pre-Experiment Bucketing Audit
A review process confirming users are being randomly and evenly assigned to experiment variants before launch.
Above-Fold Exclusion Rule
A test-design rule that deliberately prevents changes to above-the-fold elements so an experiment isolates below-the-fold effects.
Flicker-Free Testing
A technical setup that prevents users from briefly seeing the original page before a test variant loads.
Orthogonal Test Design
A test structure where multiple variables are changed independently so their individual effects can be measured without interference.
See this in the wild
ABWatcher watches how top teams apply experiment decision log.
Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.