<aside> 📌

You can explore the live system on **Figma Community** and if you’re curious about the behind-the-scenes journey, check out the full case study on Behance

</aside>

Overview

Every new project used to start the same way — building a design system from scratch, recreating components, redefining rules, and trying to keep everything consistent. It worked… but it wasn’t efficient.

That’s when we started thinking:

what if we had one strong foundation that could flex and scale with every project, instead of starting over each time?

This idea evolved into a centralized design system. A shared, living resource that allows our team to move faster, maintain consistency, and focus on what truly matters: crafting meaningful user experiences rather than redoing UI elements for every project.

Goals & Challenges

<aside> 🎯

Goals

Build once, use everywhere: create a reusable system that scales across projects.
Save time and effort: reduce repetitive setup work so designers can focus on UX.
Design smarter: allow more time for problem-solving rather than UI setup.
Collaborate better :establish a shared language for designers and developers alike </aside>

<aside> 🚧

Challenges

Finding the right balance between flexibility and consistency was critical. We needed a system that could grow without becoming restrictive.
Aligning teams with different workflows required clear communication and iteration.
Maintaining documentation and version control became as important as designing components themselves. </aside>

Through continuous testing, feedback, and collaboration, we shaped a system that works not just in theory, but in everyday design practice.

My role

UX Designer — UX designer for the root design system by collaborating with developers and gathering insights, designed core components, and contributed to introducing the system through company case studies and social media posts.

Team: 1 Lead Designer, 3 UX Designers

The process

Exploring current workflows

Building on our vision for a centralized design system, we started by exploring how our team currently approached design systems for different projects. Through collaborative interviews with designers and developers, we uncovered individual practices, pain points, and expectations.

We asked about the usability of existing libraries, challenges during design handoffs, and what features would make a new system genuinely useful. This research helped us shape a foundation that addressed real needs, blending efficiency with flexibility.

<aside>

45+ questions asked

</aside>

<aside>

10 designers interviewed

</aside>

<aside>

14 developers interviewed

</aside>