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 #2

The RFC (Request for Comments) Proposal Process

In mature engineering organizations, any significant change to the design system begins with an RFC (Request for Comments). An RFC is an open design document that describes a problem, explores alternatives, and proposes a specification before writing code.

The lifecycle of a design system RFC typically includes:

  • 1. Problem Statement: What user or squad pain point does this address? (e.g., 'Squads lack an accessible multi-select dropdown').
  • 2. Prior Art & Research: How do other systems (Shopify Polaris, Material, Primer) solve this?
  • 3. Proposed API & Spec: Visual Figma specs, accessibility keyboard maps, prop types, and token dependencies.
  • 4. Open Community Feedback: A 7–14 day review window for designers and engineers across the company to critique the proposal.
  • 5. Decision & Merging: Approved proposals enter the system roadmap; rejected proposals clearly document why.

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