Website
Use case
Highlights
Increased design system adoption across modules
Improved component reuse and consistency
Reduced rework across teams
Secured leadership support through measurable ROI
Overview
The product was fragmented: six modules, different patterns, inconsistent experiences.
The design system existed, but it was not trusted. Adoption was uneven. Leadership did not see clear return on investment.
Resources to rebuild were limited.
The goal was not to redesign everything. It was to make the system valuable enough that teams would adopt it.
Understanding the Problem
The issue was structural — not visual.
Six modules with different UI patterns
Designers embedded in separate engineering pods
Fragmented design system across the product
Inconsistent user experience between modules
No clear ROI for leadership
Limited resources for a full rebuild
Without measurable impact, the system remained optional.
Strategic approach
The approach was to reposition the design system: from a design asset to delivery infrastructure.
Phased rollout tied to outcomes
Instead of a full rebuild, I defined a three-phase rollout. Each phase delivered usable value and was tied to measurable metrics.
Phase 1 focused on the foundation: core components, layout, type, spacing — and establishing baseline metrics.
Phase 2 expanded into navigation, forms, and shared interaction patterns.
Phase 3 introduced workflow templates and scalable patterns across modules.
Each phase was connected to metrics such as workflow speed, reuse, adoption, rework, and cycle time. More than 20 metrics were tracked to show change over time.
The system proved its value incrementally.
Principle: Adoption follows value. Value must be measurable.
Key Initiatives
Phase 1. Core system foundation
No consistent baseline across modules.
What I did
Defined core components and layout rules
Standardized typography and spacing
Established baseline metrics for performance tracking
What changed
A shared visual and structural foundation
Clear starting point for system adoption
Ability to measure improvement over time
Phase 2. Shared patterns and navigation
Workflows differed across modules.
What I did
Expanded the system to include navigation and form patterns
Standardized common interactions
Aligned teams around shared components
What changed
More consistent workflows across the product
Reduced duplication in design and engineering
Faster implementation of features
Phase 3. Workflow templates and scale
Modules still solved similar problems differently.
What I did
Introduced reusable workflow templates
Created scalable patterns across modules
Extended the system into end-to-end experiences
What changed
Greater consistency at the workflow level
Improved efficiency across teams
Stronger system adoption
Metrics and performance tracking
Leadership needed proof of value.
What I did
Tracked over 20 metrics across adoption and delivery
Measured workflow speed, reuse, rework, and cycle time
Integrated metrics into product and engineering discussions
What changed
Design system impact became visible
Decisions were supported by data
Leadership gained confidence in continued investment
Additional improvements
Reduced fragmentation across product modules
Increased alignment between design and engineering
Strengthened DesignOps and governance
Created repeatable rollout model for future systems work
Cross-Functional Collaboration
Worked closely with product, engineering, and leadership.
Aligned system rollout with delivery goals.
Used metrics as the common language for decision-making.
Financial Impact & Business Enablement
The design system became part of how the product shipped.
Adoption increased because it made teams faster. Leadership supported it because it showed measurable impact.
The system moved from optional to essential.
Increased efficiency through higher component reuse
Reduced rework across teams
Faster delivery through shared patterns
Improved ROI visibility for design investment
Takeaway
Buy-in is built over time. Show value. Measure it. Repeat.
Role
Director of UX
Defined and executed the design system strategy. Reframed the system as delivery infrastructure, led phased rollout, and tied adoption to measurable outcomes to secure executive buy-in and scale usage across the product.
Related Case Studies
Reducing onboarding friction by restructuring how users reach first value.
Making dependency behavior predictable in a visual planning system.
Scaling a product with limited design resources by building systems, not screens.
Lowering early drop off by restructuring how users reach first value.
Keep the product focused on the planning model, not expanding features.
Making product decisions that preserve control and predictability.
Designing scheduling behavior that feels powerful without becoming unpredictable.
Using direct observation to guide product decisions when analytics are incomplete.
Turning design from a service into a system tied to delivery outcomes.
Driving adoption and executive buy-in through phased, measurable impact.
Turning design into a decision driver by making its impact visible.
Turning fragmented research into a system that guides product decisions.