One UX standard across 7 products and 4 brands
An earlier chapter. As Lead Product Designer I set the shared UX rules and the first version of the design system, Titan v1. It is the groundwork that later made the unified app possible.
- Products on one shared component library
- 7
- Products on one shared component library
- Duplicate UI patterns after the first audit
- 38 → 11
- Duplicate UI patterns after the first audit
- Less time from design to development
- ~40%
- Less time from design to development
- Time to resolve a cross-team UX dispute
- 2 wks → 3 days
- Time to resolve a cross-team UX dispute
Context
Seven products under four brands, each with its own team and its own way of building the same table, filter, or empty state. The first audit found 38 duplicate UI patterns.
Core Problem
Each brand had to keep its own look. The patterns underneath did not need to differ.
My Role
I owned UX oversight across four brands and seven products, as the layer between their product teams. I also led Titan v1, the shared library behind it.
Design Reviews
A fortnightly cross-product review focused on flows and behavior, not just visuals.
Brand-Aware Components
Brand-level variants inside shared components, so a brand changes its skin, not its patterns.
Mediation
A written rule for local exceptions: a team can diverge if it documents why, and the exception is reviewed after one quarter.
Outcomes
Seven products on one component library, Titan v1, with 200+ components
Duplicate UI patterns cut from 38 to 11 after the first audit
Cross-team UX disputes resolved in about 3 days instead of 2 weeks
Four brands kept their identity inside one shared framework