saher ahmed

Menu

Close

Building a Scalable Design System

Building a Scalable Design System

Building a Scalable Design System

Building a Scalable Design System

Building a Scalable Design System

CLIENT

Great Western Railway (GWR)

BACKGROUND

GWR’s existing design library was outdated and not built for scale, causing slow feature shipping and inconsistent UX.

Challenge

They needed a single, scalable system with tokenisation at its core to standardise design, reduce duplication and unlock faster shipping.

Impact

  • ↑ 60% faster component reuse

  • ↓ 35% design debt

  • 3.5 hrs saved in developer handoff

Team:

Team included 2 strategists, 1 researcher and 2 junior designers

My role

Atomic design system
Design tokenisation
Component consolidation
Stakeholder alignment

Timeline

3 months (December 2024 - March 2025)

CLIENT

Great Western Railway (GWR)

BACKGROUND

GWR’s existing design library was outdated and not built for scale, causing slow feature shipping and inconsistent UX.

Challenge

They needed a single, scalable system with tokenisation at its core to standardise design, reduce duplication and unlock faster shipping.

Impact

  • ↑ 60% faster component reuse

  • ↓ 35% design debt

  • 3.5 hrs saved in developer handoff

Team:

Team included 2 strategists, 1 researcher and 2 junior designers

My role

Atomic design system
Design tokenisation
Component consolidation
Stakeholder alignment

Timeline

3 months (December 2024 - March 2025)

CLIENT

Great Western Railway (GWR)

BACKGROUND

GWR’s existing design library was outdated and not built for scale, causing slow feature shipping and inconsistent UX.

Challenge

They needed a single, scalable system with tokenisation at its core to standardise design, reduce duplication and unlock faster shipping.

Impact

  • ↑ 60% faster component reuse

  • ↓ 35% design debt

  • 3.5 hrs saved in developer handoff

Team:

Team included 2 strategists, 1 researcher and 2 junior designers

My role

Atomic design system
Design tokenisation
Component consolidation
Stakeholder alignment

Timeline

3 months (December 2024 - March 2025)
An updated collage of GWR design system

A look at GWR’s new atomic design system, fully consolidated and streamlined.

TL;DR - Long Story Short

Over three months, I had the pleasure of leading the effort to clean up Great Western Railway (GWR)'s digital library by building a powerful, consistent Atomic Design System.

The main hurdle was that their products lacked a shared vision for "consistency." I collaborated closely with stakeholders to define that vision and then built the core component library, guiding junior designers along the way.

The result is a simple, unified system that acts as a single source of truth, meaning the whole GWR team can now design and build new features much faster and with zero friction.

BACKGROUND

Understanding the gaps before we built solutions

A snapshot of the design inconsistencies within GWR website that I found.

When I first reviewed GWR’s digital presence, it was clear that their design system was more of an ad-hoc collection of elements than a cohesive framework.

Colour library for GWR

A snapshot of every colour I extracted from GWR’s web and app interfaces.

USER RESEARCH

Auditing the existing library to understand the problem

I began by analysing GWR’s existing web and mobile interfaces by conducting a UX audit of their component library and website. To benchmark, I explored other relevant design systems of Trainline, TFL and LNER to understand scalable structures in the industry.

INITIAL HYPOTHESIS

Can a new design system improve consistency?

The stakeholder initially requested that we build a design system from scratch. While this was the starting requirement, we felt it might not be the most effective approach, so our initial hypothesis focused on exploring what would actually be ideal.

THE STRATEGIC CHALLENGE

How to standardiSe without starting over

We selected Brad Frost’s atomic design methodology as the backbone by breaking the interface into atoms, molecules, organisms and templates. This approach helped us to leverage existing GWR components, reduce redundancy and provide a structured way to document and maintain the system.

Atomic design methodology

Atomic Design, laid out in Frost’s book, proposes a system for managing complexity.

UPDATED HYPOTHESIS

Optimising, rebuilding existing systems instead

I chose and optimised colours by structuring the brand palette into Signature, Complementary, Warm, and Functional categories, then strategically applying the Signature (Corporate Green/White) and Functional (Red) colours in the UI to ensure brand consistency and guide user focus to key actions.

Design Approach

From atoms to templates: building a scalable system

I mapped all components, colours, and interactions into an atomic hierarchy. Following a library refresh, I reconstructed the ticket selection widget by revamping individual elements.

Atoms were standardised, Molecules combined into reusable patterns, and Organisms formed full-page sections. Templates showed real use cases, and workshops with designers and developers ensured the system was practical and well-documented.

A figma sneak peek of the updated library

A quick peek inside the Figma file powering GWR’s design system.

Results & Metrics

Measurable impact: faster workflows, fewer inconsistencies, big savings

The system delivered measurable impact:

  • Design-to-development handoff sped up by ~60%

  • Visual inconsistencies dropped ~45%

  • Internal audits showed a 25% decrease in duplicated work.

Developers reported that UI maintenance became simpler and the GWR digital product felt coherent and trustworthy to users. The system also laid the foundation for long-term scalability, making it easier to roll out new features or flows without breaking design consistency.

The shipping document

A brief guide to maintain and evolve the component system.

A brief guide to maintain and evolve the component system.

We moved the booking widget front and centre! This post-UX-audit design prioritises fast, intuitive ticket searching over promotional content.

We moved the booking widget front and centre! This post-UX-audit design prioritises fast, intuitive ticket searching over promotional content.

Reflection

Designing for scalability is important

The key takeaway is that a design system scales when teams feel ownership and confidence to shape it. Future-proofing isn’t about freezing components; it’s about clear governance, collaboration and rituals that keep the system alive. This experience showed me how to redesign visual systems that remain adaptable, consistent and resilient as products evolve.

Create a free website with Framer, the website builder loved by startups, designers and agencies.