Enterprise / B2B 2025

ClaiRe

A Claim Management System for Schaeffler

Role UX Designer
Company Schaeffler
Type Enterprise Web Application

The Problem: Centralizing Global Operations

ClaiRe is an enterprise web application designed to replace fragmented spreadsheet-based workflows with a centralized, role-based platform for handling both supplier-side and customer-side claims.

Before ClaiRe

The system suffered from three main issues that hindered operational efficiency across global business units.

01

Fragmented Data

Disconnected spreadsheets and emails caused data loss, version conflicts, and communication delays across regional teams.

02

Zero Visibility

No real-time insight into total claim volume, financial exposure, or negotiation status across different regional business units.

03

Approval Bottlenecks

Complex multi-stakeholder approval workflows lacked a persistent audit trail or mandate verification system.

User Personas & Context

The system was designed for high-mandate users across Europe, Asia, and the Americas.

Claim Owner

Initiates and manages claims through complex negotiation stages.

Key Requirements

  • Efficient data entry workflows
  • Consistent status context
  • Clear stage progression visibility

Reviewer & Manager

Approves stage progressions and monitors financial mandates.

Key Requirements

  • High-level overviews
  • Quick access to audit trails
  • Multi-currency support
  • Legal entity tracking
  • Mandate threshold visibility

UX Process & Research

Card Sorting & Design Thinking

An open card sorting exercise with 12 participants was conducted to see how users naturally group claim-related information.

Key Finding 1

Financials Must Be Separate

Financials must be separate from claim metadata. This led to a dedicated Financials tab in the system.

Key Finding 2

Locations in General Info

Participants consistently grouped "Affected Locations" and "Entities" under General Information rather than a separate logistics tab.

Key Finding 3

Audit Trail is Lowest Priority

It was consistently sorted last, confirming it should sit at the bottom of the navigation hierarchy.

The 5-Phase UX Process

1

Empathize

User interviews, shadowing, workshops

2

Define

Persona synthesis, pain point mapping

3

Ideate

Card sorting, wireframe sprints

4

Prototype

Figma flows, hi-fi stage production

5

Test

Usability testing, iterative updates

Information Architecture

The navigation was designed around three user goals: creating a claim, managing its lifecycle, and reviewing its history.

A shallow, flat hierarchy was preferred over deep nesting to reduce cognitive load.

Claims Overview (Home)

  • Custom table (filtered/sortable)
  • Global KPI tiles
  • "Create New Claim" button

Single Claim View

Organized into tabs:

General Information Claim Team & Collaboration Related Claims Financials Closure Audit Trail

Core Design Decisions

Accordion Form Architecture

Collapses completed sections to reduce cognitive load during complex, multi-step data entry sessions.

Gated Action Stepper

Gives users persistent progress context and prevents premature workflow advancement until stage gates are met.

Financial Mandate Visibility

Thresholds like Walkaway and Target values are shown point-blank so negotiators never exceed approved mandates.

Project Impact Metrics

1,250+
Claims Managed in 2025
IL1–IL5
Standardized Workflow Stages

Claim Evaluation → Assess Claim & Define Strategy → Negotiate & Reach Agreement → Close Process

16
Master Data Modules Implemented

Interested in Learning More?

This project is covered under NDA. I'd be happy to walk you through the detailed design decisions, user flows, and prototypes in a personal meeting.

Schedule a Portfolio Review