Design system

Design system

Design System Rebuild

I led the rebuild of Liberty’s Design System following a full migration from Adobe XD to Figma, powering 20,000+ pages on libertylondon.com. The new system prioritised simplicity, scalability, and seamless designer-developer collaboration.

It established a future-ready, inclusive foundation for digital growth.

Role

Role

Lead Design System Designer

Company

Company

Liberty London

Skills

Skills

Design System Architecture

Component Library Development
Design Token Management
Guidelines Documentation
Accessibility Compliance

Timeline

Timeline

Jan 2024 - Ongoing

Challenge

When the team shifted from Adobe XD to Figma in early 2024, the old design system proved too outdated and unusable.

For our team of 5 designers and 3 developers, a newly structured system became critical. Legacy components lacked structure, blocked efficient design, and slowed collaboration between design and development.

Strategic Objectives

To ensure the new design system met real needs across the organisation, I worked closely with stakeholders, designers, and developers from the start. I ran collaborative workshops to align on goals, audited legacy components, and established clear design principles focused on scalability, accessibility, and consistency.

Goals

Build a scalable design system in Figma to improve consistency, streamline designer–developer collaboration, and prepare for future tokenisation and a more accessible, modern UX.

Phase 1

Audit & Analysis

I reviewed all legacy Adobe XD files and frontend code. Key issues included duplicated components, visual inconsistencies, and accessibility gaps that hindered efficiency and scalability.

Phase 2

Foundation Building

I created a new file structure in Figma to establish clarity, reuse, and scalability. This included atomic organisation, manual design token setup, and foundational decisions around colour, typography, and component structure.

Phase 3

Component Creation

I built a robust component library in Figma using Auto Layout, variants, and interaction states. Accessibility, responsive behaviour, and developer-ready logic were embedded throughout to ensure long-term scalability.

Phase 4

Adoption & Handoff

I drove adoption through onboarding materials, component documentation, and a live request board in Monday. Close collaboration with developers ensured naming and behaviour aligned for smoother implementation.

Impact

A benchmarked review of design workflows and developer collaboration validated the impact of the new system.

Reduction in Component Duplication

70%

Designers now use fewer, more consistent components.

Faster Design Workflow

25%

Reusable variants accelerated common flows.

Dev-Ready Architecture

100%

Token-ready structure improved implementation.

Next Steps

As adoption grows, I’ll continue supporting dev implementation, introducing tokens and coded components, improving accessibility, and managing the Monday board to prioritise future requests across platforms.

© 2025 Yue Hu

© 2025 Yue Hu

© 2025 Yue Hu