CRO Glossary
Design System
A shared library of reusable UI components, patterns, and standards that ensures visual and functional consistency across a product.
A design system is the set of documented components (buttons, forms, modals, typography, color tokens) and rules that designers and engineers use to build interfaces consistently. In the context of experimentation, it matters because it directly affects how fast and how reliably teams can build and ship test variants — a mature design system means a new CTA style or layout variant can be assembled from existing, pre-approved components rather than built from scratch.
Well-governed design systems also reduce the risk that a winning test variant introduces inconsistencies elsewhere in the product, since components are shared and centrally maintained rather than duplicated per page. This is especially relevant for server-side or full-stack experimentation, where variants need to be production-quality rather than throwaway JavaScript overlays.
The flip side is that rigid design systems can slow experimentation velocity if every new test idea requires a formal component request or design review. Teams that experiment heavily often maintain a lightweight 'sandbox' layer within their design system specifically for test variants, so they can iterate quickly without polluting the core library with one-off styles.
Example: a product team wants to test five different button styles for a checkout CTA. Because their design system already defines button size, color, and state tokens, engineers can produce all five variants in an afternoon instead of a multi-day design and build cycle.
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 design system.
Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.