Case study · Mailchimp · 2024 – 2025
Design system refresh
Moving foundational components from spec to production, then getting product teams to actually use them.
- library adoption in 30 days
- ~50%library adoption in 30 days
- drop in component detaches
- 87%+drop in component detaches
- My role
- Program lead, design system refresh
- Worked with
- Design systems team, product design, front-end engineering
Context
Mailchimp's design system had drifted. Teams detached components to work around them, so the library and the product had grown apart.
A refresh is only worth doing if product teams adopt it, so adoption was the goal from the start.
Approach
- 01
Foundations first
We started with the components every page uses: buttons, page headers and the type scale. I moved them from spec to production with design and engineering working in step.
- 02
Adoption as a tracked workstream
Adoption and detach rates were tracked as program metrics, not left to chance, and each product team had a clear path to migrate.
- 03
Consolidating one-off patterns
Page headers had been rebuilt many times. We rolled one header component with audience multi-select across 14 high-traffic pages.
Outcome
- ~50% library adoption within 30 days of the foundational releases.
- An 87%+ drop in component detach rates over the same 30 days.
- One page header pattern across 14 high-traffic pages.