Enterprise Design System: Insurance ecosystem

Context

I led end-to-end delivery of a multi-brand design system for a large insurance ecosystem, with claims reporting as the primary use case. The system had to support two brands, desktop and mobile, and complex internal workflows built around forms.

This design system underpins the Neuron platform described in the Neuron case study, supporting two brands across the insurance ecosystem.

The design system was built retrospectively while teams were already shipping. The core challenge was introducing structure and consistency without slowing active delivery.

Role and scope

As Senior Product Designer, I owned delivery decisions across variable architecture, form patterns, component composition, and responsive variants. I worked directly with engineering and analysts to keep design decisions implementable in production conditions.

I focused on reducing ambiguity in handoff and minimizing rework, while building a system teams could scale over time.

Delivery approach

Instead of trying to build everything at once, I prioritized claims reporting flows first and delivered reusable patterns around field states, validation behavior, error handling, and review steps.

This approach improved immediate delivery outcomes while creating foundations that could be reused by other internal workflows.

System architecture

I separated Core and Theme at the variable level. Core held stable structural rules (spacing, sizing, layout behavior), while Theme handled brand-specific visual semantics.

This kept behavior and structure shared across both brands, while allowing visual differences without duplicating components.

Responsive and component strategy

I treated desktop and mobile as distinct interaction contexts, not simple scale-down states. Components used explicit variants such as `mobile`, `desktop`, `inline`, and `stacked` to reduce implementation ambiguity.

The system covered foundations and reusable components for form-heavy workflows, including InputField, Select, Textarea, Datepicker, Checkbox, Radio, FileUpload, Label, Modal, Container, TileGroup, Alert, Card, and AccordionGroup.

Execution model

I ran iterative working sessions with design and engineering to align constraints early, clarify behavior before handoff, and keep delivery pace stable.

The operating principle was practical: ship clear patterns teams can implement immediately, then scale the system through repeatable governance.

Outcome

The rollout delivered measurable impact: 15-20% faster delivery, 40-50% reduction in UI inconsistency/rework, and migration of 4 out of 5 modules to the new system.

Beyond component quality, the key result was a delivery-ready operating model teams could use consistently across brands and platforms.