“What Happens Next? Everything That Comes After Setting Up Your Desi…”
summary
Design system at Salesforce launches in 2015 and scales by running three major releases a year, with standards reviews for two weeks before each release, office hours twice a week, and a core UX engineering team of six or seven supporting roughly 30,000 internal users. Key tools include a live component builder called Previewer and a designer-editable Guidelines repo on GitHub. Pain points: missing docs, brittle automated release notes, and testing for HTML/CSS-only components. Taxonomy additions (annotations, patterns, types, properties) fix architecture and governance.
AI-written summary · about
chapters (11)
- 0:00Introduction and setup
- 2:10Maturing design systems
- 4:21Maintaining components
- 6:32Driving adoption
- 9:06Supporting users
- 12:45Documentation challenges
- 15:16Tooling for efficiency
- 16:44Strategy and architecture
- 20:40Shared governance
- 22:30Communication gaps
- 25:42Q&A session
