HELIX
Design System for a Multi-Cloud Console
YEAR
2023
BUILD
3 weeks
Helix had grown through acquisition, and its console showed it — three visual languages, inconsistent interaction patterns, and an engineering team rebuilding the same table component for the fourth time. I rebuilt the foundation: a token architecture spanning light, dark and high-contrast themes, a component library documented against real production use cases, and contribution rules that let product teams extend the system without forking it. Every component ships accessibility built in rather than bolted on. Adoption reached 87% of surfaces within two quarters, and new feature work now starts from assembly instead of invention.
When Helix expanded through acquisitions, it inherited a deeply fragmented platform plagued by three distinct visual languages, erratic interaction patterns, and massive engineering redundancies—including teams repeatedly rebuilding core components like data tables from scratch. To resolve this, I engineered a completely unified foundation built on a robust, scalable token architecture. This centralized framework natively supports light, dark, and high-contrast themes, immediately eliminating visual inconsistencies and providing a single, reliable source of truth for both design and engineering teams.
Moving beyond a static UI kit, I developed a comprehensive component library that was meticulously documented against real-world production use cases rather than idealized scenarios. Every component was shipped with accessibility structurally built-in from day one, ensuring compliance without requiring post-design remediation. By establishing clear governance and contribution rules, product teams were empowered to extend the system organically without forking the codebase. This strategic shift drove an 87% platform adoption rate within just two quarters, transforming the product development lifecycle from slow invention to rapid assembly.
