top of page
Design System.png

My journey of using heuristics to evaluate designs and spot usability gaps.

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.

  • 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
doodle_189.png
My Experience.png

As a new designer, running heuristic evaluations taught me more than just spotting usability issues.

It showed me how different teammates see problems in their own way, and how bringing those views together builds empathy and trust.

​

By letting auditors explore freely and capturing everything in a simple Miro grid, I made sure the findings felt like a team effort, not just mine. This helped me bond with developers and leads, and gave me confidence to connect user needs with real actions in the backlog.

doodle_127.png
What I Learned.png

Heuristics are powerful because they give structure to feedback.

 

They also help teams move from “this doesn’t feel right” to “this breaks a principle,” making conversations smoother and more productive.

 

And more importantly, they become actionable when shared, prioritized, and owned by the whole team.

doodle_274.png
doodle_07.png
bottom of page