Framework · Design systems · 3 min read
Design system governance models
Four ways to own a design system (solitary, centralised, federated, hybrid) and how to pick the one that fits your organisation. Federated or hybrid usually fits distributed enterprise teams.
One team or person makes the system for everyone. Risk: bottleneck.
Fits: early, small organisationA dedicated design-system team owns it.
Fits: mature organisation with budgetDesigners from many domains contribute; a core group curates.
Fits: designers spread across domainsA small core team plus federated contributors from the domains.
Fits: most enterprise organisationsUse it when
- You inherit a design system that one person or one team built, and every request now waits for them.
- Designers in several domains build their own components because the shared system doesn't move fast enough.
- You are asked to write a governance proposal: who owns the system, who contributes and who decides.
How to use it
- Describe how it works today. Write down who builds components, who decides what goes in, and how long a request takes. Name the current model honestly, even if nobody chose it. Output: "Today we are solitary / centralised / federated / hybrid, because…".
- Map where your designers sit. List the domains, how many designers each has, and whether there is budget for a dedicated design-system team. Output: a simple list of domains, designers and budget.
- Pick the model that fits. Solitary fits an early, small organisation. Centralised fits a mature organisation with budget. Federated fits designers spread across many domains. Hybrid (a small core plus federated contributors) is the most common at enterprise scale. Output: the chosen model and one sentence of reasoning.
- Define the roles. Name the core team that curates, the domain designers who contribute, and the council that decides on contributions, with members from several domains and a frontend lead. Output: a roles list with names.
- Set the cadence and the rules. Agree how often the council meets, how contributions flow (see Contribution process) and which patterns are required (see Pattern tiers). Output: a one-page governance proposal.
Worked example
An internal operations platform with 6 product teams and one designer in most domains. Today one design-system designer builds and approves everything, and the backlog keeps growing.
| Question | Answer |
|---|---|
| Model today | Solitary: one person makes the system for everyone. Risk: bottleneck. |
| Where designers sit | One designer in each of 6 domains, no budget for a full design-system team. |
| Chosen model | Hybrid: a small core (the design-system designer and one frontend developer) plus federated contributors. |
| Core team | Curates, keeps quality and versioning, runs releases. |
| Contributors | Domain designers propose and help build patterns from their domains. |
| Council | Core team, three domain designers on rotation, the frontend lead. Bi-weekly review. |
Watch out for
- The overlord. In a solitary model, one person decides for everyone and becomes the bottleneck. Plan to move away from it as you grow.
- Federated with no core. If everyone contributes and nobody curates, quality and consistency drift. Someone must own the whole.
- Copying a model from a bigger company. A centralised team needs budget and a mature organisation. Pick the model your reality supports.
- Only a project. A design system is an internal product with users (designers and developers). It needs a roadmap, research and support, not just a launch.
Template
Copy this into a one-page governance proposal.
Design system governance proposal
Model today: Problems it causes:
Domains and designers:
Budget for a core team: Yes / No / Partial
Proposed model: Solitary / Centralised / Federated / Hybrid
Why it fits:
Core team (curates):
Contributors (propose and build):
Council (decides): members, cadence
Contribution flow: link to process
Pattern tiers: link to tier list
Review this proposal on:
- Design SystemsAlla KholmatovaBook · 2017 (Amazon)
- Design That ScalesDan MallBook · 2023 (Amazon)
- Team Models for Scaling a Design SystemNathan Curtis (external site)
- A Design System Isn't a Project. It's a ProductNathan Curtis (external site)
- Your Design System Needs an EnforcerNN/g (external site)
"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.