From Fragmentation to Scale: Unified 15+ insurance product lines into a scalable product system

From Fragmentation to Scale: Unified 15+ insurance product lines into a scalable product system

Consolidating fragmented user journeys, aligning stakeholders, and creating reusable foundations for future insurance products.

Context

What started as independent product decisions became a fragmented ecosystem

As Monee expanded its insurance offerings, products were developed independently over time to meet immediate business needs. While each product functioned adequately on its own, the ecosystem had become increasingly fragmented. Users encountered different interaction patterns across products. Designers repeatedly solved similar problems. Engineers rebuilt variations of the same components.

As new features were introduced, maintaining consistency became increasingly difficult. The challenge was no longer about improving individual screens. It was about creating a scalable system capable of supporting future growth.

Acted as the de facto driver of design system consolidation across insurance products, I led the design effort to audit existing experiences, identify reusable patterns, align stakeholders, and define a system that could scale across all insurance products.

As Monee expanded its insurance offerings, products were developed independently over time to meet immediate business needs. While each product functioned adequately on its own, the ecosystem had become increasingly fragmented. Users encountered different interaction patterns across products. Designers repeatedly solved similar problems. Engineers rebuilt variations of the same components.

As new features were introduced, maintaining consistency became increasingly difficult. The challenge was no longer about improving individual screens. It was about creating a scalable system capable of supporting future growth.

Acted as the de facto driver of design system consolidation across insurance products, I led the design effort to audit existing experiences, identify reusable patterns, align stakeholders, and define a system that could scale across all insurance products.

Role

Senior Product designer

Team

  • 1 Senior Product Designer

  • Product Managers

  • Frontend Engineers

Timeline

4-6 months (ongoing)

🌟Highlights

Unified design system

Unified design system

from fragmented patterns

from fragmented patterns

150+

150+

screens migrated to reusable components

screens migrated to reusable components

-40%

-40%

design-development handoff friction

design-development handoff friction

▲Experience Consistency

▲Experience Consistency

across insurance products

across insurance products

✅Scalable foundation

✅Scalable foundation

for future product expansion

for future product expansion

The Problem

Fragmentation was slowing both user experience and product scalability

Repeated design and engineering effort

Fragmented user experiences across products

Slow feature development due to lack of reusable patterns

Increasing maintenance cost

Misalignment between product, design, and engineering

Understand The Ecosystem

I mapped the system before attempting to redesign it

Before proposing solutions, I needed to understand the true extent of fragmentation.

Cross Product Audit

Cross Product Audit

  • Purchase flows

  • Claims journeys

  • Policy servicing experiences

  • Shared interaction patterns

  • Component usage

👀 What I Found 👀

15+

insurance product lines

insurance product lines

150+

legacy screens

legacy screens

Dozens of duplicated

models solving identical problems

models solving identical problems

Inconsistent

spacing & layout structures

spacing & layout structures

Different approaches

to validate & error handling

to validate & error handling

High operational costs

of design, development & maintenance

of design, development & maintenance

Before the Revamp

Fragmented and inconsistent across products

The painpoints?

The painpoints?

Different form patterns

Inconsistent card/summary layouts

Varying quotation attainment behaviour

Approach

The solution wasn't better screens—it was a better system

The solution wasn't better screens—it was a better system

Rather than redesigning products individually, I approached the problem as a systems challenge. I focused on three areas:

Rather than redesigning products individually, I approached the problem as a systems challenge. I focused on three areas:

Standardize Shared Patterns

Standardize Shared Patterns

Identify common interactions appearing across products and standardise variations into single pattern.


Examples:

  • Form sections

  • Selection modules

  • Information summaries

  • Confirmation patterns

  • Error handling

Create Reusable Building Blocks

Create Reusable Building Blocks

Transform recurring patterns into flexible components that could support different insurance products without requiring custom redesigns.

Align Design and Engineering

Align Design and Engineering

Work closely with frontend teams to ensure component definitions were practical, scalable, and implementable.

The goal was not simply visual consistency.

The goal was shared ownership and long-term sustainability.

Key Decisions

The challenge was balancing standardisation with flexibility

The challenge was balancing standardisation with flexibility

Flexibility vs Standardisation

CHALLENGE

Each product had unique requirements.

Each product had unique requirements.

Over-standardization could restrict product teams.

Over-standardization could restrict product teams.

DECISION

Standardize core interaction patterns while allowing controlled flexibility for product-specific edge cases.

Standardize core interaction patterns while allowing controlled flexibility for product-specific edge cases.

This created consistency without sacrificing business needs.

This created consistency without sacrificing business needs.

Incremental Migration vs Big-Bang Replacement

Incremental Migration vs

Big-Bang Replacement

CHALLENGE

Replacing all screens simultaneously would introduce significant delivery risk.

Replacing all screens simultaneously would introduce significant delivery risk.

DECISION

Adopt a phased migration strategy.

Adopt a phased migration strategy.

Teams could continue delivering features while gradually adopting the new system.

This reduced disruption and accelerated adoption.

Teams could continue delivering features while gradually adopting the new system.

This reduced disruption and accelerated adoption.

Design-owned vs Shared Ownership

CHALLENGE

Systems often fail when treated as design artifacts only.

Systems often fail when treated as design artifacts only.

DECISION

Position the system as a shared product between design and engineering.

Position the system as a shared product between design and engineering.

Shared ownership increased implementation quality and long-term adoption.

Shared ownership increased implementation quality and long-term adoption.

Outcome

From fragmented experiences to a scalable design foundation

From fragmented experiences to a scalable design foundation

What this enabled:

What this enabled:

Team collaborate on one system

Team collaborate on one system

New products plug into an existing foundation

New products plug into an existing foundation

Governance and quality built into the system

Governance and quality built into the system

Data consistency for better insights

Data consistency for better insights

Better experience for our customers

Better experience for our customers

Impacts & Results

The impact extended far beyond visual consistency

The impact extended far beyond visual consistency

🙆🏻‍♀️

User Impact

User Impact

✅ More predictable experiences across products
✅ Reduced cognitive load
✅ Improved interaction consistency

🎨

Design Impact

Design Impact

✅ Faster workflow creation
✅ Reduced duplication of effort
✅ Easier maintenance of future products

⚙️

Engineering Impact

Engineering Impact

✅ Greater component reuse
✅ Reduced implementation effort
✅ Improved scalability

💼

Business Impact

Business Impact

✅ Faster product iteration
✅ Stronger foundation for future insurance offerings
✅ Reduced long-term design debt

Unified design system

from fragmented patterns

from fragmented patterns

150+

screens migrated to reusable components

screens migrated to reusable components

-40%

design-development handoff friction

design-development handoff friction

▲Experience Consistency

across insurance products

across insurance products

✅Scalable foundation

for future product expansion

for future product expansion

Reflection

Scaling products requires scaling systems, teams, and thinking

This project reinforced that scaling digital products requires more than consistent interfaces.

The most valuable outcome was not the component library itself, but the shared system thinking it introduced across design and engineering teams.

By treating the challenge as an ecosystem problem rather than a UI problem, we created a foundation that supports both current products and future growth.

Next Project

Next Project

Empowering Advertiser with a Self-Serve Media Buying Platform

Empowering Advertiser with a Self-Serve Media Buying Platform

Contact Me

Contact Me

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