Industry
Insurance
Client
Vermeg
Redesigning a 20-year-old insurance platform, one workflow at a time.
Redesigning a 20-year-old insurance platform, one workflow at a time.
Progressively modernising a mature insurance core by understanding the rules behind the workflows, redesigning the experience feature by feature, and building the reusable system behind it.
Progressively modernising a mature insurance core by understanding the rules behind the workflows, redesigning the experience feature by feature, and building the reusable system behind it.
ROLE
Senior Product Designer
DURATION
3+ years
PRODUCT
Insurance SaaS
SCOPE
UX research · Product design · Design system
01 - CONTEXT
A mature product with 20 years of insurance logic behind it.
01 - CONTEXT
A mature product with 20 years of insurance logic behind it.
The platform's logic was solid, it had two decades of insurance rules behind it. What it lacked was an interface agents wanted to use, and a system flexible enough to reskin per client without rebuilding it each time.
My work went beyond the interface. I had to understand how insurance professionals worked with policies and contracts, how business rules shaped each workflow, and how the existing product handled that complexity.
02 - THE CHALLENGE
Insurance can't be redesigned by starting with the screen.
02 - THE CHALLENGE
Insurance can't be redesigned by starting with the screen.
Every feature had rules behind it. My role was to understand what the user needed to do, what the insurance rules allowed, and how the existing product handled it, before translating that logic into interface decisions.
BUSINESS RULES
Insurance logic, dependencies, constraints and exceptions.
USER NEEDS
Tasks, information, decisions and operational context.
PRODUCT EXPERIENCE
Flows, interactions, states, validation and UI.
03 - HOW I WORKED
One workflow at a time.
One system growing alongside it.
LifeSure was not redesigned in a single pass. I worked through individual journeys, from understanding the insurance rules and existing workflows to testing new interaction models and bringing validated patterns back into the design system.
The cycle repeated feature by feature across the product, while the design system evolved alongside it.
01
🧐 Understand
Users · Product · Project goals
02
🤔 Explore
Journeys · Flows · Design patterns
03
😎 Design & Validate
UI · Prototyping · Testing · Refinement
04
🤓 Systemise
Components · Patterns · Documentation
04 - RESEARCH & DOMAIN UNDERSTANDING
Understanding the people behind the workflow.
04 - RESEARCH & DOMAIN UNDERSTANDING
Understanding the people behind the workflow.
Before redesigning individual features, I needed to understand how insurance professionals worked with LifeSure and how insurance rules shaped their daily operations.
I interviewed 16 business and technical stakeholders and used the conversations, existing workflows and collaboration with business and technical stakeholders to identify recurring needs around navigation, information hierarchy and operational tasks.
🌟 One workflow, one research cycle.
Here’s one example of how I approached research for a specific LifeSure workflow: exploring two interface directions, defining the test objectives, observing feedback and translating the findings into the next design iteration.
01 / EXPLORE
Two directions
Alternative interface proposals were prepared before committing to one interaction model.
02 / TEST
Task-based evaluation
The proposed experiences were tested around concrete tasks and objectives.
03 / OBSERVE
Feedback & critical points
Observations were grouped around usability issues and areas requiring attention.
04 / REFINE
Feed it back into design
Findings informed the next iteration of the workflow and interface.
The challenge wasn’t removing complexity.
The challenge wasn’t removing complexity.
It was making complexity easier to work with.
It was making complexity easier to work with.
05 - FROM RESEARCH TO PRODUCT
Turning insurance logic into interface decisions.
05 - FROM RESEARCH TO PRODUCT
Turning insurance logic into interface decisions.
Over three years, I translated complex insurance journeys, including subscription, claim management, and modifications into structured, high-fidelity experiences.
Complexity wasn’t something to hide. The goal was to build a clean system structured entirely around the specific tasks and decisions users needed to make daily.
01 / CREATE A THIRD PARTY
Making a long insurance form easier to navigate.
STRUCTURED CATEGORIES
INFORMATION ARCHITECTURE
INFORMATION HIERARCHY
I broke the long form into clear sections, separated the individual and company paths, and made required information easier to spot.
FROM → One long form with mixed required and optional fields.
TO → Clear categories and a focused flow that makes third-party creation easier to navigate.
02 / BENEFICIARY CLAUSES
Making coverage and clauses easier to understand.
INFORMATION HIERARCHY
INFORMATION ARCHITECTURE
DECISION SUPPORT
I turned a hidden, coverage-by-coverage interaction into a structured overview, giving insurance experts visibility into the clauses attached to each coverage.
FROM → One dropdown hiding coverage-specific clauses, making comparison difficult and forcing experts to navigate and guess.
TO → All coverages and clauses visible together, so experts can review, compare and modify them without losing context.
03 / CONFIRMATION RULES
Making complex rules easier to review and accept.
SCANNABILITY
PROGRESSIVE DISCLOSURE
DECISION SUPPORT
I made the type and criticality of each rule visible at a glance, so experts can quickly understand what they are accepting and why it matters.
04 / PRODUCT SHOWCASE
Turning the login screen into a product story.
PRODUCT STORYTELLING
BRAND PERSONALISATION
DESIGN SYSTEM
The interface can be reskinned to reflect each client's visual identity — from colours and typography to imagery and overall look and feel — while keeping the underlying product experience consistent.
CLIENTS INCLUDE : Generali · Société Générale · Suravenir · MAIF · NN Insurance Belgium · Cardif Lux Vie · BNP Paribas Cardif · AXA · Allianz · Milleis
06 - SYSTEMISE
600+
600+
Reusable components & patterns
The product redesign couldn't scale without a system.
The product redesign couldn't scale without a system.
Working feature by feature revealed the same interaction patterns across the product. Instead of solving each one from scratch, I identified reusable patterns and progressively built and stabilised a Design system and a component library alongside the redesign.
Foundations
Typography, colour, spacing, elevation and core tokens.
Components
Forms, buttons, tables, badges, navigation and inputs.
States
Default, hover, focus, error, disabled and selected states.
Documentation
Usage, behaviour, content and implementation guidance.
DESIGN SYSTEM
CASE STUDY COMING SOON
The system behind
the product. 😉
The system behind
the product. 😉
A dedicated case study exploring the foundations, reusable components, states and documentation behind the design system is coming soon.
07 - WHAT THE WORK CREATED
A stronger product experience and a foundation for continued redesign.
07 - WHAT THE WORK CREATED
A stronger product experience and a foundation for continued redesign.
01
Clearer workflows
Complex insurance operations were progressively reorganised around the tasks and decisions users needed to make.
02
Reusable language
Patterns could be reused instead of reinvented across each new workflow.
03
600+ component foundation
A shared design foundation supported consistency and continued product development.
03
Deeper domain understanding
The work required understanding the insurance rules and operational logic behind the interface.
Amenie
Let's work together
Amenie
Let's work together
Industry
Insurance
Client
Vermeg
Redesigning a 20-year-old insurance platform, one workflow at a time.
Progressively modernising a mature insurance core by understanding the rules behind the workflows, redesigning the experience feature by feature, and building the reusable system behind it.
ROLE
Senior Product Designer
DURATION
3+ years
PRODUCT
Insurance SaaS
SCOPE
UX research · Product design · Design system
01 - CONTEXT
A mature product with 20 years of insurance logic behind it.
The platform's logic was solid, it had two decades of insurance rules behind it. What it lacked was an interface agents wanted to use, and a system flexible enough to reskin per client without rebuilding it each time.
My work went beyond the interface. I had to understand how insurance professionals worked with policies and contracts, how business rules shaped each workflow, and how the existing product handled that complexity.
02 - THE CHALLENGE
Insurance can't be redesigned by starting with the screen.
Every feature had rules behind it. My role was to understand what the user needed to do, what the insurance rules allowed, and how the existing product handled it, before translating that logic into interface decisions.
BUSINESS RULES
Insurance logic, dependencies, constraints and exceptions.
USER NEEDS
Tasks, information, decisions and operational context.
PRODUCT EXPERIENCE
Flows, interactions, states, validation and UI.
03 - HOW I WORKED
One workflow at a time.
One system growing alongside it.
LifeSure was not redesigned in a single pass. I worked through individual journeys, from understanding the insurance rules and existing workflows to testing new interaction models and bringing validated patterns back into the design system.
The cycle repeated feature by feature across the product, while the design system evolved alongside it.
01
🧐 Understand
Users · Product · Project goals
02
🤔 Explore
Journeys · Flows · Design patterns
03
😎 Design & Validate
UI · Prototyping · Testing · Refinement
04
🤓 Systemise
Components · Patterns · Documentation
04 - RESEARCH & DOMAIN UNDERSTANDING
Understanding the people behind the workflow.
Before redesigning individual features, I needed to understand how insurance professionals worked with LifeSure and how insurance rules shaped their daily operations.
I interviewed 16 business and technical stakeholders and used the conversations, existing workflows and collaboration with business and technical stakeholders to identify recurring needs around navigation, information hierarchy and operational tasks.
🌟 One workflow, one research cycle.
Here’s one example of how I approached research for a specific LifeSure workflow: exploring two interface directions, defining the test objectives, observing feedback and translating the findings into the next design iteration.
01 / EXPLORE
Two directions
Alternative interface proposals were prepared before committing to one interaction model.
02 / TEST
Task-based evaluation
The proposed experiences were tested around concrete tasks and objectives.
03 / OBSERVE
Feedback & critical points
Observations were grouped around usability issues and areas requiring attention.
04 / REFINE
Feed it back into design
Findings informed the next iteration of the workflow and interface.
The challenge wasn’t removing complexity.
It was making complexity easier to work with.
05 - FROM RESEARCH TO PRODUCT
Turning insurance logic into interface decisions.
Over three years, I translated complex insurance journeys, including subscription, claim management, and modifications into structured, high-fidelity experiences.
Complexity wasn’t something to hide. The goal was to build a clean system structured entirely around the specific tasks and decisions users needed to make daily.
01 / CREATE A THIRD PARTY
Making a long insurance form easier to navigate.
STRUCTURED CATEGORIES
INFORMATION ARCHITECTURE
INFORMATION HIERARCHY
I broke the long form into clear sections, separated the individual and company paths, and made required information easier to spot.
FROM → One long form with mixed required and optional fields.
TO → Clear categories and a focused flow that makes third-party creation easier to navigate.
02 / BENEFICIARY CLAUSES
Making coverage and clauses easier to understand.
INFORMATION HIERARCHY
INFORMATION ARCHITECTURE
DECISION SUPPORT
I turned a hidden, coverage-by-coverage interaction into a structured overview, giving insurance experts visibility into the clauses attached to each coverage.
FROM → One dropdown hiding coverage-specific clauses, making comparison difficult and forcing experts to navigate and guess.
TO → All coverages and clauses visible together, so experts can review, compare and modify them without losing context.
03 / CONFIRMATION RULES
Making complex rules easier to review and accept.
SCANNABILITY
PROGRESSIVE DISCLOSURE
DECISION SUPPORT
I made the type and criticality of each rule visible at a glance, so experts can quickly understand what they are accepting and why it matters.
04 / PRODUCT SHOWCASE
Turning the login screen into a product story.
PRODUCT STORYTELLING
BRAND PERSONALISATION
DESIGN SYSTEM
The interface can be reskinned to reflect each client's visual identity — from colours and typography to imagery and overall look and feel — while keeping the underlying product experience consistent.
CLIENTS INCLUDE : Generali · Société Générale · Suravenir · MAIF · NN Insurance Belgium · Cardif Lux Vie · BNP Paribas Cardif · AXA · Allianz · Milleis
06 - SYSTEMISE
600+
Reusable components & patterns
The product redesign couldn't scale without a system.
Working feature by feature revealed the same interaction patterns across the product. Instead of solving each one from scratch, I identified reusable patterns and progressively built and stabilised a Design system and a component library alongside the redesign.
Foundations
Typography, colour, spacing, elevation and core tokens.
Components
Forms, buttons, tables, badges, navigation and inputs.
States
Default, hover, focus, error, disabled and selected states.
Documentation
Usage, behaviour, content and implementation guidance.
DESIGN SYSTEM
CASE STUDY COMING SOON
The system behind
the product. 😉
A dedicated case study exploring the foundations, reusable components, states and documentation behind the design system is coming soon.
07 - WHAT THE WORK CREATED
A stronger product experience and a foundation for continued redesign.
01
Clearer workflows
Complex insurance operations were progressively reorganised around the tasks and decisions users needed to make.
02
Reusable language
Patterns could be reused instead of reinvented across each new workflow.
03
600+ component foundation
A shared design foundation supported consistency and continued product development.
03
Deeper domain understanding
The work required understanding the insurance rules and operational logic behind the interface.
Amenie
Let's work together