Scaling consistency with the Allegro Design System
Building and operationalizing a unified design foundation for MaestroQA , enabling a full product redesign while closing the gap between design, engineering, and user experience.
A partially-built system with high stakes
When I took ownership of the design system mid-project, it was partially complete and lacked clear documentation, alignment, and adoption across teams. At the same time, the business was already investing heavily in a full product redesign built on this system , making the margin for error extremely small.
A product that outgrew its foundation
MaestroQA's product had grown rapidly without a unified design foundation. This project focused on building and operationalizing a scalable design system to unify the product experience, improve usability, and accelerate development, not just as a design artifact, but as a living operational tool.
Five pillars that moved the system forward
System Audit and Gap Analysis
Evaluated existing components, identified inconsistencies, and prioritized missing patterns that were actively blocking product teams from moving forward.
Component Standardization
Rebuilt and extended components with a focus on scalability, reusability, and clarity, including usage guidelines and a deliberate reduction of redundant variations.
Accessibility First
Embedded AA compliance into the system by default, ensuring components met accessibility standards from the ground up and reducing costly downstream rework.
Cross-Functional Collaboration
Worked closely with engineering to ensure components were not only well-designed, but practical to implement, maintain, and extend over time.
Advocacy and Adoption
Actively reinforced best practices across the team, ensuring the system wasn't just built, but actually used, understood, and trusted by the people working with it daily.
Raising the bar beyond the minimum standard
Accessibility wasn't a checkbox. By embedding WCAG compliance into every component from the start, Allegro transformed MaestroQA's product from an inconsistently accessible interface into one that met, and in most cases exceeded, industry standards. The result was a product that genuinely worked for more people.
Less is more: a leaner, sharper system
Before Allegro could grow, it needed to shrink. A thorough audit of existing patterns across the product revealed significant duplication: components that served the same purpose under different names, or minor variants that added complexity without adding value. Consolidating these freed the team to focus on quality over quantity.
Agent Performance: the system's first real test
The Allegro system and the product redesign didn't launch separately. They debuted together through Agent Performance, a new flagship feature that let us validate both simultaneously. For pilot customers, it was a concrete, visible signal of progress, and for the team, proof that the system worked in the wild.
By unveiling the redesigned product alongside the new design library through Agent Performance, we tested both in a real customer context , gathering signal on usability, visual coherence, and feature adoption while building early momentum. Pilot customers experienced the system as a finished product, not a work in progress.
A foundation the product could grow from
The Allegro system gave the team tools, confidence, and shared language, enabling a successful product redesign and sustainable development going forward.
What this project taught me about systems work
Explore the Allegro Design System
A public, limited-access version of the component library, viewable in Figma.
Public · Limited Access · View Only