Why governance matters
Without clear rules, systems drift. Teams copy components, tweak them locally, and the library becomes a suggestion. With too many rules, teams route around it. Governance is the balance between consistency and speed.
Three models
| Model | How it works | Best for |
|---|---|---|
| Centralized | A core team owns and builds everything | Small organizations, early systems |
| Federated | Product teams contribute and a core team curates | Larger organizations with many teams |
| Hybrid | A core team owns foundations, teams contribute patterns | Growing organizations |
A simple contribution flow
Propose
A short template describing the need, the use cases, and the proposed design.
Review
The core team checks it against criteria: reuse, accessibility, consistency.
Build
Design and code are done together, with tests and documentation.
Release
Publish a new version with a changelog.
Criteria for adding a component
- It is needed by at least two teams or features.
- It cannot be created by composing existing components.
- It meets accessibility requirements.
- There is an owner to maintain it.
Keep the system healthy
Review usage every quarter. Remove what nobody uses, merge near-duplicates, and fix pain points that show up in feedback. Hold a regular open session where consumers can ask for help and share what they need.



