Change Management for the Design System

Learning Goal

To understand the change management process for the design system and how it supports the design system's overall goals.

Who

Designers, engineers, QA specialists, and project managers.

What

Change management for the design system, including the flow of changes from RFC to release.

Where

In the design system context, focusing on the technical and communication aspects.

When

When changes are needed to the design system.

Why it matters

Change management is crucial for maintaining the integrity and quality of the design system. It ensures that all changes are tracked, reviewed, and communicated effectively, preventing uncontrolled changes that could break the system.

How

1. RFC (Request for Comment): Submit a detailed proposal outlining the changes, including the problem, proposed solution, and expected impact.
2. Review: Once the proposal is reviewed, it is shared with the design, development, and QA teams for feedback.
3. QA (Quality Assurance): Verify that the changes meet the quality standards, including visual, functional, and accessibility checks.
4. Release: Once approved, the changes are versioned, a changelog is updated, and a rollout plan is prepared to ensure a smooth release.

Guided Exercise

1. Create an RFC template for a hypothetical design change.
2. Write a release note sample for a recent design system update.
3. Define owner roles for a hypothetical design system project.

Independent Exercise

Run an upcoming change through the RFC flow and document the process.

Self-Check

• RFC template exists.
• Release note sample exists.
• Owners are clearly defined.

Bibliography (sources used)

• https://www.designsystems.com/governance

Read more (optional)