Danske Bank · 2025

FX Trading

Automation

Designing automated liquidity management for business customers — enabling configurable rules for currency top-ups, sweeps, and swaps, eliminating constant manual intervention.

Role
Lead Product Designer
Company
Danske Bank · Copenhagen
Scope
End-to-end design · Research
Status
Live — actively iterated
DanskeFX Auto — Rule Management Create Rule — Rule Settings
80%
Reduction in manual intervention
DaysHours
Onboarding time reduction
Real-time
Cash positioning now available
01

The problem

Business customers managing multiple currency accounts at Danske Bank faced a heavy operational burden. Without automated tools, treasurers and finance teams had to manually monitor and move funds between accounts to maintain their desired liquidity levels.

This created two costly outcomes: cash sitting idle in accounts without generating interest, and accounts occasionally tipping negative — triggering bank charges. The mental overhead of continuous monitoring was significant, particularly for businesses operating across multiple currencies.

The problem surfaced through sales feedback, direct customer research, and competitive analysis — with several competitors beginning to introduce automated liquidity tools, signalling clear market expectations forming.

02

Who I designed for

The user base varied significantly depending on company size — from dedicated treasury professionals in large organisations to business owners managing everything themselves. This range of financial sophistication was a central design constraint throughout.

User type #1
Treasurer
Expert in FX and liquidity. Needs granular control, complex rule configuration, and confidence in the automation logic.
User type #2
Accountant
Operationally focused. Needs clarity on what rules are doing and easy auditability of past actions.
User type #3
Business owner
Less financially specialised. Needs simple setup, plain language, and trust that the system is working.
03

How I approached it

I joined the project mid-discovery, with some initial research already completed. I continued the work — conducting customer interviews and presenting early mockups to validate whether the proposed solution would actually address the pain points identified.

Working within Danske Bank's Sapphire design system, I used existing components where possible, but several patterns needed extending to accommodate rule logic, scheduling, and error states.

01
Discovery
Continued customer interviews and concept testing with early mockups to validate direction and uncover gaps in the problem definition.
02
Design
End-to-end flow within Sapphire DS. Iterated heavily on edge cases as they surfaced during development — errors, conflicts, and edge conditions.
03
Delivery
Usability studies to validate comprehension and confidence. Close collaboration with engineering throughout the build.
04

The hard part

The fundamental tension: making highly complex financial automation feel simple and trustworthy across a user base with very different levels of financial expertise.

Automated rules involve conditional logic, thresholds, schedules, and currency-specific behaviour. Getting that wrong — or making it feel opaque — would undermine customer confidence in a domain where trust is everything.

A second major challenge emerged during build: we discovered many edge cases and error scenarios that hadn't been anticipated in the initial designs. Each required careful thought on how to communicate failures and help users recover gracefully.

"The challenge wasn't building the feature — it was making automated financial decisions feel understandable and trustworthy to someone who might not be a treasury expert."

05 — Solution

The final product

The solution is a rule-based automation tool that lets customers set up configurable rules for top-ups, sweeps, and swaps. A clear step-by-step structure guides users through defining the automation logic, scheduling, and global settings — with progressive disclosure to keep the interface approachable.

06

What I learned

Edge Cases Are the Product
The happy path was straightforward. The real design work was in anticipating and handling the dozens of scenarios that diverged from it — errors, edge conditions, conflicting rules.
Trust Is Built Through Transparency
Customers needed to understand what the automation was doing and why. Plain language and visible rule logic were as important as the interaction design.
Design System Constraints Are Opportunities
Working within Sapphire pushed us to solve problems in ways that would scale. Extending components rather than creating new ones meant our work could benefit other teams.
Financial Complexity Need Not Feel Complex
Progressive disclosure, plain language, and a clear step-by-step structure let the same interface serve both treasury experts and business owners.
Next case study
FX Sales Dashboard