# Overhauling ION Risk Intelligence’s compliance CMS

_Product design case study by Paul Kennedy. [Portfolio home](../../index.md) · [View the full page](index.html)_


An evidence-led redesign of the CMS that 400+ researchers use to build risk profiles, delivered in phases. Productivity rose 28% year on year, and its components went on to power a new client-facing search app.

**Role:**

Product Design Principal and lead designer on the project; mentored a junior designer

**Team:**

I worked closely with the Product Owner, Product Manager and 3 engineers

**Platform:**

Internal web CMS for compliance researchers, then a client-facing web app (KYC6 Search)

**Client:**

ION Risk Intelligence

**Scope:**

Information architecture, data model, Carbon design system adoption and UI across five delivery phases.

**Users:**

400+ compliance researchers worldwide

**Approach:**

Research and Hotjar, then phased delivery tested with researchers

**Timeline:**

6 months: 4 CMS phases, then KYC6 Search

**Results:**

+28%
productivity year on year, measured as profiles created or remediated per day
80SUS score
System Usability Scale score, up from 55 (grade D to A−); 316 responses from 400+ researchers
1 month
to deliver the KYC6 Search client app from the CMS components

**PEP:**

Politically exposed person

**SAN:**

Sanctioned

**RRE:**

Reputational risk evaluation

**KYC:**

Know your customer

**ID&V:**

Identification and verification

The existing CMS met basic data processing needs, but in a long-form entry format that was best described as stop and start. The global research team of 400+ people were crying out for a better solution.

### The old journey for adding evidence to a profile

Profile-led: every profile repeats the whole sequence

_The old stop-start journey: the whole sequence repeats for every profile the evidence mentions_

- 1 Work alongside researchers I worked closely with the research team to identify pain points in their day-to-day work.

- 2 Observe real behaviour I documented behaviour with Hotjar to see how researchers actually used the CMS.

- 3 Test with researchers I tested journeys and interactive prototypes with 2 research leads and 5 researchers, building their feedback in within the same phase.

- 4 Hand over as components I broke the prototypes into a list of required components and agreed IBM’s Carbon / React design system with the co-located dev team for a rapid build.

Screen recordings showed again and again that researchers spent more time scrolling within a task than entering the content needed to complete it.

### Pain points and how they were solved

Areas for improvement found in research, mapped to the phase that fixed each one

Evidence is where every profile starts, so the workflow had to be evidence-led, not profile-led.

### New journeys

Circular, evidence-led journeys that replace the stop-start loop

_Two ways in: create from a profile (A) or from the main menu (B)_

#### A Adding evidence from a profile

_Journey A: the circular journey for adding evidence from a profile_

#### B Adding evidence into the system

_Journey B: adding evidence into the system from any page_

#### C Adding profiles from an evidence

_Journey C: adding or creating profiles from an evidence_

ION CMS overhaulPhased delivery roadmap

Each phase ships on the foundations of the previous one · researchers adopt gradually

#### Phase 1Foundations

#### Phase 2Evidence

#### Phase 3Linking

#### Phase 4Methodology

#### Phase 5Client app

_Roadmap: what each of the five phases delivered_

### Phase cadence

Each phase about 1 month, tested twice with researchers; design and testing added up to about a month of the 6

- Design I designed the journeys and prototypes for the phase

- Test designs I tested for 1 week with 2 research leads and 5 researchers, before build

- Build With the PO, PM and 3 engineers on Carbon / React

- Test the build I tested the build with researchers at the end of the phase

- Release Feedback built in, then on to the next phase

### Key decisions

The choices that shaped the overhaul

- 1 Rebuild, don’t patch I proposed a new product built around an evidence-led workflow, rather than iterating on the old system. With the designs and workflow validated by the research team, it was an easy sell to the PO and PM, and we made the call together. Rejected: incremental fixes to the long-form, stop-start CMS Problem · Research

- 2 Ship in phases, not one big switch Researchers depend on the CMS every day, so I broke delivery into monthly phases to keep disruption low and let them learn new workflows gradually, with testing before and after every build. Rejected: a big-bang launch that would make 400+ researchers relearn everything at once Phases 1–4

- 3 Keep the source beside the form I used the adaptive layout from Phase 1 to make room for a split-screen evidence view, so researchers transcribe from the document without juggling browser tabs. Rejected: evidence in a separate tab, which hides the source while typing Profile with evidence · Pop-out

- 4 Build once, re-theme for clients Because I designed the CMS on a design system, engineering could reuse its components and re-theme them to build the client-facing KYC6 Search app in the final month of the project. Rejected: a bespoke client UI. Re-theming meant delivery in one month KYC6 Search

- Improved search results data table

- Pagination

- Search within results across all columns

- Adjustable match threshold

- Matched-on-alias flags

- Reduced scroll time

- Restructured data model

- Adaptive layout

Names, IDs, dates and article text in the mock-ups are fictional.

Scroll sideways to see the full screen.

#### Search results

#### Profile: tabs and accordions

A threshold slider with a typed value widens or narrows results, instead of fixed exact-match search.

A chip under the name explains why a row matched, so researchers can judge a hit without opening it.

Researchers can assess how complete a profile is at a glance, and accordions let them focus on one area.

Addresses and other lists reorder by drag and drop, with edit and delete on each row.

- Designed to reduce transcription errors

- Less reliance on multiple browser tabs

- Evidence pinned open across all tabs

- Pop-out for multi-screen users

- Evidence no longer nested in profiles

- Searchable evidence

- Linked profiles listed in the evidence view

#### Profile with split-screen evidence

BUDAPEST – The financial regulator today announced civil proceedings against Halvorsen Trading Kft. and its directors, including Aleksander Varga, alleging a pattern of improper conduct spanning more than a decade, including unlawful coordination with a political campaign and repeated self-dealing transactions.

The petition seeks restitution of funds and an order barring the directors from serving on the board of any registered company for ten years.

“Our investigation found the company’s charitable arm operated as little more than a payment account for its directors,” the regulator said in a statement.

The regulator has also referred its findings to the national tax authority and the electoral commission for further review.

#### Evidence view

Add profiles for evidence linking

Downloaded from regulator.example/press/halvorsen

The company also entered into at least five self-dealing transactions that benefited its directors, including payments to settle legal claims against a related property business and a purchase of artwork displayed at a directors’ hotel.

As described in the petition, none of the company’s expenditures were approved by its board. The investigation found the board had not met in more than a decade.

The adaptive layout from Phase 1 splits the screen, so researchers copy details straight from the document, with fewer transcription errors.

The evidence stays pinned across every tab until closed, and pops out to a second screen for multi-monitor users.

Documents are no longer buried in profiles: researchers can search for evidence by ID and open it directly.

Individuals and businesses linked to the evidence are listed with their risk type, visible from the evidence itself.

- Duplicate checking on the URL

- No manual keying of URLs

- Evidence previewed before inclusion

- Less manual PDF uploading

- Evidence added independently of a profile

- Profiles created directly from evidence

- Faster linking of one document to many profiles

#### Add evidence: create PDF

BUDAPEST – The financial regulator today announced civil proceedings against Halvorsen Trading Kft. and its directors, alleging a pattern of improper conduct spanning more than a decade.

The petition seeks restitution of funds and an order barring the directors from serving on any registered company’s board for ten years.

#### Evidence view: link or create a profile

Among those named alongside the directors is Marek Novak, a former adviser to the company’s charitable arm, who the petition says approved several of the transfers.

The regulator said its findings had been referred to the national tax authority for further review.

Adding evidence follows four clear steps, from choosing a format to adding it to the profile.

Screening the URL checks it against existing evidence and surfaces any match before the researcher continues.

The screened URL renders to a PDF preview automatically, cutting the need for manual PDF uploads.

Researchers search for a person, add them with one click, or create a new profile straight from the document.

- Evidence linked to each entry, not just the profile

- More input fields for PEP and sanctions data processing

- Editable dropdowns

#### PEP positions with evidence, and editing dropdown values

Each PEP position carries its own evidence, snippet and credibility score, for finer granularity than evidence at profile level.

Category values can be added and edited in place, so methodology changes don’t wait on an engineering release.

After the new CMS and data model launched successfully, I reused its UI components to design a new client-facing search app in a single month. Because I took a design systems approach, engineering could reuse the CMS components and re-theme them for clients.

#### Search

#### Results

Clients pick which datasets to search before running a query. A clickable Figma prototype covers this dataset selection feature.

The results reuse the CMS data table, match pills and tags from Phase 1, with a new client theme.

> “Thank you for making our life easier.”
> Lead Researcher Quote

### Before and after

How researchers’ work changed

- +44 7456 495994

- nedkeny@gmail.com

- LinkedIn [LinkedIn](https://www.linkedin.com/in/pj-kennedy/)
