← Selected work

Valocity

Standardising a FinTech property product across global markets.

Valocity Quantum Design System — one design language across four product teams in three markets.

Growth vs consistency

Valocity serves major banks across New Zealand, Australia, and India, yet rapid growth led to four product streams operating as disconnected islands. This fragmentation caused massive design debt, inconsistent user experiences, and slow client onboarding.

It highlighted that we weren't just facing a visual issue, but a systemic scalability crisis that threatened our delivery speed, our brand, and our integrity across every market we served.

Four fragmented product UIs converging into a single unified dashboard: navigation, filters, table, shade, and image layers.

Quantum Design System

Four product teams. Three markets. One design language.

To resolve the bottleneck, we created the Quantum Design System. Beyond establishing a multi-tiered design token structure and a reusable component library, we designed a tier of universal design patterns to be shared across all product teams.

A key highlight was a standardised, modular dashboard pattern that catered to the diverse data needs of every team while maintaining a single, coherent UX logic.

White-labelling automation

Onboarding a new client used to take days of manual UI adjustments. With automated theme switching, it became a matter of minutes.

Design velocity

Teams stopped reinventing interaction models for every new feature. A library of pre-validated shared patterns meant designers could move faster without compromising consistency.

Quantum Design System pipeline: design tokens flowing through Azure DevOps and Style Dictionary to white-label Valocity products for ING, HSBC, Commonwealth, and Westpac.

Design leadership

Driving system adoption through structured design reviews and cross-team governance.

A design system is only as good as its adoption. I took the lead in making sure the Quantum Design System actually landed across teams. I mentored two junior designers, coaching them on how to leverage the token system and contribute to the shared component and pattern library.

By establishing a formalised design review process, we moved our workflow from a siloed output model to a collaborative guild model, ensuring every feature met our new global standards.

The measure of a design system isn't the documentation. It's whether junior designers can pick it up and ship features confidently without a senior guiding them at every step. Within a few months, both designers I mentored were doing exactly that.

Design quality assurance

A single source of truth that eliminated 80% of redundant design queries and visual inconsistencies across the four product streams.

Team capability building

Empowered junior designers to handle complex features independently by giving them a clear, systemic framework to follow.

Quantum documentation showing layout and spacing tokens for the Button.Light component, with named padding and border-radius tokens.

Complexity, simplified

Applying the new framework to Nexus to prove the versatility of a standardised UX approach.

We applied the Quantum framework to Nexus, a high-stakes tool for real estate agents to generate CMA (Comparative Market Analysis) reports. Despite the overwhelming complexity of property data, I used the design system and worked alongside other team designers to create an effortless workflow for agents.

This proved the system's true value: we delivered a tool that met heavy regulatory requirements while providing an intuitive experience that required zero training for busy agents.

The Nexus CMA tool shown responsively across desktop, tablet, and mobile, presenting dense property data in a clean, consistent layout.

Impact beyond the pixels

Validating success through operational agility and a future-proofed design culture.

Before the Quantum Design System, four product teams were solving the same problems in four different ways. After it, they weren't. Redundant design queries dropped away, new bank integrations became significantly faster, and designers across New Zealand, Australia, and India were working from the same source of truth for the first time.

The deepest shift was cultural. Design moved from being a bottleneck to driving what the business could do next. That's what a design system is actually for.

Next project Spark IoT From a UX audit to a rebuilt platform operators depend on every day.