Fraud Prevention Platform
Designing clarity into high-stakes fraud decisions
UX/UI Designer · Information Architecture · Interaction Design · Visual Design · Design Systems · Prototyping
CLIENT
Mercedes-Benz Financial Services
YEAR
2025
SERVICES
UX/UI Design · UX Research · UX Strategy
INDUSTRY
Automotive
Overview
Fraud analysts and retail employees needed to evaluate customer and account information while identifying potential risk. The challenge wasn't giving employees access to more data. They already had substantial information available.
The challenge was helping them understand what mattered, why it mattered, and what they should investigate next.
I worked across user flows, information architecture, high-fidelity UI, reusable components, and developer handoff to create a clearer and more scalable experience.
The challenge
The problem wasn't a lack of information.
It was knowing what mattered.
Fraud decisions require both speed and confidence.
Employees needed enough context to recognize unusual behavior, understand account history, evaluate potential risk, and determine the appropriate next action.
When too many data points competed for equal attention, critical information became harder—not easier—to identify.
The design challenge became:
How might we make complex information easier to evaluate without removing the context required for a responsible decision?
Approach
Designing an information system before designing screens
I mapped workflows and information requirements to understand how different pieces of customer and account data contributed to a decision.
Instead of asking only, “What needs to appear on this screen?” I considered:
What does someone need to know immediately?
What signals potential risk?
What provides supporting context?
What belongs deeper in the experience?
What action should become available next?
That analysis exposed three recurring needs.
Critical signals needed stronger hierarchy.
Decision-critical information competed visually with secondary detail.
Risk needed to be recognizable without replacing judgment.
Employees needed support identifying potentially meaningful signals while retaining access to the underlying evidence.
Different workflows shared common structures.
Many scenarios reused similar types of customer, account, risk, and historical information.
[IMAGE — IA/content grouping/workflow artifact]
Key Decisions
01 — Design hierarchy around the decision, not the database
Instead of allowing the underlying data structure to dictate the interface, I grouped information according to how employees needed to evaluate it.
Primary information supported immediate understanding. Secondary information provided context. Deeper detail remained accessible when investigation required it.
[IMAGE — hierarchy exploration / annotated UI]
02 — Make risk visible without making the interface alarmist
I introduced visual indicators and clearer states that helped employees recognize potentially important signals during scanning.
The goal wasn't to have the interface make the fraud decision for them.
It was to help employees answer:
“Where should I pay attention?”
while keeping the evidence required to make their own judgment accessible.
[IMAGE — risk indicators/states]
03 — Build reusable patterns instead of one-off screens
Because different workflows relied on similar information structures, designing every screen independently would create inconsistency and make future expansion more difficult.
I developed modular patterns for customer information, account details, history, risk indicators, and actions that could be recombined across related scenarios.
[IMAGE — component/pattern system → examples in context]
The Solution
An interface organized around understanding and action
The resulting experience established a clearer hierarchy for complex account information while maintaining access to the depth employees needed.
Reusable modules and interaction patterns also created a more consistent foundation for additional fraud workflows.
[BIG FINAL UI]
Impact
Without a defensible quantitative KPI, I would keep this qualitative and concrete:
Clearer information hierarchy
for dense customer and account data
Consistent visual language
for communicating potential risk
Reusable interaction patterns
across related workflows
Scalable UI foundations
for future product scenarios
Reflection
Sometimes reducing cognitive load doesn't mean reducing information.
Enterprise products often need to display substantial amounts of data.
This project strengthened my ability to create clarity through prioritization, hierarchy, progressive disclosure, and reusable patterns rather than simply removing complexity from the screen.