Dharma

003

Project details

BRAND

Dotz

YEAR

2022

PROJECT GOAL

Create +20 components and increase Design System Adoption from Dotz team, giving them design maturity and leading them to better construct with the DS.

ROLE

I was the Specialist Designer leading Dharma Design System, taking decisions to new and current components, from conception to handoff, guiding 10 designers to use and construct.

from something that we get tired to something with fun.

is it possible with ds?

When we talk about Design system, we're not talking about buttons. We're talking about scalability, and it comes from people. So, when we talk about Design System, we talk about people, and what they believe, what they like, what they see... But technically, how they contribute to build a visual consistency inside all products.
‍

So, how we discover ways to solve? Research. We did an Internal research to understand how the team feels to use DS, understand their maturity with DS and how they could contribute in future to keep DS growing and mantaining it well.

Ok, so if they think that's useful, why they don't like to use it?

is it an confirm bias research?

Many suggestions could answer it, there's not right or wrong, but again, we need to deep understand what kind of thing are bothering them to use. And the way that i choose to understand it is finding what they actually like in DS.
‍

Considering that we have a Web library and we're still building a App library, will be great to understand what they enjoy to use.

ok, but we're gonna work on what they like, or in what they don't?

THEY KNOW SOMETHING?

Both, but now it's time to bring them to the table, and understand what they think in visual conceptions, consistency, accessibility and what they believe that could be a better way, grouping those informations to become app components. But... Is it their job, or yours? Mine, of course. But as we have to engage them, we need to put them in the construction, people like to be a part of some construction, and it's more easily to make them use it in this way.

ok, but is all of that scalable, or just to give visual pleasant?

Is it possible to have both?

We made components in group sessions and we could say: All that was worth! Responsible components that could be applied to prototype in Android or iOs sizes. And this scalability could be applied to something that really is a game changer: Time-to-market and design delivery.
‍

Since we've implemented, the time to delivery was reduced by at least 40%. Considering estimated time to build vs Using Design Sytem Below we have some screen that was designed during this project.

To end conclusions, about money, considering tech and design, the cost reduced by a team using DS was about R$43,000.00. And all squads started to use DS, not only the new components, but both libraries. The team satisfaction using DS now is 8. So, next steps are to brought them to keep constructing, and make DS joyable.

What kind of trouble did you find in this journey?

OR IT WAS A HAPPY ENDING?

If i could resume it, it will be:
‍
- Team needs.
- Brand change.
- DS dedicated team was reduced.
- Time to delivery components considering both libraries.
- Handoff and fix old bugs about components in Figma.
- Conflicted design decisions.
- To consider all opinions to build the components and make them available fast.
‍

We had a great gain in this project, but also it was a real challenge. All those things had appeared in the process, and we're talking about a project that had 8 months of duration. It shown me that priority and group decisions could lead to success, but also, you need to have the ability to mediate it, and consider everyone.