How a 20+ product enterprise portfolio, spanning different tech stacks, acquired platforms, and regional teams, was brought under a single design language, without slowing product delivery down.
Not a single bad decision, a portfolio that had grown in four directions at once, with no shared foundation pulling it back together.
Different tech stacks across product teams, each rendering UI its own way
Acquired platforms carrying 20–25 years of legacy design debt
Teams distributed across regions, each with informal, undocumented standards
No shared source of truth for interaction, accessibility, or visual patterns
The pattern repeated across product types: teams solving the same problems independently, then converging on one shared foundation.
Built independently by separate teams, each with its own patterns
No shared components; every dashboard solved layout from scratch
Accessibility fixes applied manually, release by release
Rebuilt on shared Floret components, common across every dashboard
One consistent visual hierarchy instead of three competing conventions
Accessibility built into the component, inherited by default
Custom grid and status logic maintained separately per region
No shared color or status language; each team invented its own
Small changes required touching multiple codebases at once
Shared status-token system used consistently across every region
One color-coding convention, understood the same way everywhere
A single component update propagates everywhere it's used
Desktop patterns stretched onto small screens, not designed for them
No shared mobile component library to build from
Touch targets and spacing varied screen to screen
28+ mobile-specific patterns, designed for small screens from the start
Touch targets meet accessibility minimums by default
Same visual language as desktop, adapted rather than shrunk
Used Microsoft Fluent and Google Material as reference points for structure and rigor, then built a distinct visual identity suited to the enterprise's own products and users.
Catalogued inconsistent navigation models, visual density, and duplicated interaction patterns for the same core tasks, making the fragmentation visible and prioritizable.
Codified into 42+ reusable patterns and 65+ components, built centrally so no product team had to rediscover or reinterpret usability and accessibility rules on its own.
Applied the system across floor operations, cage and credit management, table management, kiosks, and patron-facing mobile apps, each transformed using the same reusable foundation rather than a bespoke redesign.