Design System Governance & Contribution
A design system needs rules for change as much as it needs components. Product teams want a way to propose something new, a promise that an update won’t break their screens overnight, and room to step outside the system when their users need something it doesn’t cover.
Release practice is close to settled. 13 of 14 sources use semantic versioning, and 9 of 10 deprecate a pattern for a while before removing it. Staffing varies more. 8 of 14 run a core team with contributors from product teams, and the other 6 keep the work centralized. All 4 sources that cover exceptions let product teams deviate when it clearly serves their users, with no sign-off from the core team.
- systems tracked
- 19
- sources cited
- 21
- evidence cards
- 168
- questions tallied
- 7
Popular questions
Each one is researched across every system we track. Pick one and it opens in chat, ready to send.
Systems tracked
The same core design systems are tallied on every topic, so answers compare like with like. See every source
- GOV.UK
- IBM Carbon
- Shopify Polaris
- Google Material 3
- Atlassian
- GitHub Primer
- Adobe Spectrum
- Microsoft Fluent
- Salesforce Lightning
- Ant Design
- Mozilla Acorn
- Stripe Apps
- shadcn/ui
- Porsche Design System
- Base Web
- GitLab Pajamas
- Radix UI
- USWDS
- Pinterest Gestalt
Got a design system governance & contribution question?
Your first 3 questions are free. Every answer comes with the sources behind it.