A Practical Little Guide to Getting Started with a Design System
summary
A practical guide to starting a design system: how to identify UI components, set up documentation, and implement an initial "ambassador" component. Covers benefits like consistency and reusability and gives simple, low-friction steps to begin building and using a design system.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:03My design system failure
- 2:28Design system definition
- 3:53Convincing the team
- 6:01Why create a design system
- 9:10Concrete example: Sage app
- 10:15Identify users and team
- 12:22Assess existing work
- 15:55Prioritize components
- 19:28Prioritization criteria
- 24:24Create ambassador component
- 25:06Document the system
- 27:39Choose docs tools
- 30:27Organize naming
- 34:22Naming rules
- 35:26Document a component
- 37:31Component lifecycle
- 38:11Drive engagement
- 41:19Governance and new components
- 42:43Do only what's needed
- 43:05Q&A
related talks
44mA Practical Little Guide to Starting a Design System
46mA Practical Starter Guide to Creating a Design System
23mDesign Systems 101
27mA Practical Guide to Building Your Design System Infrastructure
18mDesign Systems in Practice
28mThe Three P’s of a Design System
32mIntroduction to Design Systems
41mHow to Maintain a Design System