Bringing order to a fragmented multi-market product
When I joined the project, no one could say which design was the real one. The design files and the live apps had drifted into two different products, and there was no engineering capacity to fix either. So I rebuilt the system from what was actually shipping – across 12 markets and two brands.
Selected project details and visuals have been anonymised for confidentiality.
Role
Product designer, design system owner
Scope
Design system architecture, component library, UI harmonization, documentation
Year
2026
Platform
iOS · Android
Problem
•
Multiple Figma files and an outdated component library
•
Design files and live implementations didn’t always match
•
No clear source of truth across markets and teams
Approach
•
Reconstructed what was actually in use
•
Consolidated foundations, tokens and components
•
Built a shared system that could support multiple brands
Outcome
•
One shared foundation for product UI
•
Reusable multi-brand tokens and components
•
Clearer design / development alignment

Context
One product, many realities
The product combines a loyalty app with parenting tools and content. Users can scan purchases to earn points, redeem rewards, track their child’s growth and access parenting guidance.
The experience spans around a dozen markets and two distinct brand themes, with local differences in features and content.

One product across markets, brands, design files and live apps
The problem
No single source of truth
Over time, the product had become fragmented across multiple Figma files, an outdated component library and different live implementations.

Questions that had no single answer
Constraint & approach
A full redesign wasn’t an option
Engineering capacity was limited, and changing the product architecture or underlying flows would have meant rebuilding too much.
So instead of redesigning the product, I focused on creating a shared visual system that could improve what was already there – without changing how it worked.
Foundations & tokens
Reconstructing the system
With no reliable master file, I started by reconstructing the system from the product itself. I gathered references from live implementations and existing design files, compared recurring patterns, and rebuilt screens component by component to understand what was actually being used.
From there, I mapped the existing values one by one. Some could be consolidated into shared tokens, others needed replacing, and a few required an explicit product decision.

Every legacy value was reviewed, mapped or replaced
Multi-brand architecture
One foundation, different brand expressions
The same product had to support two distinct visual identities.
I separated brand-specific values from shared semantic roles, so the same components could switch between themes without being rebuilt manually.

Brand-specific values mapped to shared roles
How it lives in Figma
The same structure was implemented in Figma using separate brand collections and shared semantic tokens, with brand switching handled through variable modes.

Documentation
Components & documentation
Once the foundations were stable, I rebuilt recurring UI into reusable components with defined states, naming and usage rules.

Patterns documented for consistent reuse
Harmonisation
Improving the product without redesigning it
I then applied the system back to existing screens. The structure and functionality stayed the same, while typography, color and UI treatments were brought into a consistent visual language.
The result was a shared system that replaced fragmented references with one working source of truth
Designers can build with reusable patterns, developers now implement against the same token structure, and the product can support multiple brand themes without maintaining separate versions of the same UI.


