Design System
Natura&Co

The Process

---

Research and Analysis

The first step was to conduct thorough research to understand the existing design system, its strengths, weaknesses, and pain points. I collaborated with designers, developers, and stakeholders to gather insights and feedback, which helped in defining the status of the Design System and its components.

Defining Tasks and Objectives

With a clear understanding of the design system's current state, it's easier to specific goals and objectives for the improvement process in each sprint. These goals were focused on enhancing collaboration, streamlining workflows, and delivering a more consistent user experience on every platform.

Design System Audit

I performed an extensive audit of the existing design system to identify outdated components, inconsistencies, and areas for improvement. This audit was documented using Notion and Jira, creating visual representations of the design system's status and components relationships.

Creating a Roadmap

Based on the research, analysis and audit, a roadmap was defined outlining the project's tasks, timelines and milestones. This roadmap served as a guiding document for the team, ensuring we stayed on track throughout the improvement process. Raising in each sprint the process of analysis, development, handoff and documentation necessary to update the components.

Iterative Design and Development

Using Figma and Adobe XD, I will iteratively design and prototype updated components if needed. I collaborated closely with the developers during this process to ensure technical feasibility and efficient implementation.

Documentation and Guidelines

As new components were designed or updated, I simultaneously documented their technical specifications, usage guidelines, and behavior across different platforms. This documentation was organized using Zeroheight, making it easily accessible for all team members.

Testing and Quality Assurance

Every component underwent rigorous testing to ensure it met the desired standards and worked seamlessly across various technologies. Storybook was used to test the components' technical feasibility and to address any visual issues promptly.

Solutions