Amanoba Logo
Back to Course

Change Management for the Design System

Day 22 of 30 · The Playbook 2026 – Masterclass for Designers

Run releases with RFC, review, QA, and communication.

Learning Goal

  • Change flow: RFC → review → QA → release.
  • Owners: design, engineering, QA.
  • Changelog and versioning are mandatory.
  • Communication: release notes + enablement.

Why This Matters

  • Uncontrolled changes break the system.
  • Transparency builds trust.
  • Helps adoption.

Explanation

  • RFC: problem, proposal, impact.
  • Review: design + dev + a11y.
  • QA: visual + functional + a11y.
  • Release: version, changelog, rollout plan.

Examples

Bad: Button changed from a Slack ping.

Good: RFC → review → QA → changelog → comms.

Guided Exercise

  1. Create an RFC template.
  2. Write a release note sample.
  3. Define owner roles.

Independent Exercise

Run an upcoming change through the RFC flow.

Self-Check

  • RFC template exists.
  • Release note sample exists.
  • Owners are clear.

Optional Deepening