Keeping your design system alive
summary
Argues that a design system survives only with concrete processes: assign a lead, keep a public roadmap (the vanilla framework used a Trello board), and run biweekly working‑group meetings plus two‑week sprints and occasional 2–3 day mini‑sprints. Uses Figma and GitHub for cross‑platform collaboration and contribution tracking, tests documentation by pairing teams to migrate sites, and enforces a documentation step in the workflow. Sets measurable goals (example: 50% team adoption) and reports that scheduled maintenance epics and regular meetings put someone in charge have a roadmap be open.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 4:02Assign a project lead
- 6:09Create a roadmap
- 8:59Be open and inclusive
- 13:14Define contribution process
- 15:59Maintain documentation
- 19:15Centralize resources
- 20:20Plan for maintenance
- 24:16Summary and recap
related talks
44mManaging Design Systems with
41mHow to Maintain a Design System
19mDesign Systems: How to Foster Participation
50mManaging Design Systems, from Features to Roadmaps
19mYou've Built a Design System - Now What?
28mThe Three P’s of a Design System
46mBuilding & Managing Design Systems
21mExpanding your Design System's sphere of influence and other lessons