Design systems panel discussion
summary
Panelists describe taking six local design systems and merging them into a single product-plus-service with documentation, training and an accessibility push; they use Tableau analytics and component counts to be objective, build dashboards and monitor component usage in code (engineering investment required) and adopt a federated governance and design‑ops funnel so updates can be iterative releases rather than yearly launches. Claims: reuse reduced duplication, measurable adoption guides priorities, and governance plus ops determines whether the system scales.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:44Question of the hour
- 3:38Product vs Service
- 4:28Product or Service
- 5:42Stakeholders
- 9:09Linking
- 10:17Maturity
- 20:19Governance
- 26:29Change
- 33:04Time constraint
- 34:59Conclusion
related talks
46mBuilding & Managing Design Systems
25mPanel discussion about design systems
27mFoundations of Design Systems
18mDesign Systems in Practice
23mDesign Systems 101
01h 03mDesign System Pitfalls & How to Escape Them
57mUnifying design and development through design systems
41mHow to Maintain a Design System