top of page
Design System.png

Creating consistency and speed through shared components and visual language

What and Why _.png

A design system is like a team’s shared toolbox. It has the colors, typography, buttons, patterns, and rules that keep everything looking and working the same way.

 

Companies create them so products don’t feel like they’re built by different teams in isolation. It saves time, avoids duplication, and makes life easier for both designers and developers.

​

Without one, every button, form, or alert can end up looking slightly different, which confuses users and slows down teams.

 

A design system helps us stay consistent, scale faster, and keep the brand identity strong.

My Experience.png
doodle_259.png
design 1.png

I got to work on two versions of the design system at SITA.

  • Version 1 (Blue) was more about building a strong base setting up consistent UI patterns across different apps and portfolios. It was the first step to align all products under one visual and functional language.

  • Version 2 (Green) was a rebranding effort, where the company wanted to highlight sustainability as part of its identity. Green became the new core color, and the system also moved into a bento-style structure that felt fresher and more modular.

​

I contributed by creating custom components when product teams needed them. Since different products ran on different stacks (like Telerik, Blazor, Angular), it was often a push-and-pull to stay close to the system. My job was to bridge that gap so teams didn’t drift too far away.​​​​​​​

​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​

​​​​​​​​​​​​​

figma_cheatsheet_takeaways 1.png
My Takeaways.png
Vector-13.png
Snippets from Figma.png
doodle_275.png
My Experience.png

Working on two versions of the design system gave me hands-on exposure to how shared guidelines evolve over time. I created custom components, adapted designs to different tech stacks, and collaborated with developers to bridge gaps between design and implementation.

It was a mix of creativity and structured problem-solving.

doodle_222.png
What I Learned.png

I learned the importance of thinking beyond screens and focusing on systems.

Consistency, accessibility, and clear component structure make a huge difference at scale.

 

I also understood how close collaboration with dev teams is essential to make the system truly work in real products.

doodle_274.png
doodle_07.png
doodle_276.png
bottom of page