← Back to selected work

Vodafone · Design systems · 2023—2024

Master Design
System Kit

A scalable token architecture and component foundation supporting more than 40 product teams across web and mobile.

Industry
Telecommunications
My role
Senior Product Designer
Team
Design system squad
Product teams
Timeline
2023 — 2024

Overview

One shared foundation for a growing product ecosystem.

Vodafone’s digital products were evolving quickly across platforms, markets, and product teams. The work needed a common design language that could make delivery faster without flattening the character of each experience.

The Master Design System Kit brought foundations, tokens, components, documentation, and contribution workflows into one dependable product for designers and engineers.

01 · The problem

Consistency was being rebuilt project by project.

01

Fragmented foundations

Teams used similar patterns with different spacing, colour, and interaction decisions.

02

Repeated effort

Designers and engineers recreated familiar product patterns instead of reusing them.

03

Uneven quality

Accessibility and responsive behaviour varied depending on the project and delivery pressure.

Foundation audit40+ product teams
Mapping shared patterns revealed where one source of truth could remove the most repeated work.

02 · Solution

A system designed as a product, not a static library.

The system connected semantic tokens to reusable components, then wrapped both in clear usage guidance. This made decisions visible and gave teams a predictable path from design to production.

Contribution and release workflows made the library sustainable: product teams could propose improvements while the core squad protected quality and coherence.

03 · The system

From foundations to production-ready patterns.

04 · Results

A shared language with measurable reach.

40+Product teams supported
2Core platforms aligned
1Shared source of truth

05 · Learnings

“A design system succeeds when teams trust the decisions behind it—not only the components inside it.”

Clear ownership, contribution paths, and documentation proved as important as the visual foundations themselves.