Context and Challenge
Nelogica is a tech giant with over 500 employees and large teams working simultaneously across multiple platforms. During the development of a new product focused on the cryptocurrency market, I conducted a broad review across the company's other products and identified a critical gap: the absence of a structured Design System.
The Core Problem
Without a structured Design System, the new product was bound to inherit the same limitations and efficiency bottlenecks already faced by the company's other major products. I saw a strategic opportunity here: to build a foundation from scratch that would serve as a business case (success story) to prove its value across Nelogica's entire operation.
To solve this, I led several strategic discussions with developers, the PO, and the UX Lead. Since the product was still under construction, I saw a strong chance to create a Design System from the ground up, focused on reducing creation time and improving technical communication—and, with this alignment, I secured the support and approval of leadership to kick off the project.
My Role and Processes
-
Audited and mapped inconsistencies I conducted a meticulous survey of all interface artifacts (colors, typography, spacing, buttons, and modals) during the discovery phase.
-
Optimized existing processes Instead of reinventing the wheel, I analyzed previous initiatives (design style guides and code reused by devs) and leveraged these foundations to accelerate the new product's definitions.
-
Standardized the technical language I defined the Design Tokens architecture (semantic variables). I established clear naming conventions (e.g., brand-primary-color) so that developers would know the exact function of a component just by reading its name.
-
Democratized governance I created and organized the official Design System documentation in Notion. This allowed any team member, current or future, to access and understand the principles guiding the interface's construction.
The New Experience
The New Experience
Business Impact
Agile
A drastic reduction in screen development time — screens were now assembled from consistent blocks.
Handoff
The bridge between Design and Engineering was consolidated. Teams started speaking the same technical language.
Centric
With standardized styles, the team stopped "pushing pixels" and focused on truly improving the user journey.
Project Lessons
01 / DESIGN OPS AND SCALABILITY
Design only truly scales when there is clear governance and continuous operational alignment between designers and software engineers.
02 / ACCESSIBILITY FROM THE GROUND UP
Accessibility shouldn't be treated as a final validation step, but rather as a fundamental requirement for all components and tokens from their conception.
03 / DOCUMENTATION AS A PRODUCT
A Design System without living documentation is useless. Centralizing rules in Notion and synchronizing guides with engineering ensures full team adherence.