Token Driven Design system | Case study

OVERVIEW

The product team was working with multiple inconsistent components, styles, and UI libraries. Each designer and developer used their own variations of colors, spacing, and interactions, which led to visual inconsistencies, errors, longer delivery times, and poor scalability. There was no single source of truth the interface’s appearance depended on the individual, not on shared rules.

A black and white image of a handrawn logo

ROLE

UX/UI Designer

Additional issues included


  • Discrepancies between web and mobile.


  • Overlapping React component libraries.


  • Difficulty maintaining dark mode and brand variants.


  • A high number of CSS overrides creating visual technical debt.

Solution

I created a modular design system built on design tokens, which became the foundation of the entire UI architecture. Tokens defined colors, typography, spacing, radiuses, shadows, and motion enabling centralized style management and consistent propagation of changes.

The system was structured into four layers:


  • Core Tokens – abstract values (e.g., color-primary-500, space-xl).


  • Semantic Tokens – contextual values (e.g., button-bg-primary, text-error).


  • Components – a standardized UI library built using semantic tokens.


  • Documentation – interactive guidelines for designers and developers.

How I Measured Results

To accurately evaluate the impact of the implementation, I conducted a set of analyses:

  • Audit of 200+ screens

  • Using tools such as Figma Inspector and style analysis plugins, I mapped all duplicated and conflicting styles.

  • Over several sprints, we tracked design and development tasks enabling a comparison of real delivery times before and after system implementation.

  • Repository commit analysis

  • I examined the number of style-related conflicts, overrides, and modification points.

  • We verified UI alignment across multiple applications, including light/dark mode and B2B brand variants.

  • Interviews with designers and developers confirmed that the system significantly improved collaboration and clarity.

Image of a Laptop on top of an eletronic device
Smooth Scroll
This will hide itself!

Token Driven Design system | Case study

OVERVIEW

The product team was working with multiple inconsistent components, styles, and UI libraries. Each designer and developer used their own variations of colors, spacing, and interactions, which led to visual inconsistencies, errors, longer delivery times, and poor scalability. There was no single source of truth the interface’s appearance depended on the individual, not on shared rules.

A black and white image of a handrawn logo

ROLE

UX/UI Designer

Additional issues included


  • Discrepancies between web and mobile.


  • Overlapping React component libraries.


  • Difficulty maintaining dark mode and brand variants.


  • A high number of CSS overrides creating visual technical debt.

Solution

I created a modular design system built on design tokens, which became the foundation of the entire UI architecture. Tokens defined colors, typography, spacing, radiuses, shadows, and motion enabling centralized style management and consistent propagation of changes.

The system was structured into four layers:


  • Core Tokens – abstract values (e.g., color-primary-500, space-xl).


  • Semantic Tokens – contextual values (e.g., button-bg-primary, text-error).


  • Components – a standardized UI library built using semantic tokens.


  • Documentation – interactive guidelines for designers and developers.

How I Measured Results

To accurately evaluate the impact of the implementation, I conducted a set of analyses:

  • Audit of 200+ screens

  • Using tools such as Figma Inspector and style analysis plugins, I mapped all duplicated and conflicting styles.

  • Over several sprints, we tracked design and development tasks enabling a comparison of real delivery times before and after system implementation.

  • Repository commit analysis

  • I examined the number of style-related conflicts, overrides, and modification points.

  • We verified UI alignment across multiple applications, including light/dark mode and B2B brand variants.

  • Interviews with designers and developers confirmed that the system significantly improved collaboration and clarity.

Image of a Laptop on top of an eletronic device
Smooth Scroll
This will hide itself!

Token Driven Design system | Case study

OVERVIEW

The product team was working with multiple inconsistent components, styles, and UI libraries. Each designer and developer used their own variations of colors, spacing, and interactions, which led to visual inconsistencies, errors, longer delivery times, and poor scalability. There was no single source of truth the interface’s appearance depended on the individual, not on shared rules.

A black and white image of a handrawn logo

ROLE

UX/UI Designer

Additional issues included


  • Discrepancies between web and mobile.


  • Overlapping React component libraries.


  • Difficulty maintaining dark mode and brand variants.


  • A high number of CSS overrides creating visual technical debt.

Solution

I created a modular design system built on design tokens, which became the foundation of the entire UI architecture. Tokens defined colors, typography, spacing, radiuses, shadows, and motion enabling centralized style management and consistent propagation of changes.

The system was structured into four layers:


  • Core Tokens – abstract values (e.g., color-primary-500, space-xl).


  • Semantic Tokens – contextual values (e.g., button-bg-primary, text-error).


  • Components – a standardized UI library built using semantic tokens.


  • Documentation – interactive guidelines for designers and developers.

How I Measured Results

To accurately evaluate the impact of the implementation, I conducted a set of analyses:

  • Audit of 200+ screens

  • Using tools such as Figma Inspector and style analysis plugins, I mapped all duplicated and conflicting styles.

  • Over several sprints, we tracked design and development tasks enabling a comparison of real delivery times before and after system implementation.

  • Repository commit analysis

  • I examined the number of style-related conflicts, overrides, and modification points.

  • We verified UI alignment across multiple applications, including light/dark mode and B2B brand variants.

  • Interviews with designers and developers confirmed that the system significantly improved collaboration and clarity.

Image of a Laptop on top of an eletronic device
Smooth Scroll
This will hide itself!