Building a scalable multi-product Design System to unify experience and accelerate delivery

Triggle is a SaaS company specialized in B2B travel technology, powering booking platforms for hotels and suppliers. As the product suite grew, design and code consistency started to diverge across multiple repositories and teams.

Different squads built components independently, resulting in duplicated patterns, visual inconsistencies, and maintenance overhead. The lack of shared documentation and tokens slowed down design and engineering velocity.

The Challenge

We needed to unify UI and UX across three core products — Hotels Backoffice, Supplier Platform, and Core Admin — while ensuring scalability, accessibility, and efficient handoff between design and code.

We conducted an audit across all front-end repositories, identifying duplicated components and mismatched styles. Around 38% of the UI was shared but not centralized, which highlighted the need for a core library.

Through stakeholder workshops, we defined the Design System’s goals: unify experience, reduce QA effort, improve accessibility, and accelerate delivery. The strategy focused on incremental adoption rather than a big-bang rollout.

We evolved from a static UI kit to a fully governed Design System with design tokens, versioned releases, contribution workflow, and usage analytics. Documentation was centralized, and release notes improved visibility across teams.

The system was structured into Core and Product branches (Hotels and Supplier), enabling shared components while allowing domain-specific variations. This laid the groundwork for a scalable multi-product system (partial L4 maturity).

Governance & Collaboration

We defined contribution rules, release cadences, and component versioning. A governance group (Design + Front-end) ensured design-code parity, reviewing each new addition for quality and accessibility compliance.

The Design System became the foundation of every new Triggle product, empowering designers and developers with shared patterns, tokens, and documentation. Its scalability allowed simultaneous development across brands without losing coherence.

Metrics are internal estimates based on team retrospectives. Design maturity level is referenced against the infa.ai/learn/maturity framework. These figures are not formally audited.

Starting small proved key. By releasing incremental versions, adoption grew naturally. The focus on shared ownership encouraged contribution and avoided the ‘design team only’ bottleneck common in DS initiatives.

Beyond components, the Design System became a cultural tool. It aligned designers, developers, and PMs around shared standards, accelerating decision-making and raising the quality bar across Triggle’s product suite.