Home
Bookmarks
Leagues
LEARN
Courses
Career Paths
Assessments
Tutorials
Arcade
Glossary
GROW
Certifications
Log in
Glossary
Log inSign up
Courses/Introduction to Design Systems/Governance Principles & Contribution Models/
Exercise #9

Challenge: Architecting an Enterprise Contribution Flow

Consider a high-growth fintech with 150 engineers across 12 product squads. The checkout squad needs a customized 'CountdownTimer' component for flash deals within two weeks.

Applying our governance principles:

  • Immediate Squad Need: The squad builds the component locally in their checkout feature branch, strictly using design system tokens (color-bg-warning-subtle, space-12, font-mono-tabular).
  • RFC Evaluation: The squad submits an RFC proposing the component for @system/lab. During review, the marketing and travel squads confirm they also need flash-sale timers.
  • Promotion: The checkout squad authors the component in the Lab package with visual regression tests and accessibility documentation, where it is approved and merged.

Topics

The 3 Organizational Models for Design Systems
The RFC (Request for Comments) Proposal Process
Decision Trees: 'Should This Be in the Design System?'
The Component Incubation & Promotion Pipeline
Semantic Versioning (SemVer) for Design Systems
Automated Visual Regression Testing (Visual QA)
Community Stewardship: Office Hours & Design Guilds
Writing Actionable Changelogs & Release Notes
Challenge: Architecting an Enterprise Contribution Flow
design

From lesson

1

Governance Principles & Contribution Models

Level 2 · Core Principles & Governance

Top contributors

Community contribution details will appear here once real learner activity is available.

Share