Fraud Detection Dashboard — main view

Fraud Detection Dashboard

Client

Inovasi Daya Solusi

Role

UI/UX Designer & Developer

Scope

Dashboard Design, Risk Rules, User Management

Tools

Figma

Year

2026

Project Overview

Inovasi Daya Solusi needed a dedicated fraud detection dashboard built entirely from scratch. The platform needed to surface suspicious transactions, manage blocked users, and configure risk rules — all within a single, cohesive interface.

I designed the complete product end-to-end, aligning it with the visual language of the existing main dashboard to maintain consistency across the company's ecosystem while tailoring it specifically to the needs of fraud monitoring workflows.

The Problem

The primary users of this dashboard would be C-level executives — specifically the CEO and CFO. This introduced a unique design constraint: the interface had to be simple enough for non-technical users to navigate comfortably, while still being comprehensive enough to surface all the critical fraud data they needed to make decisions.

Balancing aesthetic clarity with functional depth was the core challenge. Every element had to earn its place on the screen — no unnecessary complexity, no missing information. The design needed to communicate trust and authority at a glance, without requiring a learning curve.

C-Suite

Target Audience

From Scratch

Built End-to-End

Design Process

The design process was highly iterative. Because the client had a clear but evolving vision, there was significant back-and-forth throughout the project. The dashboard went through multiple phases — each round of feedback reshaped the layout, the data being surfaced, and how information was prioritised. What started as a focused transactions view in Phase 1 evolved into a richer dashboard with trend charts, risk scores, and distribution breakdowns in Phase 2.

Adding to the complexity, the client's availability was limited — meetings were difficult to schedule and often spaced apart. This meant I had to be proactive in anticipating needs, preparing multiple directions in advance, and making the most of every feedback session to keep the project moving forward between rounds of revisions.

Client feedback documentation

Client Feedback & Documentation

* Some content has been blurred to protect company confidentiality.

The process followed a structured but flexible path:

1. Requirements Gathering Defined feature requirements with stakeholders, focusing on what C-level executives needed to see and act on daily.
2. Design Exploration Tested multiple design directions — layouts, colour systems, and data visualisation approaches — before converging on a final direction.
3. Prototyping & Iteration Built high-fidelity prototypes in Figma, iterating rapidly based on each round of client feedback.
4. Usability Testing Conducted usability testing to validate that the interface was intuitive for its specific audience — ensuring clarity without sacrificing depth.

Designing for Simplicity

A key insight from testing was that reducing visual noise was more effective than adding explanatory elements. Rather than tooltips and labels, the design relied on clear hierarchy, generous spacing, and familiar patterns to guide users naturally through the data.

Dashboard Clarity:

The dashboard needed to communicate the most critical metrics immediately — suspicious transactions, blocked users, and risk scores — without requiring users to dig through multiple views.

Risk Rules Management:

The risk rules page had to feel manageable rather than technical. Rules are presented as simple cards with clear statuses, making it easy to scan, toggle, and configure without feeling overwhelmed.

User Detail Panel:

Blocked user details needed to be accessible in context — a side panel approach was chosen so executives could review user information without losing their place in the main list.

Outcome & Reflections

The final product delivered a clean, focused interface that gave executives exactly what they needed — a clear view of fraud activity, the ability to manage risk rules, and detailed user profiles — all without unnecessary complexity.

This project reinforced a principle that is easy to overlook: simplicity is not the absence of depth — it is the result of it. Every screen went through multiple iterations to strip away what wasn't essential while preserving what was. The most effective design decisions were often about what to remove, not what to add.

Working with limited client availability also taught me the value of self-direction and preparation. By coming to each session with multiple options and clear rationale, I was able to keep the project moving forward despite scheduling constraints.

If I could revisit this project, I would advocate for more direct access to the end users earlier in the process. While the client provided great direction, first-hand observation of how the CEO and CFO interact with data tools would have sharpened the design even further.