When Design Systems Lie
summary
Says most design systems are actually glorified component libraries and that components alone are necessary but not sufficient; documentation and education sit at the center, Figma and CSS are treated as tools, and design systems must be built to change and be informed by real usage. Gives a bank visual-identity system as a working example, warns that about 80% of variants go unused, and urges reality should inform design systems through testing, refactoring, and usage-driven standardization.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:45Why design systems matter
- 4:37Design systems in larger systems
- 8:51Understanding interconnected systems
- 12:20Six lies about design systems
- 13:44Design systems ≠ component libraries
- 17:35Documentation is required
- 21:49Design systems needn’t be complete
- 25:19Atomic design is not a linear process
- 28:50Design systems can’t predict the future
- 30:12Choices ≠ thoughtful design
- 34:06True purpose of design systems
- 45:19Beauty in design systems
- 47:50CSS as a creative tool
- 49:14Q&A
