top of page
Natura GaYa Design System
Optimizing Design System architecture and adoption to Latam products teams
Client
Natura Cosmetics
Year
2025
Type
Design System
Challenge
Increase the confidence to use design system components without fear of low performance and break changes.
Use
Section small
Along with other focal points, we built a use and contribution flow that was based on consultations with the focal point closest to the designer squad. Contributions could be of 3 types: correction, evolution or creation of a new component, be it team or core. As Design Chapter Lead, I was also responsible for taking the needs of designers from shared product squads to discuss design system improvements at iDS focal points meetings every two weeks.
Contribution flow
Performance in Design Critiques and consulting of component use
Impact
˜50%
more efficiency from design to code in production
Optimized components, with clear purposes, simple-to-use properties, and documentation
Better high quality product's navigation and consistency
Plan
The Design System team is small and lacks the budget to expand. With 2 designers and 3 developers, we will focus 80% of our time on creating GaYa 2.0, while also supporting 20% of the time on bug fixes for the current Design System.
The new generation will work in a new Figma and code environment, and it will be split into 4 phases (first 2 before beta launch release and 2 after, releases each two-week sprint):
-
Recreation of the Foundation: review of the Design Principles, reorganization of the library architecture, new taxonomy of primitive and semantic tokens.
-
Structure: recreate atomic components and create a playbook with guidelines to use and contribute to Core and Team components.
GaYa 2.0 Launch release
(metrics: likes and comments in the documentation page, use of components per squads, emails by roles that read the playbook).
-
Coverage: recreate essential components
-
Evolution: recreate the rest of components and templates
(metrics: likes and comments in the documentation page, use of components per squads, emails by roles that read the playbook, nº of Detaches, NPS)
xx%
Lorem ipsum dolor sit amet nsectetur
xx%
Lorem ipsum dolor sit amet nsectetur
Lorem ipsum dolor sit amet consectetur. Id ipsum vel dictum et integer in. Non lectus mi sit ipsum non etiam quis. Placerat amet tempor gravida amet volutpat dui nam odio nunc. Metus sed lacus massa pellentesque purus nullam.
xx%
Lorem ipsum dolor sit amet nsectetur
xx%
Lorem ipsum dolor sit amet nsectetur
Workshop to pilot of a Team components library.
Design process and Jira workflow upstream/downstream review.
bottom of page