Operating model / Governance
Who decides, who contributes, what gets removedGovernance is three published answers: who can change the system, what the bar for a change is, and how disagreements get resolved. Write them down before the first contested PR, not after.
Choose the governance model that fits your organization's culture, size, and maturity level.
Single team owns and controls the design system
Small organizations, early-stage design systems
Multiple teams contribute with shared ownership
Medium to large organizations with multiple product teams
Community-driven with voting mechanisms
Open source projects, highly collaborative cultures
Combines elements from multiple models
Large, complex organizations with diverse needs
The test of a contribution model: a product engineer can find out in five minutes whether their component belongs in the system and what it takes to land it.
Different decisions carry different weight. A token tweak shouldn't wait on a committee; a breaking change should never skip one.
3-5 weeks
Design System Lead
4-6 weeks
Design System Committee
1-2 weeks
Design Lead
3-6 months
Design System Lead + Engineering Lead
Nothing gets removed without warning. Semantic versioning sets the contract; a fixed sunset timeline gives consumer teams a codemod-backed window to migrate.
Every decision type above names an owner. These are the roles those names resolve to.
Start with a simple governance model and evolve it as your design system matures and your organization grows.
Too many decision makers: Avoid committees that are too large or have unclear authority.
No clear escalation path: Define how conflicts and deadlocks get resolved.
Rigid processes: Build in flexibility for urgent fixes and special cases.
You'll know it's working when RFCs get answered inside the SLA, product teams land contributions without escalating, and nobody ships a fork because the front door was too slow.
The playbook chapter goes deeper on the same ground — centralized vs federated vs open, RFC discipline, funding — sequenced into the 90-day path. The workflows page is where the model you picked above runs day to day: the four-stage pipeline every contested change moves through.
