Case Study · Elevance Health · 2025–2026

Find Care Experience

Every extra click between a member and an appointment is a click that ends in a call center instead. Call centers are the most expensive support channel a health insurer runs. Anthem members needing to find a provider, manage an appointment, or check a claim were routed through multiple disconnected portals, each reflecting the insurer's internal plan structure rather than what a member was actually trying to do. This was a cost-structure problem wearing a UX problem's clothes.

Select Date & Time
Select Date & Time
Locations Near You
Locations Near You
Get Care Now
Get Care Now
The Problem

Every extra click between a member and an appointment is a click that ends in a call center instead.

My Role

End-to-end: research, flow architecture, high-fidelity UI, design system contribution.

The Approach

Intent-First Information Architecture

The Outcome

+29%: Task completion rate

Scope, Constraints & Reality

Design system

Built inside and contributed back to Polaris, Anthem's existing enterprise system. New patterns had to be justified as reusable across other product teams, not one-off solutions for this flow alone.

Bounded scope

Scheduling, rescheduling, cancellation, and Get Care Now. Explicitly not a rebuild of the entire member portal, inside a large regulated org where scope creep on a healthcare product means a much longer compliance and legal review cycle.

Accessibility

WCAG 2.1 AA as a component-level requirement, reviewed in Figma before handoff rather than a post-launch audit item, given a user population more likely to rely on assistive technology than the average consumer app audience.

Timeline & budget

A 16-week engagement, scoped tightly to scheduling, rescheduling, cancellation, and Get Care Now rather than the full member portal. Enough time to do the accessibility and Polaris-contribution work properly, not enough to justify expanding scope beyond what was actually broken.

The Work
01Context & Problem
Context & Problem

Members were asked to diagnose which system handled their care: 12 drop-off points in a funnel that took 8 steps just to book an appointment.

02Key Decisions
Key Decisions

Three decisions: Progressive Disclosure (care type → location → preferences), Contextual Actions (reschedule/cancel inline on card), Unified Care Pathways (single 'Get Care Now' entry point).

03Manage Appointment Flow
Manage Appointment Flow

The full appointment lifecycle in one place: five screens from Find Care landing through Select Date & Time, Confirm Booking, Cancel, and My Care Team.

04Get Care Now Flow
Get Care Now Flow

One entry, three kinds of care. Smart routing sends virtual, in-person, and urgent care requests down the right path without the member choosing a system first.

05Design System
Design System

Visual language built for clarity, trust, and accessibility: a structured colour palette and semantic context states.

Design Decisions

1

Intent-First Information Architecture

Legacy navigation mirrored the insurer's internal plan structure. The redesign organizes around what a member is actually trying to do (find care, manage benefits, view claims), validated with a 24-member card-sorting study before a single wireframe existed.

2

One Primary Action Per Screen

Legacy flows stacked four to six competing actions per screen, exactly the ambiguity that turns a simple task into a support call. Every redesigned screen has one clear primary CTA, with error recovery made explicit instead of buried in a modal.

3

Component-Level Accessibility

Every Polaris contribution shipped WCAG 2.1 AA compliant from the start. Focus management and contrast were reviewed in Figma before engineering touched it, not caught in a QA pass after the fact.

Impact

+29%
Task completion rate

Appointment management (58%→83%), claims lookup (61%→87%), and document download (71%→94%) measured over a 60-day post-launch cohort.

Support call volume

Appointment changes and claims status were top call drivers. Both saw measurable reduction in the first quarter after launch.

6
Polaris patterns adopted

Appointment card, form validation states, coverage alert, document row, inline error, and confirmation banner, adopted across 6 product teams within 6 months.

Screens7
Click to expand · ← → to navigate