Paul Wilshaw · Designed for Humans

UKFast / ANS · 2021–2023 · Head of UX Design

One shared design language

Two brands. More than 100 products. No shared design language.

UKFast / ANS · Head of UX Design

The challenge

When UKFast and ANS merged, two brands came together with more than 100 products. Teams worked on different technology stacks and kept designing and building the same interface pieces from scratch, each one slightly different.

The cost wasn't only inconsistency. Duplicated components meant duplicated effort, decisions were made product by product, and ideas often went into build before anyone had tested them with users.

It was a merger of two cultures, too. UKFast already had a design system and ways of working I'd built there. ANS had neither, and no dedicated UX function. Bringing the teams together meant teaching as much as building.

What I did

As Head of UX Design, I led the UX strategy for the merged business and the design system that tied it together.

I built the system collaboratively, with the teams who would use it: 1,000+ components, 900+ custom icons and 300+ illustrations. With teams on different stacks, a shared design language gave everyone the same parts and the same rules to build from, whatever their codebase.

Training and education were paramount. I ran workshops, paired with designers and developers on real work, and wrote the teaching into the design system itself: every part came with how to use it, why, and the do's and don'ts, down to how to draw an icon on the pixel grid.

During the merger, UKFast's and ANS's customer portals were combined into one new portal, Glass. We called the work Portal to Glass.

Alongside it, I made user research a standard step, so teams tested ideas before building them. And I created a roadmap framework linked to Jira and Azure DevOps, so product, engineering, sales and marketing could all see what was being built, why and when.

The icon pages of the design system in Figma: icon sizes and stroke weights, do's and don'ts, how to draw an icon on the pixel grid, and sets of directional, public sector, people, symbol and object icons
Icons: sizes, strokes, do's and don'ts, how to draw them on the pixel grid, and the sets themselves.
Icon size guidance: always design at the smallest size, 16 by 16 pixels, and fill as much of the bounding box as possible so icons line up in toolbars. A row of icons, a star, database, search, light bulb, box, chat, chip and pound sign, sits on a 16 pixel baseline
Close up: design every icon at 16 by 16 pixels and fill the box, so a row of icons lines up.
Icon colour pairing: background and icon colour pairs with hex values and token names for default, cloud and infrastructure, positive and warning, in dark and light mode, such as Glass600 with Glass200 and Paper150 with Paper700, each with an accessibility scale against the background
Close up: icon and background colour pairs for each context, in dark and light mode, checked for contrast.
Button components in Figma: primary, secondary, action, next and back buttons, each with every state, usage do's and don'ts, spacing, and the colours for dark and light mode
Buttons: every state, when to use each one, spacing, and colours for dark and light mode.

What changed

The system was adopted across the business and now supports more than 100 products. Teams stopped duplicating interface work, products became more consistent, and research reduced the risk of building the wrong thing.

Product and website screens built with the design system: eCloud home pages, screens from Portal to Glass (the two companies' customer portals merged into one) in light and dark, welcome screens, the ANS identity sign-in and long desktop website pages
Built from the same parts: Portal to Glass, which merged the two companies' customer portals into one, alongside eCloud, sign-in and the website.

Highlights

  • Built a design system adopted across the business: 1,000+ components, 900+ custom icons and 300+ illustrations
  • Made user research a standard step, so teams tested ideas before building them
  • Created a roadmap framework linked to Jira and Azure DevOps, so every department could see what was being built and why
  • Introduced a pricing strategy that stopped the business competing on price alone