Design Systems for the Rest of Us
summary
Small three‑person system team at a company with 120 developers and 14 designers builds a pragmatic design system by prioritizing adoption‑driven development and a Trojan Horse push into a flagship product. They ship tokens (JSON → CSS vars / Stylus / Android XML), React components implemented with React + styled‑components, and sketch libraries generated to ~80% (manual fixes remain). Components reach production quickly but accessibility and responsiveness are deferred until a later cleanup phase.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:12What is Design Systems
- 2:17Design Systems Venn Diagram
- 3:17Design Systems
- 4:00Adoption Driven Development
- 4:38Trojan Horse Strategy
- 5:15Consistency
- 7:53Components
- 8:22React Components
- 9:15React Style Components
- 10:30The Right Abstraction Layer
- 11:26Getting into Production
- 11:58Production Success
- 12:52Design Assets
- 14:37Benefits
- 15:14Sketch Library
- 15:55Documentation
- 16:44Design Guidelines
- 17:42Accessibility
- 18:06Dont follow everything
- 18:34Flexibility
- 19:14Cosmos
related talks
27mAdvanced Design System Considerations
18mDesign Systems in Practice
41mBuilding a design system with React in 2025, what's new?
46mBuilding & Managing Design Systems
56mDesign System as a Product
21mDesign Systems 101: The Developer Approach to Better Frontends
24mTiny Design Systems for Tiny Teams
28mLet's talk about design systems