Skip to content
UX Atlas
Design systemCraft conventionAdvanced

Design System Governance

Who decides what goes in, how changes are proposed, and how the system stays coherent as more people touch it.

Definition

Governance covers ownership, contribution, review and decision-making for a design system. It is what prevents a system from either ossifying or fragmenting as an organisation grows.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

On this page
  1. Definition
  2. Governance models
  3. What has to be written down
  4. Continue from here

Governance models

ModelHow it worksFails when
CentralisedA dedicated team owns everythingThe team becomes a bottleneck and loses touch with product needs.
FederatedRepresentatives from product teams share ownershipNobody has time, and decisions stall.
HybridA core team owns foundations, product teams contribute componentsThe contribution path is undefined, so nobody uses it.
Open contributionAnyone can propose, a small group reviewsReview capacity is exceeded and quality drifts.

What has to be written down

  • How to propose a new component, and what evidence is required.
  • The criteria for promoting something from one team's code into the shared system, usually a threshold of independent need.
  • Who reviews, and what the service level for review actually is.
  • The deprecation process, including notice periods and migration support.
  • How exceptions are granted and recorded, since undocumented exceptions become precedents.

Continue from here

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Principles behind this

The reasoning this solution is an application of.

Practical example

A worked decision where this was the deciding factor.

Short definition

The one-paragraph version, for when that is all you need.

Related concept

Connected closely enough to change how you apply this.