Design System for the Youlytics Portal
As the Youlytics Portal expanded to support dashboards, reporting, asset management, and collaboration workflows across the company, the product surface area grew quickly. Early UI patterns were created ad hoc to meet immediate needs, which led to inconsistencies, repeated design decisions, and slower iteration over time. To support long-term scalability and consistency, I designed and evolved a shared design system that served as foundational infrastructure for the Youlytics Portal. More images coming soon
Role
Lead Product Designer
Client
Rover
Timeline
Ongoing
Project Scope
Designed and evolved the design system used across the Youlytics Portal, supporting a 100+ person organization. - Owned system structure, component definitions, and interaction patterns - Evolved the system in parallel with product development - Partnered closely with engineering to ensure patterns scaled in production - Replaced fragmented, ad-hoc UI decisions with shared, reusable standards
The Challenge
As product development accelerated, teams faced growing friction: - UI patterns were inconsistent across dashboards and reporting views - Design decisions were repeatedly revisited instead of reused - Engineers interpreted designs differently without shared conventions - Scaling the product introduced risk of fragmentation and rework Without a shared system, maintaining clarity, consistency, and velocity became increasingly difficult.
Key Decision
Build the system incrementally alongside the product
Rather than attempting to define a comprehensive system upfront, I evolved the design system in parallel with real product work. This allowed patterns to emerge naturally from actual usage across dashboards, reporting, asset management, and collaboration workflows. Designing incrementally ensured the system remained practical, relevant, and closely aligned with product needs as the platform evolved.
The Solution
Design components around real usage patterns, not visual uniformity
Components were structured around how teams actually consumed and interacted with data, including tables, filters, charts, states, and actions. I prioritized clarity, density, and consistency for complex internal workflows over purely aesthetic alignment. This approach reduced cognitive load and ensured interaction patterns remained predictable across reporting and analytics views.
What the System Enabled
- Faster iteration across the Youlytics Portal without re-solving common patterns - Consistent interaction behavior across complex data views - Reduced duplication of design and development effort - Easier onboarding for designers and engineers contributing to the product
Impact
- Improved consistency and usability across the Youlytics Portal - Reduced rework caused by ad-hoc UI decisions - Enabled the product to scale without sacrificing clarity or development velocity