CASE STUDY · 01
Redesigning the corporate banking workspace so treasury teams move money in seconds, not screens.
Treasury teams at large corporates spend most of their day toggling between a dozen separate screens — payments, statements, reconciliation, approvals — each living in its own silo.
A quick audit of three customer teams turned up the same three pain points:
The cost wasn't just lost minutes — it was lost trust. Every extra screen made teams second-guess what they'd already done.
We started with eight one-on-ones with treasury heads across four cities. The brief was simple: walk us through your last bad day at work, screen by screen.
Three patterns emerged:
From these, the design north-star became: one workspace, three jobs, never more than two clicks away.
We rebuilt the dashboard around three persistent panels — Position, Pipeline, Pending — that stay docked regardless of where the user navigates. Every action (initiate, approve, query) opens as a side-sheet over the dashboard rather than a full route change, so context is never lost.
A new event timeline replaces the old audit log. Instead of a 40-column table, every transaction now reads as a human-language story: who did what, when, with which counter-signature.
The biggest behavioural shift: makers and checkers started sitting at the same screen. The WhatsApp tango quietly disappeared.
As of early 2026, the redesigned flows are in active handoff and pilot rollout. Within the initial stakeholder review cohort:
*Pilot-cohort and moderated-testing figures. Full production metrics pending broader rollout.
The hardest constraint wasn't the design — it was the data model. Three of the legacy systems behind the screens couldn't be touched in this phase, which meant the new front-end had to gracefully reconcile inconsistent fields, partial responses, and the occasional silent failure.
Building a "trust layer" around unreliable plumbing became its own design problem: how do you show a number you're not sure about, in a product where being unsure is unacceptable? The answer ended up being a quiet badge on the affected fields plus a one-click "reconfirm" — small UI, big behaviour change.
Bring engineering into the user interviews earlier. We caught a few "this is technically impossible" walls only at the prototype stage, which forced two redesigns. The shape of the answer would have been the same, but we'd have arrived a month sooner.
Enterprise design is rarely about a clever new screen. It's about removing the quiet daily friction nobody complains about because they've stopped noticing it.
The biggest wins on this project came from things that look invisible in a portfolio shot — a panel that stays put, a phrase that reads like a sentence, a confirmation that doesn't lie.
I joined as design lead on an active, mid-flight revamp — inherited incomplete documentation and led design across all remaining drops.
My scope included:
← BACK
All projects
NEXT CASE →
Altera Institute
If you have a banking, workflow or fintech problem that doesn't fit in a tidy bucket, I'd love to hear about it.
© Saraswati — Designed with care
