Design Systems

The Challenge

With over 20 teams and numerous products within the EY umbrella, maintaining design consistency was a systemic problem. Inconsistency didn't just create visual misalignment — it produced different interactions and interfaces across products that were meant to work together.

This fragmentation forced users to re-learn how each product worked, even when those products lived within the same workflow. The result was cognitive overhead, reduced trust in the platform, and a slower, less efficient audit process.

The Solution

We created Motif — a comprehensive design system that serves as the single source of truth for every team across EY's product portfolio. Rather than a static library, Motif is an ever-evolving resource, updated each sprint release and available to all designers in real time.

We collaborated with each team lead as a sounding board — so every team can bring in ideas and request what is needed. This co-ownership model ensures Motif reflects real product needs, not just top-down mandates.

What Motif Covers

Motif is structured around the principle that a design system should answer questions before they're asked. It covers every layer of the design stack — from foundational tokens to complex, context-specific patterns.

• Design tokens Color, typography, spacing, and shadow values as named variables, shared between design and code
• Component library Fully documented, responsive components with all state variants (default, hover, focus, error, disabled)
• Pattern library Compositional patterns for common UX scenarios: empty states, loading, forms, data tables
• Motion guidelines Standardized easing curves, durations, and interaction choreography
• Documentation Usage guidelines, accessibility notes, and do/don't examples for every component

Product Design Versioning

Before Motif could be adopted system-wide, we first needed to understand the current state of every product. We audited all EY Assurance products, defined which design version each belonged to, and created a phased alignment plan to bring everything into a consistent system without disrupting active development.

This versioning work gave us a clear migration path — and gave product teams confidence that the transition would be controlled, not chaotic.