CRO Glossary
ICE Score
A prioritization framework that scores experiment ideas on Impact, Confidence, and Ease to rank what to test next.
ICE stands for Impact, Confidence, and Ease. Each proposed test is rated on these three dimensions, usually on a 1-10 scale, and the scores are averaged or multiplied to produce a single priority score. Teams then sort their backlog by this score to decide what to build and test next, rather than relying purely on gut feeling or whoever argues loudest in a meeting.
Impact estimates how much the change could move the target metric if it works. Confidence captures how sure the team is that it will actually work, based on prior data, research, or analogous tests. Ease reflects the effort and engineering cost required to build and ship the test. A high-impact idea that takes five sprints to build might score lower overall than a modest but nearly-free copy change.
The appeal of ICE is speed: it's lightweight and lets a growth team triage dozens of ideas in an hour. The tradeoff is that the scores are subjective and easy to game, since anyone can inflate a favorite idea's Impact or Confidence rating. Many teams pair ICE with a second, more rigorous framework like PIE or a formal experiment prioritization framework once the backlog gets large, using ICE mainly as a fast first pass.
For example, a team comparing 'add trust badges near checkout' (Impact 6, Confidence 7, Ease 9) against 'rebuild the entire checkout flow' (Impact 9, Confidence 5, Ease 2) would likely test the trust badges first, since the combined score is higher and the risk of wasted effort is much lower.
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 ice score.
Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.