Design Systems
Disney Threads Design System
Four teams building one AR shopping app, each reinventing the other's buttons. We built the system that made them stop.
- Role
- Product Designer, Design Systems
- Duration
- 1.5 months
- Team
- 4 designers, 4 product teams
- Scope
- Tokens · Type · 10+ components
84% component reuse rate · goal was 80
The problem
Same product, four dialects.
Goals you can grade
If a design system's health isn't measured, it isn't known.
Color, earned not picked
The team voted on the primary brand color to keep Disney's visual identity intact, but the vote only decided the candidate. Each tint and shade then had to pass an accessibility review before entering the palette: contrast checked against WCAG guidelines, tested with color-blind simulations, and reviewed with accessibility experts.
Tokens and type
Tokens were organized by what they control rather than where they're used: color tokens for brand and UI, spacing tokens for layout, typography tokens for text. Naming had to read the same to a designer and a developer, so a handoff needs no translation layer: --brand-color-royalblue-500 means one thing to both.
Components, sourced from the teams
The library wasn't designed at a desk. It was harvested.
Documented to be used
Every component shipped with the same four-part documentation: anatomy (what each part is called), layout and spacing (the measurements), options (variants available), and states (active, disabled, focused, error, success).