Luke FinchSay hello

Work

Building a design system for One App

Bringing legacy design systems together as shared product infrastructure.

Contentsquare's product ecosystem had grown across several products, teams, and frontend foundations. A shared design system could make the experience more coherent, but it also had to work across React and Vue applications and give teams a practical route off their existing libraries.

I shaped the case for treating the Consolidated Design System as product infrastructure. The work covered component strategy, migration, adoption, and the operating practices that make a shared system useful beyond the team that builds it.

Teams needed a way to prioritise components, revamp patterns that no longer fit, add missing components, and track adoption. I connected that work to contribution guidance, design sprints, council meetings, designer open sessions, and shared communication channels. This gave teams ways to use the system, raise gaps, and influence its direction.

The system was designed to support One App: a shared foundation for bringing Contentsquare, Hotjar, and Heap experiences together. The work therefore extended beyond visual consistency. It addressed how product teams could build and maintain a more unified experience across a fragmented application estate.

The adoption report recorded 75 components delivered and approximately 74% of tracked component usage on the new system. It also showed the new system ahead of cs-materials, with hotsauce at zero usage across the tracked surface.