Triggle

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

How did I help them

  • Design System Strategy
  • UI Architecture
  • Documentation
  • Accessibility
  • Design–Dev Collaboration
Design System tokens, components, and documentation overview.

Industry

SaaS / Travel Tech

Headquarters

Palma, Spain

Timeline

12 months (Ongoing)

Company Size

40–60 employees

Role

Lead Product Designer

Stakeholders

CTO, Front-end Lead, Product Manager, QA Lead

How a growing SaaS company scaled consistency, speed, and quality through a unified Design System adopted across multiple products.

Context

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.

  • Fragmented UI libraries – duplicated patterns and inconsistent behavior.
  • High maintenance costs – parallel fixes and QA duplication.
  • Slow delivery cycles – design–dev friction and lack of parity.
  • Limited documentation – tribal knowledge instead of standards.
  • Scalability issues – new products couldn’t easily reuse components.
Mapping inconsistencies and defining a unified foundation for multi-product growth.

Discovery & Strategy

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.

The Design System reached Level 3 maturity, reduced UI bugs by 45%, and achieved 44% component coverage across products.

Impact

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.

Consistency drives confidence — the DS not only improved UX and delivery but also unified culture across teams.

Reflection

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.

Leader · Builder · Thinker · Analyst · Digitalist · Learner · AI Driven · Collaborator · Creative · Optimizer · Innovator · Maker · Researcher · Strategist · Designer · Leader · Builder · Thinker · Analyst · Digitalist · Learner · AI Driven · Collaborator · Creative · Optimizer · Innovator · Maker · Researcher · Strategist · Designer ·
View