Improving UI By Implementing Cross-Brand Design System

Design system foundations

COMPANY

William Hill

ROLE

Product Designer

Project description

The Problem

Inconsistent design across products created costly design debt and negatively impacted the customer experience at William Hill. Additionally, designers and developers struggled to collaborate effectively, hindering efficiency.

My Role

I partnered with the Senior UI Designer and Head of Global Product to lay the foundations for Helix—William Hill's first-ever design system. This involved building the core UI libraries and securing buy-in from key senior stakeholders.

Process

Research

To uncover the current processes and pain points across Product teams, I conducted internal research through workshops and surveys involving colleagues from branding, research, engineering, and product design.

Our findings highlighted a pervasive lack of clear documentation processes, leading to inefficiencies across teams. Key insights included:

  • Inconsistent File Practices: Designers provided varied answers on essential pages for Figma files, resulting in inconsistent workflows.

  • Limited Resources: Designers lacked UI kits, leading to designs relying heavily on screenshots, which frustrated developers.

  • Scattered Files: Teams struggled to locate files, which were dispersed across Figma, Confluence, and OneDrive.

To assess the effectiveness of existing documentation specifically for designers, I conducted a survey among UX and UI teams, revealing:

  • 80% of respondents rated current documentation as poor.

  • 100% relied on screenshots in their designs.

  • 100% reported abandoning searches for components.

  • 100% expressed enthusiasm about using a design system.

Reframing the Problem

Helix will serve as a comprehensive design system, unifying products and brands with reusable components and patterns that ensure consistency and enable seamless collaboration at scale.

Solution

Step 1: Establish a clear framework to effectively plan and divide project tasks.

Step 2: Develop detailed UI libraries and patterns alongside robust documentation for teams to follow.

Step 3: Align ways of working to unify teams across the 888 William Hill group.

Step 1: Define Helix’s Structure

To build a cohesive and effective design system, I established a clear structure for Helix as a single source of truth. Designed in Figma, it incorporates design tokens, a UI kit, and a component library, providing the product team with the confidence to develop consistent and scalable UI solutions.

After researching industry-leading design systems like Atlassian, Carbon, Material, and Shopify’s Polaris, I identified the atomic design approach as the optimal framework. This method ensures our product team adopts a unified mindset, viewing the UI as a collection of interrelated components that form a seamless and cohesive whole.


Atomic design approach.


Step 2: Build UI Libraries & Documentation

2.1 UI Library

To date, I’ve developed component libraries for two of William Hill's four product verticals: Gaming and Retail. With autonomy to structure the project, I began by conducting a comprehensive audit of the core customer journeys within Gaming. This process involved recording components on each page and categorizing them at atomic and molecular levels, such as accordions, modals, and other UI elements. Using this detailed inventory, I systematically created and refined components.

This approach was aligned with initial groundwork laid by the Senior UI Designer, who had begun creating atomic-level components like colors, typography, and icons. To ensure seamless progress tracking and collaboration, I established an epic in Jira, allowing stakeholders to monitor updates efficiently.


Game tile component.


2.2 Documentation

Effective documentation is critical to ensuring consistent design practices and clear communication across teams. I created a series of Figma files that serve as resources for both designers and other stakeholders, organised into three key categories:

Best Practices

Page and Component Documentation: Detailed breakdowns on using templates, including anatomy overviews, dos and don’ts, and clear explanations.

Usability Testing: A guide to leveraging usertesting.com, complete with audience flowcharts.

Accessibility: Comprehensive guidance on designing inclusively and ensuring accessibility.


Guide to accessibility.


Templates

Ready-to-use Figma templates for projects, such as component design, presentations, customer journey mapping, SUS scoring, and page layouts.


Customer journey map template.


Getting Started

A set of resources to onboard new designers and inform other departments about the design team’s processes. Key documents include:

  • Design Team Org Structure: Overview of roles within the team.

  • Brand Guidelines: A comprehensive look at William Hill’s visual identity, tone of voice, and brand values.

  • Design Processes and Methodologies: Documentation of research, ideation, and prototyping workflows.

  • Personas: Profiles detailing target users, their needs, goals, and pain points.


Screenshot of personas from document detailing how and why personas are used.


This layered documentation strategy supports consistent adoption of the Helix design system while fostering collaboration and alignment across the organisation.


Step 3: Integrating Our Ways of Working as a Global Team

Education and Training: Sharing Knowledge

Workshops were essential in promoting Helix adoption, educating designers and developers on its use, benefits, and limitations. This enabled teams to improve design efficiency and usability across the organization.

Collaboration and Feedback: One Team, One Dream

Collaboration and open feedback between designers and developers were key to ensuring Helix met team needs, resulting in a more efficient design process and stronger alignment.

Governance and Ownership: Establishing the Flight Plan

Helix’s sustainability relied on clear governance, defined roles, and robust documentation. This structure maintained consistency across teams and ensured ongoing relevance in design and development.

Advocating for Helix

As a large-scale, long-term project, Helix required widespread support from stakeholders across the product organisation. I played an active role in securing buy-in by presenting Helix to key stakeholders, outlining its strategic importance and potential impact on efficiency and user experience.Through these initiatives, Helix has been successfully integrated into William Hill's product workflows, positioning it as a vital tool for unifying the design and development processes globally.


Extracts of a presentation I delivered to senior stakeholders advocating for Helix.

Results

As the Helix project was an ongoing initiative at the time of my departure from William Hill, formal results were not finalized. However, throughout the project, I gained valuable insights that will inform my future work on design systems. Below are the key learnings from my experience.

Collaboration

Working closely with designers, developers, and stakeholders taught me the importance of effective communication, active listening, and finding common ground to successfully create the Helix design system.

Documentation

This project highlighted the value of creating concise, user-friendly documentation. It refined my writing skills and taught me to consider how others would use and benefit from the system.