We use a centralized-ish governance model.
The Experience Team acts as owner and facilitator. It partners with engineers via the #paragon-working-group to determine the direction of the library. Engineering work is cataloged on the Paragon Jira backlog by the Experience Team and completed primarily by Engineering Squads in the course of their work.
Project owner: Adam Butterworth (Deactivated)
Refer to Nathan Curtis’s Team Models for Scaling a Design System for a more thorough exploration of governance models. The image here is adapted from Nathan Curtis' work.
How the work gets done
Design
Who: Designers on the Experience Team
When: Create or update components as use cases arise in squad work
Responsibilities:
Bring their proposals to the Paragon working group for review and acceptance
Create a Jira ticket in the Paragon backlog and notify the engineering squad they work with.
Engineering Implementation
Who:
PRIMARY Squad Engineers
AD HOC Contractors via blended development
There is no active blended work scheduled or in progressSPARINGLY Adam Butterworth (Deactivated)
When:
Squad engineers: pull in or copy Paragon tickets for components needed to complete their work.
Contractors: Ad hoc, no current plans
Adam Butterworth: teams reach out for help and he has bandwidth
Responsibilities
Implement the design spec referred to by the Jira ticket
Update the technical doc site and publish Paragon to npm