You've Built a Design System - Now What?
summary
Carbon runs 38 components across three libraries and successfully onboarded ~90 teams. Governance uses GitHub issue templates, a pinned code of conduct, and biweekly component check-ins to stop ad hoc overrides. Adoption grows through being available, exhaustive docs, demos of measurable wins (accessibility, performance), and publishing roadmaps 3–4 months ahead. Contributions accept multiple entry levels; a complex data table ships lightweight then undergoes a 3–4 month redesign with breaking HTML changes to add functionality. Team rituals include Thursday hack time and regular celebration to sustain momentum.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:11Governance
- 4:05Code of Conduct
- 6:05Design System Governance
- 7:48Design System Adoption
- 11:38Design System Maintaining
- 15:31Design System Growth
related talks
41mHow to Maintain a Design System
46mBuilding & Managing Design Systems
23mBuilding an open source design system for the many
38mDesign systems panel discussion
31mDesign System & Community
18mDesign Systems in Practice
45mPaving the adoption path of your Design System for engineers
26mKeeping your design system alive