Module 8 of 12 · 7 min read
Design Systems & Standards Governance
How to govern a design system across distributed domains: governance models, contribution and pattern tiers, adoption without policing, and metrics.
Why it matters
Many new leads come from hands-on design-system work: building libraries, migrating tools, documenting components. The leadership step is moving from building the system to governing it: deciding how standards get made, adopted and evolved across domains, without becoming the bottleneck or the "design police." This is the Consistent practice pillar in the course's example practice model.
Sooner or later someone will ask you: "How would you handle teams that don't want to adopt shared standards?" Common pitfalls: enforcing by authority, reviewing every contribution yourself, and treating resistance as a people problem instead of a signal about the system.
1. From library to system to practice
| Level | What it is | Your role as lead |
|---|---|---|
| Component library | Figma + code components | Ensure quality, versioning |
| Design system | Components + tokens + patterns + guidelines + code + docs | Product strategy for the system |
| Standards practice | Principles, process standards, governance, adoption | Governance, community, decision rights |
Treat the design system as an internal product: its users are designers and developers. It needs a roadmap, research with its users, adoption metrics and support.
2. Governance models (after Nathan Curtis / EightShapes)
| Model | Description | Fits when |
|---|---|---|
| Solitary | One team/person makes the system for everyone | Early, small org (risk: overlord, bottleneck) |
| Centralised | Dedicated DS team owns it | Mature org with budget |
| Federated | Designers from many domains contribute, a core group curates | Distributed teams with designers spread across many domains |
| Hybrid (core + federated) | Small core team + federated contributors | Most common at enterprise scale |
Contribution process (lightweight)
- Need identified in a domain.
- Check: does an existing component/pattern solve it? (office hours / Slack or Teams channel)
- If no → proposal (problem, use cases from ≥2 domains if possible, draft).
- Council review (bi-weekly): accept as core / accept as domain-specific / reject with reason.
- Build + document + release notes.
- Announce in show & tell.
Classify patterns into tiers
| Tier | Rule |
|---|---|
| Core (buttons, inputs, tables, navigation shell) | Must use, consistent everywhere |
| Recommended patterns (filtering, bulk edit, empty states) | Use unless you have a documented reason |
| Domain-specific | Owned by domain, may graduate to core later |
| Experimental | Labelled, time-boxed, measured |
This gives you a clear answer on consistency vs autonomy: consistent where it serves users across tools; flexible where the domain context demands it, and transparent about which is which.
3. Driving adoption (not enforcing)
Why teams resist standards: components don't fit their case, the standard was decided without them, migration cost, slow contribution process, no visible benefit.
Adoption playbook
- Involve before you decide. Contributors from domains on the council.
- Make the right way the easy way. Good docs, templates, plugins, starter files.
- Show the benefit in their terms. Dev hours saved, fewer QA bugs, faster handoff. A before/after story from a past migration or rollout works well here.
- Pilot with a willing team, then publish the results.
- Migrate incrementally. "New screens use the system; old ones migrate when touched."
- Listen to rejection. A team refusing a standard often reveals a gap in the standard.
- Escalate rarely, and only for core tier and real user impact.
Answer template for "a team doesn't want to adopt":
"First I'd want to understand why: is the component missing something, is migration too expensive, or do they not see the value? Then I'd see whether it's a gap we should fix in the system, whether we can make migration incremental, and whether it's a core standard or a recommendation. For core standards that affect users across tools, I'd make the case with evidence and agree on a realistic timeline. Most resistance is information, not opposition."
4. Measuring the design system
| Metric | How |
|---|---|
| Adoption / coverage | % of screens/components from library (Figma library analytics; code imports) |
| Detachment rate | Figma: detached instances, a signal of misfit |
| Time to deliver | Design/dev time for standard features before vs after |
| Consistency defects | QA bugs tagged "UI inconsistency" |
| Satisfaction | Quarterly survey of designers & devs (e.g., "The DS helps me work faster", 1–5) |
| Contribution health | # proposals, cycle time from proposal to release |
Figma's library analytics (Organization/Enterprise plans) give you insertion/detach data. Check what your organisation's plan offers.
5. Beyond components: process standards
A UX "standard" can also be a process:
- Minimum research standard per project size (e.g., "M/L projects test with ≥5 users before dev").
- Accessibility baseline (WCAG 2.2 AA for new screens; European Accessibility Act awareness).
- Handoff standard: annotations, states, edge cases, numbered annotation markers that link specs to the design.
- Design QA checklist before release.
Rule: every standard needs an owner, a reason ("why this exists"), and a review date. If nobody can say why a standard exists, retire it.
Practice
Evidence to collect
Keep proof in your leadership log:
- Governance one-pager.
- Adoption case study with real numbers where they exist (timeline, number of domains or teams that adopted, sessions run, feedback).
Read / watch
Library → Design systems: Nathan Curtis (EightShapes) on governance/team models, Brad Frost Atomic Design, Alla Kholmatova Design Systems, NN/g Design Systems 101, Config talks on design-system adoption.
Talking about it
- "How would you handle teams that don't want to adopt?" Use the answer template in section 3. The core message: resistance is information; tiers make clear what is required and what is flexible.
- With your manager: frame the system as an internal product with users, a roadmap and metrics, not as a design-team hobby. Bring one adoption number and one satisfaction number.
- With engineering leads: talk about dev hours saved, fewer UI bugs and faster delivery. Invite a frontend lead onto the council.
- In a promotion or hiring conversation: tell your adoption case study as a change story (how you got people to adopt), not as a craft story (how good the components were).
Check yourself
Answer out loud, then open the section to compare.
- Why does a federated or hybrid model fit an organisation with designers in many domains? → answer
- What are the four pattern tiers? → answer
- Name two ways to measure the design system. → answer
Connections
← Module 7: DesignOps, Team Models & Capacity · UX Lead Course · Module 9: UX Maturity & Measurement →
Related
- 11 — Workshop techniques: run a design-system standard workshop with designers and frontend devs
- Module 10: Stakeholders, Influence & Change: Kotter & ADKAR for adoption
- Module 9: UX Maturity & Measurement: measuring the practice & the system
- Module 5: Enterprise & Internal Applications: consistency matters for expert users