Clarks.

Laying the foundations of Clarks' first design system and untangling a clunky US wholesale portal, as design lead across two scrum teams.

RoleLead Digital Product Designer, contract ClientClarks Years2019 to 2020 ScopeDesign lead across two scrum teams and the UK and US markets. Design system creation, a heuristic review of the B2B portal, personas and service blueprints, remote unmoderated testing, and the 2020 digital roadmap
A pair of Clarks shoes with the Clarks logo over the top.
7 months
On site in Street and remote with the US
2
Scrum teams led across the UK sites and the US B2B portal
1 sprint
To design and build the new forms, pairing directly with the developers
UK + US
Teams and stakeholders across both markets

Page summary

  • Clarks had a style guide but no design system, so teams were rebuilding the same components time and time again. And the US wholesale portal, Clarks' own system, was old and clunky, so the US team asked for a UX review with a very open brief.
  • I led the creation of the design system, defined with brand designers, product designers and developers together. On the B2B side I took the work from a heuristic review through to personas and service blueprints.
  • The system was adopted and incorporated into Storybook to match the dev components, and the new forms went from nothing to designed, built and shipped in a single sprint.

The problem.

Clarks runs its UK sites, the main retail site, Originals and Outlet, plus a US B2B portal, built and maintained by separate scrum teams. There was a decent style guide but no design system, so every team was interpreting the brand for themselves and rebuilding the same components time and time again.

The B2B side was a different problem. The US business is predominantly wholesale, selling to big shopping chains and mum and pop stores through a portal Clarks owned. It worked but it was old and clunky, and the US team asked for a UX review with a very open brief. Part of why the brief was so open only became clear later. Few people in the UK really understood how the US business worked.

A workshop in progress, brand designers, product designers and developers gathered around printouts of the site covered in sticky notes.

What we did.

The design system

Getting a design system adopted is a people problem before a design one, so I started with workshops bringing brand designers, product designers and developers together to define what good looked like for Clarks and how the wider business would use it. The tooling was a deliberate choice. Figma was only just emerging and Sketch was still the standard, but more importantly Sketch gave us the control the vision needed, a system that non designers could use to make basic changes and designs themselves. Scaling and enabling, not gatekeeping.

The system shipped as shared Sketch libraries, incorporated into Storybook so design and development stayed matched, working omnichannel across the UK sites. It was basic but it was the foundations to build on. Forms were where we proved it, pairing directly with the developers, co-creating and building the new form components in a single sprint.

Form field components in the design system, showing the range of states and scenarios each field is defined for.
Four phones showing steps through a checkout journey.
A set of service email screens redesigned and rewritten as part of the work.

Alongside

Designs from wireframe to high fidelity, prototyping in sprint with the developers, and remote unmoderated user testing. And the 2020 digital roadmap, which the whole digital strategy hung off, crafted with the director responsible for digital technology and innovation.

Slides from the Clarks digital strategy deck, covering team collaboration, agile processes and scrum ceremonies.

The B2B portal

I ran a heuristic review of the portal first, highlighting the friction points and identifying the flows worth improving. But fixing flows for users nobody could describe felt backwards, so we built the picture. Remote workshops and stakeholder interviews with the US team, plus the analytics, produced four key personas for the groups actually using the wholesale platform, worked up and shared across the business. From there we ran empathy mapping sessions, identified the four highest value journeys and mapped each one in detail as a service design blueprint.

Pages from the documentation, a central reference of the US marketplaces findings for all stakeholders to view and help co-create.

What happened.

The design system was adopted by the design team and lives in Storybook matched to the dev components. The forms shipped from that single sprint. And the improved B2B flows were built, working from the blueprints, before the contract ended.

Then COVID. The majority of Clarks' UK revenue came from bricks and mortar stores rather than digital, and the business was already running on a rolling three month budget with a lot of contractors filling gaps. When the stores shut the contractors went, me included.

“He showed leadership in helping us to develop a design system, mentor colleagues and handle challenging stakeholders.”

My manager at Clarks, written recommendation, April 2020
The four final Clarks B2B personas, worked up and shared across the business.
A remote workshop mapping an end to end journey with the US team.
Pages of the B2B checkout journey with the changes we advised to improve the experience for the sales reps.

Learnings.

  • The heuristic review found the friction but the personas and blueprints did the real work, getting the UK and US to a shared understanding of a wholesale business one side barely knew existed.
  • The workshops mattered more than the Sketch file. Brand designers, product designers and developers defining the system together meant adoption wasn't a separate battle afterwards.
  • Building the system so non designers could use it turned out to be the point. In a business run on a rolling three month budget and contractors, the work has to survive the people leaving.