Design System as a Product
summary
Argues a design system is an internal product and shows concrete steps: interview research finds at least three drastically different designer workflows, build a tiny working component into the app during a five‑person, six‑week project, and that single page saves time and improves pairing. Uses Sketch, a component library, design tokens and lightweight docs. Recommends start small, use pilot teams, choose ownership like a core team or guild, and treat maintenance and funding as ongoing investments.
AI-written summary · about
chapters (4)
related talks
23mDesign Systems 101
18mDesign Systems in Practice
01h 03mDesign System Pitfalls & How to Escape Them
20mDesign Systems for the Rest of Us
25mPanel discussion about design systems
28mThe Three P’s of a Design System
25mHow to understand the perspectives in Product Design processes as a developer
12mDesign Systems-Revamping Products for Consistent UIs