Designing a clearer investigation workflow for complex AML operations.
A self-initiated portfolio project exploring how complex AML investigation workflows could be made easier to understand and navigate.
AML investigation involves alerts, transactions, risk signals, entity relationships, case history and decisions. For this concept, I explored how this information could be organised around the decisions users need to make, rather than simply presenting more data.
“How might I help users move from alert → context → investigation → decision with less cognitive load?”
| Constraint | Design response |
|---|---|
| Dense information | Clear hierarchy |
| Multiple user roles | Role-specific workflows |
| Complex relationships | Focused visualisation |
| High-stakes decisions | Clear states and explanations |
| Desktop-first | Large-screen workflow |
| 3-week timeline | Focused product scope |
| User | Primary responsibility | Main need |
|---|---|---|
| L1 Analyst | Triage alerts | Speed and clarity |
| L2 Investigator | Investigate complex cases | Context and relationships |
| Compliance Manager | Monitor operations | Visibility and control |
Design implication — the same information isn't equally important to every user. So I designed the experience around role + workflow stage, rather than creating one dashboard for everyone.
Alongside the investigation flow: Manager Dashboard → Audit Trail
This became the core scope of Nexus — mapped out end-to-end in FigJam before any screen was drawn.
Helping analysts decide what needs attention first. The Alert Queue is designed around the first decision an analyst needs to make:
Which alert needs my attention?
The primary view focuses on: Severity · Entity · Alert type · Risk score · Amount · Status. Additional information can be accessed when required.
This is the core investigation experience. The layout brings together case context, investigation and decision-making in one workspace.
| Case context | Investigation | Decision |
|---|---|---|
| Case details | Transaction history | Escalate to L2 |
| Timeline | Risk flags | File SAR |
| SLA | Related cases | Dismiss |
| Assigned analyst | Notes & documents | Set priority |
The Alert Queue surfaces the risk score alongside severity, alert type, entity and flagged amount, giving analysts an initial signal for prioritisation.
Make risk visible at the point of triage.
Helping investigators see relationships without creating more noise. The network represents relationships between entities and transactions, using visual hierarchy to communicate node size, risk colour, connection weight, and transaction information.
From individual investigations to team-level visibility. The manager experience focuses on: Workload · SLA risk · Team performance · Trends.
The analyst asks "What should I investigate?" The manager asks "Where does my team need attention?" So the dashboard is designed around exceptions, workload, and operational visibility rather than individual transaction details.
Making activity easier to review. The Audit Trail provides visibility into who → did what → when → on which case. The concept also explores surfacing unusual activity patterns so important events don't remain buried in a large activity log.
The interface uses semantic colours to communicate meaning. The same visual language is carried across risk, severity, SLA, and status states.
Colour communicates meaning, not decoration.
The intention was to explore how repetitive actions could become more efficient for experienced users.
This is a design exploration, not a validated production feature.I used Figma AI Make during early exploration to generate layout directions and accelerate initial scaffolding.
| AI helped with | I owned |
|---|---|
| Initial layouts | Information hierarchy |
| Dashboard exploration | Workflow structure |
| UI scaffolding | Risk and severity system |
| Faster iteration | Interaction decisions |
AI helped me get to a starting point faster. The product decisions remained mine.
It's about helping users understand what matters now. That became the central idea behind Nexus.
The project pushed me to think beyond individual screens and ask:
Who is using this?
What are they trying to decide?
What information do they need right now?
What can wait until later?
The result is a concept built around one simple principle:
Turn complex information into confident decisions.
| Type | Independent portfolio concept |
| Role | UX/UI & Product Designer |
| Timeline | 3 weeks |
| Platform | Desktop |
| Domain | AML · Financial Crime · B2B SaaS |
| Tools | Figma · FigJam · Figma AI Make |