Use controls when feasible
- Baseline
- IF
- OR
- THEN
- ELSE
The decision
- IF
- comparable untreated pages, clusters, regions, or time periods exist
- THEN
- use a control or difference-in-differences design
- ELSE
- use interrupted time series with explicit limitations
- Primary metric
- estimated incremental lift
- Guardrail
- control contamination
- Reason
- Makes the decision explicit, measurable, and reversible where possible.
- LAKA levels
- Baseline
- Operators
- IF
- OR
- THEN
- ELSE
- Governs gates
- measurement
- Source
- 04-IF-ELSE-AND-OR-RULEBOOK.md — EXP-006 — Use controls when feasible
The other eleven rules in Measurement and Experimentation
- EXP-001 Require a mechanism hypothesis IF an intervention has no stated reason it should affect an outcome Baseline
- EXP-002 Capture a baseline IF a change is about to be implemented Baseline
- EXP-003 Use a change ledger IF any SEO-relevant production change occurs Structural
- EXP-004 Choose one primary metric IF an experiment has many possible success metrics Baseline
- EXP-005 Set guardrails before launch IF a change can improve the primary metric while harming quality, accessibility, revenue, or trust Baseline
- EXP-007 Account for seasonality and external events IF demand, algorithms, campaigns, news, inventory, or holidays can affect the outcome Baseline
- EXP-008 Represent uncertainty IF sample size is small, variance is high, or exposure is incomplete Baseline
- EXP-009 Allow processing and learning time IF a change has not had enough crawl, index, ranking, or behavioral exposure Baseline
- EXP-010 Distinguish single-variable and package tests IF several material variables change together Minor
- EXP-011 Escalate by diagnosed mechanism IF a lower-level LAKA intervention fails Minor
- EXP-012 Use explicit continue/revise/revert/retire decisions IF a review point is reached Baseline
This rule as JSON: GET /v1/rules/EXP-006