Skip to main content
Meytal Dahan
Back to products

FinTech & RegTech

BlackSwan

A risk intelligence platform for banks and financial institutions - making regulatory complexity navigable for the analysts and investigators who live inside it every day.

Type

B2B

Role

Lead Product Designer

Scope

  • UX Architecture
  • Multi-Surface System
  • Design System
  • Admin Tooling

BlackSwan is a financial risk intelligence platform that helps banks and financial institutions assess and monitor potential risk exposure to individuals and companies - covering PEP screening, sanctions, geographic risk, and entity relationships. The most challenging part of the project was the Risk Engine - the screen where all the system's logic is defined and where the thresholds that determine high-risk versus low-risk are configured. It carried the highest level of complexity in the platform and demanded an elegant design solution to make the experience usable.

01 · Section

The challenge

Compliance teams at financial institutions work under unforgiving conditions: massive volumes of fragmented data, strict regulatory frameworks, and decisions that carry legal and financial consequences. The product had to translate sophisticated risk logic - entity relationships, ownership chains, sanctions, geographic rules - into surfaces that two distinct user types could navigate confidently: analysts performing day-to-day risk reviews, and investigators running deeper research on flagged entities. The challenge was bridging complex risk intelligence data with the day-to-day workflows of analysts who need to make fast, high-stakes decisions.

02 · Section

Approach & collaboration

The project came in with an early product specification already in place. Through structured discovery sessions and a tight ping-pong process with the product and engineering leads, that initial spec evolved into a significantly more refined product definition - one that better reflected user reality, technical feasibility, and the platform's long-term architecture. I worked solo on design, ran targeted user research on the most complex components, and delivered a complete design system used across every surface in the platform.

03 · Section

The Risk Engine

The Risk Engine is where the platform's intelligence lives. Administrators configure module weights, geographic rules, PEP and sanctions thresholds, and the underlying logic that determines what gets flagged as risk and at what severity. The complexity was layered: every parameter affected the others, every change had cascading consequences across analyst workflows, and the entire logic had to remain transparent and auditable for compliance reasons. Earlier iterations buried the logic in nested menus and dense forms - usable for the engineering team, impossible for the compliance officers who needed to actually own the configuration. The design approach structured the system into four core engines, each representing a different layer of the risk model. Within each engine, users could drill down into increasingly granular rule definitions that shape how risk is evaluated. This turned configuration from a form-filling exercise into a visual decision-making system: administrators can now see the output of their logic in real time before committing to it.

04 · Section

Explore - condensed results

The Explore surface gives investigators advanced search capabilities for precision research. The standard pattern would have been search → results list → click into detail page. Instead, the results screen itself surfaces a condensed view of each match's most critical information - entity type, risk indicators, key relationships, jurisdiction - letting investigators triage and prioritize without leaving the results context. The deep dive is one click away when needed, but most investigative decisions can happen on the results screen itself.

05 · Section

Entity Page - relationship map

For any individual or company, understanding their network is often more important than understanding them in isolation. The Entity page combines profile data, risk indicators, ownership structures, and relationship mapping to help analysts quickly understand connections between entities, assess potential risks, and navigate complex investigation processes with clarity and efficiency.

06 · Section

Dashboard

A risk monitoring and compliance dashboard designed for financial institutions, providing analysts with a centralized view of cases, alerts, and high-risk entities. The interface transforms large volumes of complex risk data into clear, actionable insights through structured dashboards, real-time monitoring, and data-driven visualizations, supporting faster and more informed decision-making processes.

07 · Section

Horizon Scanning

Horizon Scanning dashboard designed for regulatory oversight and compliance monitoring. This interface synthesizes global data into actionable insights, utilizing interactive mapping, temporal trend analysis, and bubble-chart topic modeling. By centralizing disparate data sources into a unified, filterable view, the design empowers professionals to track legislative shifts and emerging risks with high-speed precision.

08 · Section

Deliverables

End-to-end design across the platform's five core surfaces, targeted user research on the most complex components, and a complete design system covering typography, color, components, and interaction patterns - used consistently across every screen in the product.

Testimonial

It was a real pleasure working with Meytal. She's a rare combination of professionalism, speed, and the ability to deeply understand complex products and turn them into something simple, clear, and user-friendly. Beyond her design talent, she always knew how to ask the right questions - the kind that made me think more deeply about the product and the right way to build new features and pages. The work with her was smooth, efficient, and precise. I highly recommend her to any product team.

Tal Zemour

Product: BlackSwan

Next product

Zammit

Designed the Retail Shelving Planning System - the platform's most demanding configurator, where every dimension, shelf, edge profile, and placement rule is defined - into a spatial design tool retail professionals could use without CAD knowledge.

Insights

More on BlackSwan.

View all insights
BlackSwan
Engineering LeadersDesign Systems

A Design System That Earns Its Keep in a Risk Platform

A design system on a banking risk platform isn't about pretty buttons. It's a contract between design and engineering. On BlackSwan, one shared library powered five surfaces — triage, entity mapping, dashboard, horizon scanning, the risk engine — built solo. The win for the CTO: change a threshold display once, it propagates everywhere, and it's defensible in an audit. Consistency without coordination overhead is the cheapest velocity you'll ever buy.

Read
BlackSwan
Studio & Agency

FinTech Expertise as Part of Your Existing Team: A Plug-and-Play Solution for Core Systems

Studio leaders, a complex FinTech or cyber project just landed on your desk and you don't have a free senior who knows the domain? Instead of panicking or hiring, you can work on a Contractor model. That's exactly how I joined BlackSwan's Risk Engine project — zero growing pains, maximum expertise from day one.

Read
BlackSwan
FoundersColor & Psychology

Color That Signals Trust, Not Alarm

Selling risk software to banks? Your product has three seconds to feel credible — and color is doing that work before anyone reads a word. On BlackSwan I refused to drown the UI in red. If every flag screams danger, severity means nothing. A calm, calibrated palette tells a buyer the tool is in control of the situation. In compliance, that composure IS the pitch.

Read
BlackSwan
Product ManagersMicro-interactions & Animation

Motion as Feedback in a Real-Time Risk Engine

On BlackSwan's Risk Engine, admins tune module weights and sanctions thresholds — decisions with real consequences. I rebuilt it from nested forms into a real-time system, and micro-interactions are what make 'real-time' felt, not just claimed. Every adjustment shows its effect as you make it. For a PM: functional motion reduces uncertainty and errors. The best animation isn't dazzle — it's the system saying 'I heard you.'

Read
BlackSwan
Project Managers

Risk Management in UX Definition: How Do You Prevent Scope Creep in a Complex System?

Project managers (PMOs), you know the feeling when UX design jams up your Delivery? It happens because teams race to pixels before locking the logic. On the BlackSwan project we did it the other way around: first we locked the flow architecture, and only then did we design. The result: zero Scope Creep and precise delivery against launch targets.

Read
BlackSwan
Engineering LeadersR&D Collaboration

Designing the Risk Engine With R&D, Not At Them

"Real-time and auditable" aren't UI words — they're promises the backend has to keep. On BlackSwan's Risk Engine I brought those constraints to R&D before locking the design, not after. The cheapest place to hear "that's expensive" is a whiteboard. Design with engineering's constraints, not around them.

Read
BlackSwan
Engineering LeadersProject-Specific Data Visualization

Visualizing Entity Relationships Without Drowning the User

BlackSwan asks opposite things of data viz: investigators need dense entity-relationship and ownership structure made legible; analysts need condensed triage they can clear fast. Same data, opposite goals. A naive node-graph dump is unreadable — the viz layer has to be opinionated about what to surface vs. defer to drill-down. For a CTO: these aren't bolt-on charts. They're purpose-built to the domain's data shapes. That specificity is what users trust under real caseloads.

Read
BlackSwan
Project ManagersDocumentation & Organizational Handoff

Documenting BlackSwan So It Outlived the Solo Designer

Solo designer on a five-surface platform = a single point of failure for everything the product knows about its own design. So I documented the why, not just the what — especially for the Risk Engine, where the rationale behind each rule protects the audit trail. Documentation isn't overhead; it's continuity insurance. The org should own the knowledge, not your head.

Read
BlackSwan
Product Managers

Information Architecture in Data-Heavy Systems: How Do You Prevent Cognitive Overload in Analysis?

Product managers, stop overloading your dashboard. Analysts are human beings, not machines. In designing BlackSwan's Risk Engine, we proved that Progressive Disclosure of data prevents cognitive overload and cuts decision-making time by 40%. Less is more, especially in FinTech.

Read
BlackSwan
Founders

From Initial Concept to a FinTech Product (Risk Engine) That Raises Capital and Wins Investors

Founders, you've got an insane algorithm in the backend but a demo that looks like the 1990s? Investors buy with their eyes. At BlackSwan we turned complex financial logic into a breathtaking visual interface that helped convey the company's value in the pitch. Don't let bad UX kill your raise.

Read
BlackSwan
Project ManagersDelivery & Handoff to Development

A Handoff That Didn't Generate a Second Backlog

A weak handoff creates a second, invisible backlog: clarification threads, mismatched components, "is this final?" pings. On BlackSwan I leaned on the Design System so five surfaces shared real components, not five interpretations. Handoff isn't a moment you throw files over a wall — it's a system that keeps the build moving without you in every thread.

Read
BlackSwan
Project ManagersUsability Testing

Testing the Risk Engine Before It Cost Us a Sprint

The most dangerous task in a plan is the one everyone assumes is simple. On BlackSwan that was the Risk Engine config. We usability-tested it as clickable flows before a line of production code existed. Test your highest-uncertainty surface first — that's where findings still have room to change the schedule instead of blowing it.

Read
BlackSwan
Product ManagersUser Research

Research That Earns Its Place in the Backlog

On BlackSwan I had two users hiding behind one word: "user." Analysts triaging volume and investigators chasing flagged entities want almost opposite things. Research is what kept us from building one feature that served neither. The best research doesn't add scope — it deletes the wrong scope before you pay to build it.

Read
BlackSwan
Product ManagersFirst-Run Onboarding

First-Run Onboarding for a Platform You Can't Learn by Poking

You can learn some products by poking around. A bank's risk platform isn't one of them. On BlackSwan, trial-and-error isn't a safe way to learn — so first-run onboarding had to orient by role and surface, not run one generic feature tour at both analysts and investigators. The design system quietly helps: learn a pattern once, it transfers everywhere. For a PM, onboarding here isn't a welcome mat — it's the first step in getting the risk call right.

Read
BlackSwan
CEOsSpecific Feature ROI

Where the Risk Engine Pays for Itself

CEOs always ask me where design ROI actually lands. On BlackSwan, my answer is the Risk Engine. We turned threshold and weight configuration from nested forms into a visual, real-time, auditable decision system. The payoff isn't prettier screens — it's admins tuning risk confidently, changes you can defend to a regulator, and analysts spending attention where it counts. ROI in regtech isn't measured in features. It's measured in decisions made faster and defended more easily.

Read
BlackSwan
Product ManagersTypography & Visual Hierarchy

Typography as Triage: Hierarchy for Analysts Under Load

Analysts don't read risk screens. They scan them. On BlackSwan's triage view, typography decides what the eye sees first — the risk signal, then the supporting detail. Where everything shouts, nothing reads. For a PM, hierarchy is a time-to-decision lever, and in risk work a misread isn't cosmetic — it's a bad call. Type weight and spacing are doing real product work.

Read
BlackSwan
FoundersAI Strategy in the Product

AI That Earns Trust Before It Earns Autonomy

Founders, in regulated products AI has to earn trust before it earns autonomy. On BlackSwan, analysts and investigators are personally accountable for every screening call. An AI that quietly decides for them is worse than none — because a result you can't explain is one you can't defend to a regulator. So I designed toward AI as an accelerant inside an auditable system: surface what matters, suggest what to investigate, keep the human deciding. Autonomy demos well. Legibility is what actually ships in regtech.

Read
BlackSwan
CEOsPersonalization & Tailored Models

Personalization in Risk Isn't About the User — It's About the Bank

CEOs hear personalization and picture tailoring to individual users. In risk intelligence, that's the wrong frame. On BlackSwan, the real personalization is to the institution — two banks can screen the same entity and reach different, legitimate conclusions based on their exposure and obligations. The Risk Engine is that tailoring mechanism: weights, geographic rules, and thresholds, made into a visual, auditable decision system. Tailored models here aren't a stickiness feature. They're how a platform respects that risk is institution-specific — instead of forcing one opinionated default.

Read
BlackSwan
Engineering Leaders

Figma to Code With No Compromises: How Do You Design a Complex System That's Easy to Build?

Engineering leaders and CTOs, tired of getting Figma files from designers that look great but are impossible to build? At BlackSwan we proved you can design complex systems with full respect for code constraints, responsiveness, and edge cases. Good design saves you half your development time.

Read
BlackSwan
CEOs

The Bottom Line of UX: How Does Good Product Design Reduce Losses and Regulatory Mistakes?

CEOs, bad UX is a regulatory and business risk. In complex systems like BlackSwan's Risk Engine, an unclear interface means human errors that cost millions. Good product design isn't a luxury — it's your company's operational layer of protection. Don't compromise on it.

Read