Contribution model
A contribution model defines how product teams add to or change a design system — RFC process, code-review expectations, design review, who can merge, what testing is required. It's the practical mechanism that turns governance from policy into practice.
The strongest models are explicit: a one-page diagram of "if you want to propose a token, follow this; if you want to add a component, follow that". The weakest are tribal knowledge that newcomers hit walls against. Common patterns include a "core + community" split (core team owns critical primitives, contributors propose new components), inner-source PR workflows, and dedicated office hours. Nathan Curtis's writing at Eightshapes is the canonical reference.
Related: Design system governance · Federated design system · Versioning · Design system maturity