Source design system

Where Source design system is used:

UK ๐Ÿ‡ฌ๐Ÿ‡ง, Ireland ๐Ÿ‡ฎ๐Ÿ‡ช, Germany ๐Ÿ‡ฉ๐Ÿ‡ช, Czech Republic ๐Ÿ‡จ๐Ÿ‡ฟ, Greece ๐Ÿ‡ฌ๐Ÿ‡ท, Turkey ๐Ÿ‡น๐Ÿ‡ท, Spain ๐Ÿ‡ช๐Ÿ‡ธ, Italy ๐Ÿ‡ฎ๐Ÿ‡น, Albania ๐Ÿ‡ฆ๐Ÿ‡ฑ, Portugal ๐Ÿ‡ต๐Ÿ‡น, Hungary ๐Ÿ‡ญ๐Ÿ‡บ, Romania ๐Ÿ‡ท๐Ÿ‡ด, South Africa ๐Ÿ‡ฟ๐Ÿ‡ฆ, Egypt ๐Ÿ‡ช๐Ÿ‡ฌ, Ghana ๐Ÿ‡ฌ๐Ÿ‡ญ, Mozambique ๐Ÿ‡ฒ๐Ÿ‡ฟ, Tanzania ๐Ÿ‡น๐Ÿ‡ฟ

Goal โžก Made to scale

Having a huge presence in EMEA with many different languages poses a challenge for a design system.

And Source hasnโ€™t always been this unified. It used to be very fragmented and each market we operate in had its design system creating inconsistencies experiences across the markets.

At one point in the past, Vodafone Spain called it ReSource, Vodafone Germany called it Brix, and Vodafone Business also has its own name, thereโ€™s even a design system for internal tooling. And we ended up with around 10 โ€˜design systemsโ€™.โ€จโ€จSo the big challenge here is ensure the design system caters to all markets and languages.

Madness of multiple design systems in the past

Source Design system - as of 2024

Accessibility at the heart of the process

As an accessibility lead at Vodafone, I also created comprehensive resources to ensure that accessibility touches on every point of the design, from component-level to page-level accessibility. When I say accessibility, this does not mean only revolving around contrast ratio and colour but weโ€™re complying with the accessibility to the entirety of WCAG 2.2

Accessibility embedded in every component of the design

Accessibility guidance that explains in a wider scope such as user flow

Want to know more of the design system process and challenges? get in touch