All work

Olympus Scalable Global Design System

Designing a token-driven global design system for enterprise SaaS products, client solutions, and distributed product teams.

Olympus is a cloud-enabled SaaS platform powering enterprise dashboards and client-facing solutions across Haptiq’s product ecosystem. I helped evolve its design system into a scalable, token-driven foundation that supported global teams, white-label products, and enterprise clients including Sony Music, P&G, Nestlé, Electrolux, and more.

Company
Haptiq
Client
Internal Haptiq project for Olympus
Timeline
2025-2026
My Role
UI Designer & Systems Designer / Architect
Teams
Cross-functional teams across North America, Poland, and India
Tools
Figma, FigJam
Scope
Global Design System for Haptiq’s Olympus software suite and client-facing solutions for brands including Sony Music, P&G, Nestlé, Electrolux, ZCG, DRF, and more.
Haptiq Core 2.0 component documentation pages laid out side by side

Background

Haptiq operates across two connected sides of the business: a service side and a product side.

Service sideMy team

Pantheon is Haptiq’s technology enablement solution suite, supporting clients end to end.

  • Product development
  • Value creation
  • UX/UI design
  • Consulting
  • System integrations
  • AI & data science
  • Intelligent automation
  • Cloud engineering
  • Marketing technology
  • ITSM
  • Digital transformation
Product sideThis project

Olympus is Haptiq’s SaaS platform foundation, powering enterprise dashboards, management systems and client-facing solutions. As it became the base for more products, it needed a tokenized design system that could support:

  • High-density data interfaces
  • AI-enabled workflows
  • White-label products
  • Global delivery teams

Olympus Product Ecosystem

Olympus was not a single dashboard. It was a modular SaaS ecosystem supporting the full alternative asset management lifecycle, from fundraising and investor engagement to investment, portfolio management, reporting, and exit.

The platform included modules such as Investor Relations, Deal Management, AI Document Processing, Performance+, Data Room, Marketing Cloud, Private Credit, and Executive Reporting. Each module had different workflows, data needs, and user expectations, but all needed to feel like one unified product experience.

DataArtificial IntelligenceAutomationComplianceReporting

Because Olympus also connected multiple data sources, including ERP systems, POS systems, inventory platforms, files, market data, and marketing technology tools, the design system had to support dense tables, KPI cards, charts, filters, alerts, permission-based data rooms, and AI-enabled insights while maintaining clarity and consistency.

ERP • Oracle, SAP, Dynamics

Direct connectivity via APIs for Trial Balance details

FILES • Excel, Sheets, Sharepoint

Enrichment level data unique to each business easily integrated

MARKET DATA • CapIQ, Alpha Advantage, US Census

External data sets for additional analysis and insight

POS • Crunchtime, Micros, Opera

Source data (ops, sales, etc.) with direct impact on financials

INVENTORY • Ordoro, Katana, Inflow

Profitability KPIs to further inform the financial picture

MARTECH • GA, SFDC, Zoho, Hubspot

Internal data to help support valuation and forecasting models

Olympus dashboard on a laptop

Problem

We were growing. Our design system could not.

As Haptiq scaled its client base, the existing design-to-development pipeline reached a breaking point.

The system lacked tokenization, which meant UI changes required manual updates across files and code. Different teams were working with inconsistent patterns, creating visual and functional drift. White-labeling was also difficult because switching from Olympus branding to a client-branded experience required manual overrides instead of system-level theme changes.

The result was slower delivery, duplicated design work, inconsistent UI quality, and unnecessary friction between design and engineering.

Olympus on a tablet

Building it the atomic way

Rebuilding the system meant thinking in layers, from single atoms up to full pages. Pick a layer to see what it means in Haptiq’s system.

In Haptiq Core 2.0 Buttons, icon buttons, toggles, checkboxes, chips and avatars.
ButtonButtonButtonDRF AILabel Label Label AF

Design Goal

Move from designing individual screens to architecting a scalable system.

The goal was to create a single scalable design foundation that more than 100 designers and engineers could use to build consistent, enterprise-ready products across Olympus and Haptiq’s client solutions.

Animation explaining how variables switch themes

I collaborated with distributed design and engineering teams across North America, Poland, and India to help rebuild the system around design tokens, Figma Variables, multi-brand theming, and design-to-code alignment.

We needed to create:

  • 01A single source of truth for global teams
  • 02Tokenized foundations for color, spacing, typography, radius, and components
  • 03Multi-brand and white-label support
  • 04Better parity between Figma and production
  • 05Faster delivery for client-facing enterprise solutions
  • 06A flexible system for AI, data, dashboards, and high-density workflows

The Initiative

Design Tokens for Everything

We launched a system-level initiative to decouple visual styling from component logic. Instead of relying on static styles, we rebuilt the design system around a multi-tier token hierarchy. This allowed the product team to update brand, theme, and UI behavior at the system level rather than manually editing individual components or screens.

Design System
Hex value#0061DD
Primitive colourBlue-600
Semantic coloursurface-highlight
ComponentButton
Change the primitive:Only the primitive changes; everything downstream follows.
Button

Token Architecture

The system was structured into 3 layers:

Primitive /Reference tokensSemantic TokenComponent TokenUI Output#0061DDprimaryColorinteractionColorbuttonPrimaryBgColorButtonValueBase VariablesCommonSpecificReachSpecificity
Primitive /Reference tokensSemantic TokenComponent TokenUI Output#0061DDFont size: 12pxFont weight: MediumCorner Radius: 100primaryColorinteractionColorbuttonPrimaryBgColorfont-sm-500label-strongbutton-label-textradius-largeradius-interactivebutton-radiusButton

This structure made the system more flexible. A theme could change at the semantic level without breaking component logic, and component tokens gave teams more granular control when needed.

Screens built from the token system

Variables & Multi-Mode Support

Using Figma Variables, we created modes that allowed teams to switch between default Olympus styling and client-branded themes inside the same system.

Instead of redesigning each client experience from scratch, teams could apply a new visual identity through the design system.

This supported:

  • 01Default Olympus theme
  • 02Client-branded themes
  • 03Light and dark modes
  • 04Scalable white-label configurations
  • 05Future product extensions

Dev Handoff

Figma-to-Code Alignment

A key part of the project was improving the relationship between design and engineering. Tokens were mapped to CSS root variables so developers could implement values directly instead of interpreting static design files.

Figma Tokens
Colors
Border Radius
Applied to the componentButton labelbackground: var(--color-primary);
border-radius: var(--radius-small);

Pick a colour or radius in the plugin, then check the JSON and Handoff tabs: design and code read the same tokens.

This created stronger parity between Figma and production, reduced ambiguity, and helped distributed teams work from the same system language.

Container
border: button.cta.default.border-color
fill: button.cta.default.background-color
height: button.s.height
paddingLeft: button.s.padding-left
paddingRight: button.s.padding-right
borderRadius: button.border-radius
borderWidth: button.border-width

Component Library

The global design system included reusable components optimized for enterprise dashboards and high-density data products.

Components included: buttons, inputs, dropdowns, filters, tables, cards, modals, alerts, tags, chips, navigation, sidebars, data visualizations, pagination, tooltips, and form patterns.

Impact

The redesigned system created measurable operational leverage.

  • 01Increased development velocity by 40%
  • 02Reduced branded environment deployment from weeks to hours
  • 03Created a single source of truth across the global product suite
  • 04Improved consistency across dashboards, modules, and client solutions
  • 05Reduced design debt caused by duplicated styles and manual overrides
  • 06Improved design-to-development alignment across distributed teams