Cigna Design System — Enterprise Healthcare

Three Organisations.

One Platform

35% Faster Development

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.

View Design Components

Read Our Story ->

#0075C9

#004E87

#E8F4FD

#D32F2F

#FFEBEE

#4CAF50

#333333

#666666

#9E9E9E

#E0E0E0

#F5F5F5

#FFFFFF

Dependents

Deductible met

$750 / $1,500

Enroll in plan

View benefits

Cancel this claim?

Claim #CLM-2026-04821 will be withdrawn. Reimbursement will not be processed.

Cancel claim

Keep

Medical

Dental

Vision

Your Member ID is the 11-digit number printed on the front of your insurance card.

I am the subscriber

I authorize release of PHI under HIPAA

Claim approved

Prior authorization pending

Out-of-network denied

Paperless EOB delivery

HIPAA two-factor auth

Claim #CLM-2026-04821 submitted

EOB will be available within 7–10 business days.

Date of service

06 / 13 / 2026

June 2026

Taylor Smith · Subscriber

Member ID: U•••••42891 · PPO Plan

Claim updates

Coverage & benefits

Find a provider

Sign out

01 - Context

System is well established with real data and real users.

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.

🔒 UI components and data are limited 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

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.

Alignment

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.

Design + Build

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.

Integration

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.

05 — Design System / Components

What I actually built.

Component categories.

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

Colors

Typography

Buttons

Forms

Spacing

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

Building a Design System isn't the hard part. Building one that three teams, with three different codebases and opinions, will actually use consistently? That's the design problem.

06 — Impact

Three months later,
the numbers told their own story.

35%

Faster Development

Reduced dev time through reusable components

20+

Components Built

React & JS, aligned to healthcare design system

3 Orgs Aligned

Cigna, Munich Re, Deloitte.
one source of truth

07 — Learnings

What this project
changed about how I work.

01 A component library is really a trust contract.

The component library wasn't just about efficiency. it was a shared vocabulary that let three organizations talk about UI without talking past each other. A reusable button isn't just a button; it's a contract.

02 The best design skill I have is knowing when to stop designing.

Cigna spoke in business outcomes. Munich Re spoke in platform constraints. Deloitte spoke in delivery timelines. The work was understanding all three dialects fluently enough to satisfy all three simultaneously.

03 Constraints aren't blockers. They're the brief.

Adding features to a live product isn't the same as building new ones. You don't get to change the furniture. you work with what's there. That constraint forced a level of design discipline I now actively seek out.

"The most underrated UX skill isn't craft, it's making everyone in the room feel like the design outcome was also their idea. That's how you actually ship things in enterprise."

Cigna Design System — Enterprise Healthcare

Three Organisations.

Three Organisations.

Three Organisations.

One Platform

One Platform

One Platform

35% Faster Development

35% Faster Development

35% Faster Development

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.

View Design Components

Read Our Story ->

I was the personwho spoke everyone'slanguage.

UX Engineer

UX Design

Design Systems

Javascript

React

Healthcare Platform

Cross Functional Collaboration

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

So I started by listeningbefore 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.

What I actually built.

What I actually built.

Component categories.

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

Building a Design System isn't the hard part. Building one that three teams, with three different codebases and opinions, will actually use consistently? That's the design problem.

Three months later,the numbers told their own story.

Three months later,the numbers told their own story.

35%

Faster Development

Reduced dev time through reusable components

20+

Components Built

React & JS, aligned to healthcare design system

3

Orgs Aligned

Cigna, Munich Re, Deloitte. one source of truth

What this projectchanged about how I work.

01

A component library is really a trust contract.

The component library wasn't just about efficiency. it was a shared vocabulary that let three organizations talk about UI without talking past each other. A reusable button isn't just a button; it's a contract.

02

The best design skill I have is knowing when to stop designing.

Cigna spoke in business outcomes. Munich Re spoke in platform constraints. Deloitte spoke in delivery timelines. The work was understanding all three dialects fluently enough to satisfy all three simultaneously.

03

Constraints aren't blockers. They're the brief.

Adding features to a live product isn't the same as building new ones. You don't get to change the furniture. you work with what's there. That constraint forced a level of design discipline I now actively seek out.

"The most underrated UX skill isn't craft, it's making everyone in the room feel like the design outcome was also their idea. That's how you actually ship things in enterprise."

Project Slide Deck

Full case study presentation — process, decisions, and outcomes in detail.

Download The Deck from Here!

View The Deck Here!

I was the person
who spoke everyone's
language.

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

So I started by listening
before I drew anything.

Three months later,
the numbers told their own story.

Three months later,
the numbers told their own story.

Cigna, Munich Re, Deloitte.
one source of truth

What this project
changed about how I work.