One System, 150 Brands: Amdocs Case Study

Transforming Amdocs’ design operations by migrating to Figma and building a scalable system to deliver 150+ brands efficiently.

One System, 150 Brands: Amdocs Case Study

Transforming Amdocs’ design operations by migrating to Figma and building a scalable system to deliver 150+ brands efficiently.

One System, 150 Brands: Amdocs Case Study

Transforming Amdocs’ design operations by migrating to Figma and building a scalable system to deliver 150+ brands efficiently.

Design system components
Design system components
Design system components
Project Overview
This project was delivered with Kido team, including system designers and engineers - a complex but genuinely fun challenge, built through close collaboration and smart experimentation.
Company:

Kido - strategic design operations partner

Client:

Amdocs - global communications & media software & services provider

Project Type:

Design system migration and scaling

Role:

Project Owner, System Designer

Timeline:

Q2-Q3 2023

Skills:
  • Design System

  • Variables

  • Governance

  • Education & Training

  • Design Ops

Project Overview
This project was delivered with Kido team, including system designers and engineers - a complex but genuinely fun challenge, built through close collaboration and smart experimentation.
Company:

Kido - strategic design operations partner

Client:

Amdocs - global communications & media software & services provider

Project Type:

Design system migration and scaling

Role:

Project Owner, System Designer

Timeline:

Q2-Q3 2023

Skills:
  • Design System

  • Variables

  • Governance

  • Education & Training

  • Design Ops

Project Overview
This project was delivered with Kido team, including system designers and engineers - a complex but genuinely fun challenge, built through close collaboration and smart experimentation.
Company:

Kido - strategic design operations partner

Client:

Amdocs - global communications & media software & services provider

Project Type:

Design system migration and scaling

Role:

Project Owner, System Designer

Timeline:

Q2-Q3 2023

Skills:
  • Design System

  • Variables

  • Governance

  • Education & Training

  • Design Ops

The Challenge

Amdocs’ design infrastructure relied on multiple disconnected tools - Axure for UX and prototyping, InVision for documentation, Sketch and InVision DSM for design - which slowed workflows and made collaboration difficult. With over 70 designers spread across Israel and India, finding a single source of truth was a constant challenge, and significant back-and-forth was needed to ship new designs. On top of that, the team had to support around 150 new brands each year, including light and dark mode, adding even more complexity to already fragmented tools and processes.

The Challenge

Amdocs’ design infrastructure relied on multiple disconnected tools - Axure for UX and prototyping, InVision for documentation, Sketch and InVision DSM for design - which slowed workflows and made collaboration difficult. With over 70 designers spread across Israel and India, finding a single source of truth was a constant challenge, and significant back-and-forth was needed to ship new designs. On top of that, the team had to support around 150 new brands each year, including light and dark mode, adding even more complexity to already fragmented tools and processes.

The Challenge

Amdocs’ design infrastructure relied on multiple disconnected tools - Axure for UX and prototyping, InVision for documentation, Sketch and InVision DSM for design - which slowed workflows and made collaboration difficult. With over 70 designers spread across Israel and India, finding a single source of truth was a constant challenge, and significant back-and-forth was needed to ship new designs. On top of that, the team had to support around 150 new brands each year, including light and dark mode, adding even more complexity to already fragmented tools and processes.

Discovery
We began with a thorough discovery phase - conducting team interviews, reviewing existing files, and mapping current workflows to uncover key pain points and inefficiencies. From there, a list of challenges was distilled to the following:
  • Consolidate all design tools and transfer them to Figma

  • Create one library of base components for all brands

  • Implement a painless solution for theming and multi-brand design components

  • Create cross-team Figma infrastructure

  • Streamline documentation creation and maintenance processes

  • Train and support design teams in using Figma in day to day activities

  • Tight deadline - 3 months to deliver the end result

Discovery
We began with a thorough discovery phase - conducting team interviews, reviewing existing files, and mapping current workflows to uncover key pain points and inefficiencies. From there, a list of challenges was distilled to the following:
  • Consolidate all design tools and transfer them to Figma

  • Create one library of base components for all brands

  • Implement a painless solution for theming and multi-brand design components

  • Create cross-team Figma infrastructure

  • Streamline documentation creation and maintenance processes

  • Train and support design teams in using Figma in day to day activities

  • Tight deadline - 3 months to deliver the end result

Discovery
We began with a thorough discovery phase - conducting team interviews, reviewing existing files, and mapping current workflows to uncover key pain points and inefficiencies. From there, a list of challenges was distilled to the following:
  • Consolidate all design tools and transfer them to Figma

  • Create one library of base components for all brands

  • Implement a painless solution for theming and multi-brand design components

  • Create cross-team Figma infrastructure

  • Streamline documentation creation and maintenance processes

  • Train and support design teams in using Figma in day to day activities

  • Tight deadline - 3 months to deliver the end result

The Process

Once we moved into execution, the priority was to build components that were both scalable and adaptable to multiple use cases. The slot approach became essential - it allowed teams to customize layouts and flows without breaking the system’s core structure.

The Process

Once we moved into execution, the priority was to build components that were both scalable and adaptable to multiple use cases. The slot approach became essential - it allowed teams to customize layouts and flows without breaking the system’s core structure.

The Process

Once we moved into execution, the priority was to build components that were both scalable and adaptable to multiple use cases. The slot approach became essential - it allowed teams to customize layouts and flows without breaking the system’s core structure.

Amdocs DS flexible compoenent with slots

Example of flexible components created with slots

Amdocs DS flexible compoenent with slots

Example of flexible components created with slots

Amdocs DS flexible compoenent with slots

Example of flexible components created with slots

The Process

As components were being migrated, we investigated ways to streamline multi-brand design. Token Studio was an option, but when Figma introduced native variables at Config 2023, we opted for the safer, built-in solution. We then dove deep into experimenting with variables to make it work efficiently for our system.

The challenge was managing variables that had different scopes: some were global and consistent across all brands, while others were brand-specific and needed to be dynamic and customizable. All of this was done while working with a brand-new, largely unexplored feature, which added an extra layer of complexity to the implementation.

The Process

As components were being migrated, we investigated ways to streamline multi-brand design. Token Studio was an option, but when Figma introduced native variables at Config 2023, we opted for the safer, built-in solution. We then dove deep into experimenting with variables to make it work efficiently for our system.

The challenge was managing variables that had different scopes: some were global and consistent across all brands, while others were brand-specific and needed to be dynamic and customizable. All of this was done while working with a brand-new, largely unexplored feature, which added an extra layer of complexity to the implementation.

The Process

As components were being migrated, we investigated ways to streamline multi-brand design. Token Studio was an option, but when Figma introduced native variables at Config 2023, we opted for the safer, built-in solution. We then dove deep into experimenting with variables to make it work efficiently for our system.

The challenge was managing variables that had different scopes: some were global and consistent across all brands, while others were brand-specific and needed to be dynamic and customizable. All of this was done while working with a brand-new, largely unexplored feature, which added an extra layer of complexity to the implementation.

Dylan Field announcing Variables feature at Config 2023

Feature announcement at Config 2023 by Figma CEO Dylan Field

Dylan Field announcing Variables feature at Config 2023

Feature announcement at Config 2023 by Figma CEO Dylan Field

Dylan Field announcing Variables feature at Config 2023

Feature announcement at Config 2023 by Figma CEO Dylan Field

The Solution

The final solution introduced a structured variable collection divided into two main groups:

  • Customizable variables — values that change per customer or brand

  • Non-customizable variables - system and component tokens that alias the customizable ones

The resulting foundation architecture looked like this:

  • Colors collection: customizable values that adapt for each customer

  • Aliased variables: system and component tokens referencing the customizable set

  • Modes management: enabling both client themes and light/dark mode control.

The Solution

The final solution introduced a structured variable collection divided into two main groups:

  • Customizable variables — values that change per customer or brand

  • Non-customizable variables - system and component tokens that alias the customizable ones

The resulting foundation architecture looked like this:

  • Colors collection: customizable values that adapt for each customer

  • Aliased variables: system and component tokens referencing the customizable set

  • Modes management: enabling both client themes and light/dark mode control.

The Solution

The final solution introduced a structured variable collection divided into two main groups:

  • Customizable variables — values that change per customer or brand

  • Non-customizable variables - system and component tokens that alias the customizable ones

The resulting foundation architecture looked like this:

  • Colors collection: customizable values that adapt for each customer

  • Aliased variables: system and component tokens referencing the customizable set

  • Modes management: enabling both client themes and light/dark mode control.

Amdocs DS final variables architecture
Amdocs DS final variables architecture
Amdocs DS final variables architecture
Training
Training played a critical role in Amdocs’ transition to Figma. We delivered 16 sessions to design teams in Israel and India, in two languages, ensuring that everyone could get up to speed with the new tool.

The program was designed to cover all essentials and support a smooth transition from previous tools.

Key elements of the training program included:

  • Introduction to Figma: An overview of Figma and its capabilities, highlighting the benefits of a unified design platform

  • Hands-On Workshops: Interactive sessions where designers could practice using Figma in real scenarios

  • Office Hours: Dedicated time to answer questions and provide additional support, ensuring teams could resolve challenges quickly

Training
Training played a critical role in Amdocs’ transition to Figma. We delivered 16 sessions to design teams in Israel and India, in two languages, ensuring that everyone could get up to speed with the new tool.

The program was designed to cover all essentials and support a smooth transition from previous tools.

Key elements of the training program included:

  • Introduction to Figma: An overview of Figma and its capabilities, highlighting the benefits of a unified design platform

  • Hands-On Workshops: Interactive sessions where designers could practice using Figma in real scenarios

  • Office Hours: Dedicated time to answer questions and provide additional support, ensuring teams could resolve challenges quickly

Training
Training played a critical role in Amdocs’ transition to Figma. We delivered 16 sessions to design teams in Israel and India, in two languages, ensuring that everyone could get up to speed with the new tool.

The program was designed to cover all essentials and support a smooth transition from previous tools.

Key elements of the training program included:

  • Introduction to Figma: An overview of Figma and its capabilities, highlighting the benefits of a unified design platform

  • Hands-On Workshops: Interactive sessions where designers could practice using Figma in real scenarios

  • Office Hours: Dedicated time to answer questions and provide additional support, ensuring teams could resolve challenges quickly

Documentation

To ensure consistency and scalability, a mini design system for documentation was designed. The documentation components were connected in prototype mode, allowing teams to explore them directly on the canvas or in presentation view - making documentation more interactive and accessible.

Using Figma variables, we also made the documentation themeable, so it could easily adapt to different brand guidelines and could be changed with the mode switch, just like the designs.

Documentation

To ensure consistency and scalability, a mini design system for documentation was designed. The documentation components were connected in prototype mode, allowing teams to explore them directly on the canvas or in presentation view - making documentation more interactive and accessible.

Using Figma variables, we also made the documentation themeable, so it could easily adapt to different brand guidelines and could be changed with the mode switch, just like the designs.

Documentation

To ensure consistency and scalability, a mini design system for documentation was designed. The documentation components were connected in prototype mode, allowing teams to explore them directly on the canvas or in presentation view - making documentation more interactive and accessible.

Using Figma variables, we also made the documentation themeable, so it could easily adapt to different brand guidelines and could be changed with the mode switch, just like the designs.

Amdocs DS documentation example

Interactive documentation for a Button component

Amdocs DS documentation example

Interactive documentation for a Button component

Amdocs DS documentation example

Interactive documentation for a Button component

Impact & Results
The new Figma-based design system transformed how Amdocs teams collaborate and scale design. By consolidating tools, introducing scalable components, and implementing a variable-driven multi-brand architecture, Amdocs design teams reduced redundancy and significantly improved efficiency.

12

Teams using library

173

Total components

26,300

Activity 1st week of the release

70

Designers across 2 countries

150

Supported brands yearly

Impact & Results
The new Figma-based design system transformed how Amdocs teams collaborate and scale design. By consolidating tools, introducing scalable components, and implementing a variable-driven multi-brand architecture, Amdocs design teams reduced redundancy and significantly improved efficiency.

12

Teams using library

173

Total components

26,300

Activity 1st week of the release

70

Designers across 2 countries

150

Supported brands yearly

Impact & Results
The new Figma-based design system transformed how Amdocs teams collaborate and scale design. By consolidating tools, introducing scalable components, and implementing a variable-driven multi-brand architecture, Amdocs design teams reduced redundancy and significantly improved efficiency.

12

Teams using library

173

Total components

26,300

Activity 1st week of the release

70

Designers across 2 countries

150

Supported brands yearly

It now takes about 5 minutes to add a new brand to the Design System

It now takes about 5 minutes to add a new brand to the Design System

It now takes about 5 minutes to add a new brand to the Design System

Reflection
This project reinforced the importance of approaching system design as both a technical and organizational transformation. Migrating to Figma wasn’t just about moving files - it was about reshaping how 70+ designers collaborate, make decisions, and maintain consistency across 150 brands.

It also offered a rare opportunity to explore and stress-test Figma’s newest capabilities, including the then brand-new Variables feature announced at Config 2023. Working with an untested feature at scale required experimentation, patience, and creative problem-solving. Through extensive testing, we established reliable patterns for multi-brand theming and light/dark mode management - insights that proved valuable not only to Amdocs but to future system implementations as well.

It taught me how crucial it is to balance flexibility with governance: building a system that’s scalable and efficient, yet adaptable enough to handle constant change. Working closely with cross-functional teams also deepened my appreciation for clear documentation, structured onboarding, and the power of shared ownership in driving adoption.

Reflection
This project reinforced the importance of approaching system design as both a technical and organizational transformation. Migrating to Figma wasn’t just about moving files - it was about reshaping how 70+ designers collaborate, make decisions, and maintain consistency across 150 brands.

It also offered a rare opportunity to explore and stress-test Figma’s newest capabilities, including the then brand-new Variables feature announced at Config 2023. Working with an untested feature at scale required experimentation, patience, and creative problem-solving. Through extensive testing, we established reliable patterns for multi-brand theming and light/dark mode management - insights that proved valuable not only to Amdocs but to future system implementations as well.

It taught me how crucial it is to balance flexibility with governance: building a system that’s scalable and efficient, yet adaptable enough to handle constant change. Working closely with cross-functional teams also deepened my appreciation for clear documentation, structured onboarding, and the power of shared ownership in driving adoption.

Reflection
This project reinforced the importance of approaching system design as both a technical and organizational transformation. Migrating to Figma wasn’t just about moving files - it was about reshaping how 70+ designers collaborate, make decisions, and maintain consistency across 150 brands.

It also offered a rare opportunity to explore and stress-test Figma’s newest capabilities, including the then brand-new Variables feature announced at Config 2023. Working with an untested feature at scale required experimentation, patience, and creative problem-solving. Through extensive testing, we established reliable patterns for multi-brand theming and light/dark mode management - insights that proved valuable not only to Amdocs but to future system implementations as well.

It taught me how crucial it is to balance flexibility with governance: building a system that’s scalable and efficient, yet adaptable enough to handle constant change. Working closely with cross-functional teams also deepened my appreciation for clear documentation, structured onboarding, and the power of shared ownership in driving adoption.

Let’s talk

Made with ❤️ In Israel © 2025 Julia Skigar. All rights reserved.

Let’s talk

Made with ❤️ In Israel © 2025 Julia Skigar. All rights reserved.

Let’s talk

Made with ❤️ In Israel © 2025 Julia Skigar. All rights reserved.