Building a design system for scale & web accessibility

Problem

As our platforms grew, so did the chaos. Without a shared design language, every new feature felt like reinventing the wheel. We needed to unify our products and transition from legacy code.

Design value

A living design system adopted by 3 designers and 2 development teams, from junior to senior level.

Improved web accessibility.

Faster shipping through modular, reusable UI built with web components.

Role

Leadcraft, strategy, and rolloutof  design system with product owners.

Work with developers to untangle legacy constraints.

Key learning

Prototypes helped cross-functional teams understand the vision.

Helping product leaders & developers see the vision before launch made our goals tangible.

Before

Legacy UI was a mix of Bootstrap and custom code that wasn’t easily manageable.

Building and designing with legacy delayed project timelines.

Custom codes increased UI inconsistencies across pages.

Onboarding new developers took long and mistakes were frequent.

After

Developers and designers work in sync using a shared library. Now all team members can interact with a web component live in code.

We sweat the details on components and patterns so they can be re-used across channels and devices. This gives designers and developers more time for problem-solving and research.

Designing for joy
Cross-functional collaborator
Systems thinker
Case study 1Case study 2Case study 3