Prescription drug plan
ActivePDP information surfaced during migration to ESI as provider. Members see plan details, formulary links, and pharmacy tools in one consistent layout.
Why Fondue matters
Enterprise health care does not scale on one-off screens. Members move between benefits, prescription drug plans, and secure enrollment. Partners need the same components engineering ships. My team modernized Fondue so designers, developers, and external partners work from one system with synchronized release.
The problem. Design output outpaced a system that was not yet partner-ready or consistently accessible at scale. Figma libraries and production code drifted apart. High-traffic member flows could not afford regression during modernization.
My role. I grew the design org to 30+ and sponsored Fondue modernization: token architecture, component governance, partner onboarding, and design–engineering rituals that keep releases aligned.
- Design + code parityTokens, components, and documentation deploy in the same release cycle. No handoff gap between Figma and production.
- Partner-friendlyExternal partners adopt the same components internal teams use. Fewer one-off implementations.
- Accessibility in governanceWCAG requirements are enforced at the component level before anything ships to members.
Foundations
Tokens are the contract between design and engineering. Fondue uses semantic naming so teams reason about intent (primary action, surface, danger) rather than raw hex values.
primary-600Actions · links
secondary-500Accents · highlights
neutral-900Headings · body
neutral-200Borders · dividers
success-600Confirmation · active
warning-500Attention · pending
danger-600Errors · critical
neutral-50Page background
Display XL · 40px
Your benefits at a glance
Display LG · 28px
Prescription drug plan details
Body LG · 18px
Review your coverage before open enrollment ends. Changes take effect January 1.
Body · 16px
Your member ID and group number appear on your insurance card. Keep this information secure.
Label · 12px uppercase
Plan status · Active
4px · space-1
8px · space-2
16px · space-4
24px · space-6
32px · space-8
8px base grid. Touch targets minimum 44px on member-facing flows.
Components
Interactive specimens below mirror Fondue component states. Each ships with accessibility review, documentation, and matching code in the same release.
Buttons
Form · 44px touch target
Your prescription drug plan information is available after you sign in securely.
Status · badges
Coverage active
Pending review
Member patterns
Fondue patterns combine components into flows members use daily: benefits summary, PDP details, and secure account tasks. These patterns ship across properties during programs like ESI PDP migration and secure member modernization.
Secure member account
VerifiedSecure enrollment and account tasks consolidated onto a single Fondue-based framework. Fewer fragmented patterns, faster iteration with governance.
Design + code parity
The goal is one release path: token change propagates to Figma libraries, documentation, and production components together. Partners onboard to the same pipeline.
Design tokens
Semantic color, type, and space definitions in a single source file.
Component library
Figma and code stay version-locked. Accessibility criteria per component.
Production deploy
Engineering and partners ship the same build. No drift between design and code.
Governance model
I established rituals so the system scales with the org, not despite it.
- Component ownershipEach component has a design and engineering owner. Changes go through review before release.
- Accessibility gateWCAG criteria are checked at the component level. No component ships without passing contrast, focus, and screen reader requirements.
- Partner onboardingExternal partners receive the same documentation and component packages internal teams use. Reduces one-off implementations.
- Contribution modelTeams propose additions through a shared intake process. Design leadership prioritizes by member impact and reuse potential.
- Critique cultureSystem changes are reviewed in cross-functional critique with product, engineering, and accessibility specialists.
Where Fondue ships
Adoption is the measure of a design system. Fondue underpins member-facing programs my team leads across Centene web properties.
Member portals
Benefits, account, and plan information for millions of members across state-specific experiences.
ESI PDP migration
Prescription drug plan information surfaced through provider transition using shared Fondue patterns.
Secure member modernization
Secure enrollment and account flows consolidated onto one Fondue-based framework.
Partner integrations
External partners adopt Fondue components for consistent member experience outside core properties.
For the full leadership story including team scale and program delivery, see the Centene case study. For how I extend system discipline into agentic design ops, see Agentic design ops.