Case Study
Design System Revamp:
Scaling Consistency
Across 56 Markets

Role
Product Designer
Domain
E-commerce
Product
High-traffic e-commerce platform for a global FMCG brand with 45M+ annual users
Approach & Key Decisions
We started with the redesign of three pages for the US market. Once the new layouts were established, I helped identify reusable patterns and build a design system around the actual product UI rather than adapting the outdated library.
Two decisions shaped the system: using Atomic Design principles to organise components, and creating shared components with design tokens to support both brand themes. This approach established a common foundation that could scale as more pages and markets adopted the new design.
Building the System
01 Foundations & Component Library
I audited the existing UI Kit and built a new component library structured around Atomic Design principles. The system covered core UI elements and more complex patterns, with consistent naming, variants, and interaction states.
I also established design tokens for key visual properties, including colour, typography, spacing, radius, and shadows, using Figma Variables to manage shared styles.

Button Component - Design Tokens Mapping
02 Two Brands, One System
I used shared components and design tokens to support both brands. Instead of maintaining separate component libraries, we used the same underlying UI structure with brand-specific colour values.
Switching the theme changed the visual appearance while preserving the component structure. The development team implemented the same principle in code, keeping the design and implementation aligned.
Theme Switching in the User Flow
03 Documentation for Multiple Teams
I documented component usage, variants, and interaction states to support consistent implementation. The guidelines covered not only designers and developers, but also content teams responsible for adapting page content and imagery to local markets.

Component Documentation & Specifications
This gave teams a shared reference for building and maintaining pages across the platform.
Outcomes
The redesign replaced fragmented UI patterns with a shared, reusable system.
Before
Outdated visual design and inconsistent UI patterns.
Duplicated elements across pages.
No reliable shared foundation for teams across markets.


Old UI Kit
After
A standardised component library with shared design tokens.
Two brand themes supported by the same component structure.
Reusable components introduced across redesigned and legacy pages.
Clearer guidelines for design, development, and content teams.
Input behaviour demo: showcasing dynamic data entry and state changes in real-time
To improve readability across markets, I also introduced adaptive typography using Figma Variables. While most markets shared the same font, Arabic and Asian markets required language-specific typefaces to better support their writing systems.

Adaptive typography with Figma Variables for improved readability across different writing systems
The design system was implemented across 56 markets, establishing a shared foundation for two brand themes and a library of 206 reusable components.
It supported the rollout of new page designs and the gradual replacement of legacy UI components, helping maintain a more consistent experience as the platform evolved.

Reusable Pages & Components Across Markets
Key Learnings
Build from real product needs. Starting with redesigned pages helped us identify reusable patterns based on actual product requirements.
Design for scalability from the start. Shared components and design tokens made it possible to support two brand identities without maintaining separate UI libraries.
Consistency requires shared conventions. Clear naming, documentation, and collaboration between design and development were essential to successful adoption.


