Case Study — Enterprise Healthcare UX

Three Organisations.

Three Organisations.

Three Organisations.

One Platform

One Platform

One Platform

Zero Regressions

Zero Regressions

Zero Regressions

How I helped Cigna, Munich Re, and Deloitte speak the same design language and shipped new features into a live healthcare system without breaking a thing.

Cigna X Deloitte

Mednext — Munich Re HealthTech

UX Designer + Engineer

React · JavaScript

35% faster development

View Design Components

Read Our Story ->

01 - Context

01 - Context

System is well established with real data and real users.

System is well established with real data and real users.

3

3

Organisations. One Shared Product

Organisations. One Shared Product

Cigna needed new features inside Mednext, Munich Re HealthTech's existing platform, delivered through Deloitte. Three organizations, three sets of priorities, one live healthcare product that couldn't break. I sat at the intersection of all three, translating between what each needed and what was actually possible.

Cigna needed new features inside Mednext, Munich Re HealthTech's existing platform, delivered through Deloitte. Three organizations, three sets of priorities, one live healthcare product that couldn't break. I sat at the intersection of all three, translating between what each needed and what was actually possible.

🔒 UI components abstracted for NDA compliance

02 - My Role

I was the person
who spoke everyone's
language.

My title was UX Engineer, which in practice meant sketching a component in Figma in the morning and shipping it in React by afternoon. That dual fluency mattered: when engineers pushed back, I could engage with the actual constraints; when product asked why something felt off, I could trace it to a specific component and fix it at the source. I sat at the bridge between three organizations, and that bridge had to hold weight in both directions.

UX Engineer

UX Design

Design Systems

Javascript

React

Healthcare Platform

Cross Functional Collaboration

03 - Design System

The real deliverable wasn't features.
It was trust.

20+

Reusable components. One source of truth.

Design systems live or die by adoption. My approach was to build components so well-documented, well-named, and precisely scoped that the path of least resistance was also the path of consistency. The only way to keep three teams from diverging into three different products.

Want to see exactly what I built? The full component breakdown, contributions, and prototypes are further down.

See the Components

04 - Process

So I started by listening
before I drew anything.

Discovery

Discovery

First, I mapped what already existed.

First, I mapped what already existed.

Before designing a single new component, I mapped the existing Mednext design system. What patterns were already established? Where were the gaps? Understanding the existing system deeply was the only way to add to it without breaking it.

Before designing a single new component, I mapped the existing Mednext design system. What patterns were already established? Where were the gaps? Understanding the existing system deeply was the only way to add to it without breaking it.

Alignment

Alignment

Then I got everyone in the same room.

Then I got everyone in the same room.

The hardest design problem wasn't the UI. it was alignment. I facilitated working sessions between all three teams to surface conflicts early and establish shared principles before any code was written.

The hardest design problem wasn't the UI. it was alignment. I facilitated working sessions between all three teams to surface conflicts early and establish shared principles before any code was written.

Design + Build

Design + Build

Then I built things that could be used forever.

Then I built things that could be used forever.

Rather than designing features one-off, I built a library of 20+ reusable React and JavaScript components aligned with the healthcare design system. Each was composable. engineers assembled new screens without reinventing UX patterns from scratch.

Rather than designing features one-off, I built a library of 20+ reusable React and JavaScript components aligned with the healthcare design system. Each was composable. engineers assembled new screens without reinventing UX patterns from scratch.

Integration

Integration

And we shipped, without breaking a thing.

And we shipped, without breaking a thing.

Feature integration into an active healthcare platform requires discipline. I worked closely with QA and engineering to ensure new components fit within existing constraints. nothing in production broke as a result of what we added. At launch: zero regression issues.

Feature integration into an active healthcare platform requires discipline. I worked closely with QA and engineering to ensure new components fit within existing constraints. nothing in production broke as a result of what we added. At launch: zero regression issues.

05 — Design System / Components

What I actually built.

My Specific Contributions

My Specific Contributions

01

01

Audited the existing Mednext component library to identify gaps between platform capabilities and Cigna's new feature requirements before writing a line of code.

Audited the existing Mednext component library to identify gaps between platform capabilities and Cigna's new feature requirements before writing a line of code.

02

02

Architected 20+ React and JavaScript components from scratch, aligned with healthcare design tokens and Mednext's visual language.

Architected 20+ React and JavaScript components from scratch, aligned with healthcare design tokens and Mednext's visual language.

03

03

Created a block design framework and cross-trained the broader team. designers and developers alike. so components were used correctly across all three organizations.

Created a block design framework and cross-trained the broader team. designers and developers alike. so components were used correctly across all three organizations.

04

04

Documented component behavior, states, and edge cases to reduce ambiguity for developers working across three codebases with three different deadlines.

Documented component behavior, states, and edge cases to reduce ambiguity for developers working across three codebases with three different deadlines.

05

05

Established design-to-engineering handoff conventions that reduced back-and-forth review cycles and accelerated iteration velocity by 35%.

Established design-to-engineering handoff conventions that reduced back-and-forth review cycles and accelerated iteration velocity by 35%.

06

06

Established design-to-engineering handoff conventions that reduced back-and-forth review cycles and accelerated iteration velocity by 35%.

Established design-to-engineering handoff conventions that reduced back-and-forth review cycles and accelerated iteration velocity by 35%.

Component categories.

A sample of the component types built. abstracted for NDA compliance, representative of the actual scope.

Colors

Typography

Buttons

Forms

Components

Spacing

Auth

Primary Blue

#0075C9

CTA buttons, links

Error Red

#D32F2F

Validation errors

Disabled Gray

#9E9E9E

Disabled buttons

Dark Blue

#004E87

Hover state, logo

Error Background

#FFEBEE

Error input highlight

Border Gray

#E0E0E0

Input borders, dividers

Light Blue Tint

#E8F4FD

Page background, info cards

Text Primary

#333333

Headings, body text

Success Green

#4CAF50

Logo accent, success

White

#FFFFFF

Card surfaces, inputs

Text Secondary

#666666

Labels, helper text

Surface Gray

#F5F5F5

Background sections

Measurable Impact

28%

Reduced Integration Regressions

+40%

Development Speed

50+

Reusable Components

5

Teams

60%

Time Saved

Key Learnings

Key Learnings

Key Learnings

Trust Through Transparency

Trust Through Transparency

Making design decisions visible and involving all teams early built unprecedented trust and buy-in across organizations.

Making design decisions visible and involving all teams early built unprecedented trust and buy-in across organizations.

Scale Through Systems

Scale Through Systems

A robust component library isn't just about efficiency, it's about creating a shared language that scales with your organization.

A robust component library isn't just about efficiency, it's about creating a shared language that scales with your organization.

Measure Collaboration

Measure Collaboration

Tracking component adoption, reuse rates, and team satisfaction gave us clear signals that our approach was working.

Tracking component adoption, reuse rates, and team satisfaction gave us clear signals that our approach was working.

Create a free website with Framer, the website builder loved by startups, designers and agencies.