Building & Managing Design Systems
summary
Panelists describe concrete tradeoffs: a 25–28 person design-systems group running a component library with Sketch/Figma designs and React implementations, multiple products (one example: 127 downstream apps) lagging on versions, CI/CD for cloud but 1–2 year on‑prem update delays, and measurable wins like fewer bugs and faster prototyping. Accessibility work targets WCAG and aria semantics (screen‑reader order matters). Contribution is pragmatic and often loosely governed with content and localization folded into the system.
AI-written summary · about
chapters (17)
- 0:00Design systems panel intro
- 1:26Panelists and backgrounds
- 4:15Pandemic hobbies
- 6:43Starting a design system
- 10:52Maintaining design systems
- 15:30Measuring success and justifying ongoing investment
- 16:14Splunk’s design system team
- 19:07PC Optimum rogue system
- 21:37Designers vs developers collaboration
- 25:07Splunk design system users
- 27:35Accessibility in design systems
- 31:03Legacy system evolution
- 33:53Evolving existing systems
- 35:57Design system contribution models
- 41:55Loblaw’s contribution model
- 44:01Localization in design systems
- 45:25Closing & Q&A
