Data Driven Design Systems in Practice
summary
Optimizely uses Axiom and Zeplin’s Omlet to quantify design system health: a CLI analysis produces dashboards that show component adoption over time, per-project core vs custom percentages, and a dependency tree that flags risky updates. The team counts ~50–60 Axiom components in one library and hundreds-to-thousands across products, surfaces zero-use components, prioritizes maintenance, projects adoption gains from replacements, and reports clearer stakeholder visibility and measurable migration progress.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:02What is a design system
- 2:48Building a design system from scratch
- 5:14Why Optimizely chose Omelette
- 7:19Demo of Omelette’s component adoption dashboard
- 9:25Tracking component adoption
- 11:34Detecting duplicate components
- 13:19Dependency trees for safe updates
- 14:21Prioritizing components by usage
- 15:47Business impact of data-driven design systems
- 17:09Omelette’s future roadmap
- 18:54Closing remarks
related talks
19mEvolving systems with data and heart
57mUnifying design and development through design systems
38mDesign systems panel discussion
52mLeaning Into Design Systems
20mFind Out If Your Design System Is Better Than Nothing
30mEvolutionary Design Systems
27m"Design Systems from 0 to 1"
20mDesign Systems for the Rest of Us