Insurance operations platform

Data-heavy legacy replacement - Led design for a global insurer’s claims platform balancing business goals with how adjusters work.

At a glance

Product
An insurance platform for Riverstone International, covering claims, policy and reinsurance for teams across the UK, US and Europe
My role
Senior Product Designer — led the claims pod; roadmapping and platform strategy; design reviews and standards across pods
Scope
Took the claims platform from discovery through launch, covering claim creation, data searches, financial tracking, error handling and workflow automations

The challenge

Riverstone International is a global run-off insurer and reinsurer. In 2024 alone it paid about $1.8bn in gross claims, yet its adjusters were still working on a years-old legacy system. Nothing sat in one place. Claim data arrived from many different sources, including brokers and other insurers, and adjusters spent hours bringing it together manually. The workflows were just as scattered. Someone creating a claim had no idea where they were in the process, any errors only appeared once they’d reached the very end, and without reliable autosave, work was often lost.

The system was used across the UK, US and Europe, but over the years each region had been patched with its own fixes and workarounds. Each country also had its own laws and business requirements, so what mattered in one often didn’t matter in another. On top of that, adjusters had years of habits built on the old system. We had to work out what could be automated, join the workflows into a clear path and give every region what it needed, without asking anyone to relearn the job from scratch.

Who it was for

Claims adjusters handling complex run-off claims across Riverstone’s offices in the UK, US and Europe.

My role

I led design for the claims pod and owned the claims experience end to end, while other designers covered policy and reinsurance.

To untangle the most complex parts of the claims process, I led a series of workshops with subject matter experts and ran brainstorming sessions on how to make each workflow simpler. We looked at every process step by step, cut it down to the fewest steps possible and removed anything redundant. Beyond regular stakeholder demos, the work went through rigorous user acceptance testing (UAT). Improvements and change requests came in throughout, and we turned them around quickly so the platform stayed true to how claims really run.

Claims journey maps, a service blueprint, a process flowchart, and a workshop wall of sticky notes.
Journey maps, flowcharts, service blueprints and workshop sessions from untangling the claims process at Riverstone International.

Keeping five pods building one product

With five pods building different parts of the same platform in parallel, a lot was happening at once, and the biggest risk was drifting apart: inconsistent patterns, varying behaviour and a platform that no longer felt like one product. So documentation became a big part of the project. We kept the design system and pattern library up to date so everyone worked to the same standard, and set up regular design reviews to keep each other on track.

Consistency was only half of it. We also looked for ways to cut development effort. When one pod built a feature, we checked whether another could reuse it, and we looked for common patterns across pods so developers could build them once. Designers shaped their work so developers could pick it up faster. I ran a standardisation forum with developers, where we compared what was built with what was designed and closed the small gaps that slipped through. We used AI to help spot discrepancies, so inconsistencies were caught early instead of reaching users. All of this meant close collaboration, both between design and development and across the pods.

The solution

Every workflow in simple steps

Instead of various overwhelming screens, we broke each workflow down into simpler steps, and all of those steps sat together in one place rather than being scattered across the system. Adjusters always knew where they were and what came next. Claim creation was one of these workflows. Each step asked only for what it needed, mandatory fields were clearly marked, and errors showed up on the field straight away rather than at the end. We also introduced automated data entry, cutting out much of the manual work.

A dashboard for the day ahead

Before, adjusters had no single view of their work. The new dashboard showed their tasks at a glance, along with recent financials and tracking, so they could see what was pending and what was urgent as soon as they logged in. Urgent claims rose to the top before they could sit unread, and handing work over when someone was out became quick and simple.

Finding data in one place

Finding information used to mean digging through screens. We built a data hub where all claim data could be seen in one place, along with one central search. Users could filter, sort and choose which columns they wanted to see, so they could get to the data they needed quickly.

The outcome

We replaced a legacy system with one platform that protected years of Riverstone data and kept the way adjusters already worked. Instead of a different patched-up version in every region, the UK, US and Europe now work on one cohesive platform, and feature flags switch on what each region needs.

For the first time, adjusters could see what was happening at every step, so they felt in control of the process instead of lost in it. Feedback showed the flows felt clearer and left more time for the actual decision, and the platform could now scale across offices and countries without each one building its own workarounds.

More projects