...
Design and engineering work is distributed.
Decision making is centralized.
The three Partpart-time Paragon Leads act as owners and facilitators. They partner with designers and engineers via the #paragon-working-group and the weekly Paragon Working Group Meeting to coordinate work and make decisions on the direction of the system.
Work is cataloged on the Paragon Jira BacklogGitHub Project by Paragon Leads and the Experience Team. Work is completed primarily by Engineering Squads in the course of their work and through blended development initiatives lead by the Paragon Leads.
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.
Part-time Paragon Leads
Product Lead | Design Lead | Engineering Lead |
|---|---|---|
Marco Morales (Deactivated) vacant | Design resourcing escalation path: Michael Leary | Engineer resourcing escalation path: George Babey |
Paragon Working Group
The Paragon Working Group is an informal group of volunteer engineers and designers who meet weekly at the Paragon Working Group Meeting and discuss issues in #paragon-working-group Slack.
...
| Status | ||||
|---|---|---|---|---|
|
Supports the strategic direction of the system
Aids in chunking of work in JiraGitHub
Supports blended development initiatives
Serves as a champion and advocate among product leaders.
...
Provides feedback and approval on proposed design additions, technical additions, and architectural changes
May also assist with the responsibilities of the design owner and technical owner
Participate in a support and triage rotation to continue to maintain the design system.
Support discussion, questions, and learning about the design system
Engineering Squads
| Status | ||||
|---|---|---|---|---|
|
...