Secrets to a Successful Design System
summary
Design system work focuses on productivity not aesthetics and delivers measurable gains: a 12 month build rolls out to three major applications and uses design tokens and a CSS compatibility layer to cover non‑React surfaces. Change management includes canary builds, deprecation notices and automated critical‑path tests after a one‑line button change (missing type defaults to submit) breaks forms. Governance moves from a blocking service team to inner‑source maintainers and KPIs show improved speed, quality and ease of contribution.
AI-written summary · about
chapters (35)
- 0:00Introduction
- 1:55What is a design system
- 4:17Envision Guide to Design Systems
- 5:31Why Design Systems
- 5:54Design Systems are Hard
- 6:27Idea
- 7:23Start with an idea
- 7:40Get buyin
- 8:40Business hat
- 9:06Threats
- 10:49Design Systems
- 11:51Tech Stack
- 12:13Design System
- 12:44Design Tokens
- 13:45CSS Only Version
- 14:23Continuous Delivery
- 14:52Example
- 15:49Design systems are a dependency
- 16:37deprecating
- 16:59Critical Path
- 17:28Release Candidate
- 17:51Maturity
- 18:05Bugs
- 18:46Service team
- 19:17Innersource model
- 20:02Collaboration is the key
- 20:36What have we learned
- 20:46The world is bigger than react
- 20:59Design systems are dependencies
- 21:23How do I know if I made a successful design system
- 21:40Key performance indicators
- 22:03What did we get out of it
- 22:33Speed
- 23:23Perfection
- 24:36Thank you
related talks
41mHow to Maintain a Design System
12mDesign Systems-Revamping Products for Consistent UIs
23mDesign Systems 101
01h 03mDesign System Pitfalls & How to Escape Them
41mBuilding a design system with React in 2025, what's new?
22mDesign Systems, when and how much? — Diana Mounter
56mDesign System as a Product
35mDesign system - From a Developer Point-of-View