Unifying three disconnected products with a design system
Three complementary fraud-prevention products, each with its own interface and interaction model. I built the design system and code library that brought them together, and redesigned the core screens analysts used every day.
Unified three standalone products into one coherent suite, built on a design system and modular UI framework that cut front-end build time and underpinned every release that followed.
Context
On becoming Senior Designer at The AI Corporation, I inherited three complementary products used by fraud analysts. Each had grown up separately, with its own UI, its own UX, and its own way of doing the same things differently. For the analysts who moved between them, every inconsistency was a small tax on attention, and in fraud work, attention is the job.
Approach
The work split into two reinforcing halves: build the foundation, and prove it on the screens that mattered most.
A design system from nothing
The organisation had no prior standardisation of design or implementation. I researched the products, then created a comprehensive design system and the front-end code library to implement it, so the standard became the path of least resistance for developers rather than a document they could ignore. From that point on, it formed the basis of all front-end development across the suite.
Redesigning the core screens
I applied the system to the products analysts relied on:
- RiskNet, the core product, used by fraud analysts to identify suspicious transactions. I redesigned the main screen with the analysts, prioritising the presentation of key data points and giving important actions logical, intuitive placement.
- SmartScore, a set of screens for building automated alert rules. I rebuilt the flow as an end-to-end wizard, significantly simplifying rule creation, and applied the same design system used in RiskNet so the experience stayed consistent across the suite.
Outcome
The disconnected suite became a coherent one, built on a shared system rather than three divergent codebases. The modular UI framework underneath it cut front-end build time and gave the products room to grow without fragmenting again. The redesigned RiskNet and SmartScore screens put the right data and the right actions where analysts expected them, and every product built afterwards started from the same foundation instead of reinventing it.
This was where my conviction about enterprise design systems took hold: the value lies in letting an organisation stop paying the consistency tax over and over, not in the component library itself. It’s the same belief I carried into building design systems at IDBS and, later, Xceptor.
(This sat within a 2011–2016 tenure at The AI Corporation that also included designing an award-winning, location-based project management product, work that won the European Satellite Navigation Innovation Award and helped secure venture funding.)