Speaker Panel Q&A
summary
Panelists report concrete practices and outcomes: tracking parity between Figma and code and component coverage percentages to prove impact, theming Postmates via the Uber base components, and supporting 58 brands by locking down foundational tokens and tiny primitive components. Teams run usability experiments across design and code, use napkin‑math ROI (hours saved × teams) to sell value, try Ditto for content components, and favor tooling that minimizes time from contribution to reintegration so contributions actually get shipped.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:55Panelist backgrounds
- 2:16Uber’s design monitoring progress
- 3:42Design system interview questions
- 5:26Sub-component trust structures
- 7:31Engaging teams in design systems
- 11:53Multi-brand system challenges
- 15:04Early design system ROI
- 18:34Accessibility and motion
- 21:06Promoting systems at agencies
- 23:56OS to brand mapping
- 25:42Content consistency management
- 28:54Incentivizing contributions
- 34:33Closing
