Proteus is a multi-brand design system platform designed to bring consistency, speed, and governance to a complex product ecosystem. Multiple brands shared the same product foundation, but visual and behavioural drift had made delivery slower, QA harder, and rebrands unnecessarily expensive. The work focused on building a token-first, component-led system that allowed brands to express themselves while keeping the underlying product experience stable and reusable.
The challenge
Design and delivery inconsistency had become a scaling problem. Multiple brands shared one product core, but each brand had drifted visually and structurally. Spacing, typography, components, states, and behaviours were inconsistent. Rebrands often became rebuilds, and quality depended too much on who last touched the UI.
- UI drift across multiple brands
- Inconsistent spacing, typography, components, and behaviours
- Rebrands taking too long
- Repeated QA issues and UI regressions
- Low component adoption
- No clear governance model
- Too many one-off solutions
How I approached it
The process started by identifying where inconsistency appeared most often and why teams were bypassing shared patterns. From there, the system moved toward a token-first model. Semantic tokens defined product intent, while brand tokens handled visual expression. Components consumed the semantic layer, allowing the same component to support different brands without being duplicated.
Audited repeated UI patterns and inconsistencies
Mapped common component and layout needs
Defined a semantic token architecture
Connected brand expression to semantic intent
Created reusable components with states and variants
Introduced governance for intake, review, release, and QA
Aligned design and engineering around reusable rules
Trade-offs
The main challenge was balancing flexibility with control. Each brand needed to feel distinct, but the product still needed to behave consistently. Too much freedom would recreate the original problem. Too much rigidity would push teams to work around the system.
- Driving adoption across teams
- Avoiding too many one-off components
- Supporting brand flexibility without breaking UX consistency
- Translating design rules into engineering-friendly logic
- Making governance feel like a speed enabler, not a blocker
Final direction
The final solution was a token-first, component-led design system. The foundation separated product intent from brand expression. Components had clear variants, states, spacing rules, and behavioural expectations. Teams could reskin or adapt a brand through configuration instead of rebuilding the interface from scratch.
Outcomes
Proteus created measurable improvements across consistency, delivery speed, adoption, and quality. UI inconsistency dropped from around 60–65% to under 20%. Full brand reskins went from 3–4 weeks to under 4 hours. Component adoption grew from under 15% to over 80%, and UI regressions per release dropped by around 67%.
The goal was not to police design. It was to make the best path the easiest path.
Design systems are not really about components. They are about reducing decision debt. When the system is structured well, teams move faster, brands stay flexible, and quality becomes repeatable instead of depending on memory, luck, or whoever last touched the UI.