Meridian — Case study, Sara Kellsson
← Back to work
Case study, 2026

Rebuilding Meridian's business banking from the account outward.

A six-month engagement redesigning the core dashboard, transfer flow, and cardholder controls for a European bank serving 240,000 small businesses.

Client
Meridian Bank
Role
Lead product designer
Timeline
Jan to Jul 2026
Team
2 designers, 6 engineers

Context

Every account owner was routing around the same three screens.

Meridian's original dashboard was designed in 2019 for a smaller book of business. By late 2025 it was handling 40x the volume it was built for. Support tickets clustered around the same friction: reconciling multi-currency balances, moving money between sub-accounts, and adjusting per-card spending limits.

The team had shipped fixes for years without touching the base architecture. Our brief was to rebuild the account-level surface from scratch and prove it in a controlled rollout before touching anything else.

Approach

We stripped the surface to four objects and rebuilt every task around them.

01
Object model first
Accounts, cards, transfers, and rules. Everything the user acts on maps to one of the four. Everything else is a view or a filter.
02
One page per object
Instead of tabbed sections nested three deep, each object gets a single canonical page. Actions live in a right rail. Related objects link inline.
03
Progressive disclosure
The dashboard shows what changed today. Everything else is one keyboard shortcut away. The command bar became the primary navigation for power users.
04
Server-side state
All optimistic UI patterns removed. The interface reflects the ledger, never a hopeful projection of it. Slower, but trusted.
Account overview, transfer flow, and card controls, shown at desktop breakpoint.

Detail

The transfer flow was rebuilt around the ledger, not the form.

The old transfer screen was a series of dropdowns and inputs. Users would enter an amount, submit, and wait several seconds to see whether the money had actually moved. Ambiguity was the biggest source of tickets.

The new version shows the ledger as it will look after the transfer. Amounts appear in position immediately. If the transfer fails, the row disappears rather than a modal popping up. Users understand the state of their money by looking at it, not by reading a status message.

62%
Reduction in support tickets on transfer flow
2.8x
Faster task completion on account switching
94
System usability scale, up from 71
18k
Accounts migrated in phased rollout

"Sara reframed the project on week two. We came in wanting a UI refresh and left with a rebuilt object model that made every future feature cheaper to ship."

Julian Fahri, VP Product, Meridian Bank
Design
Sara Kellsson
Aline Reber
Engineering
Meridian platform team
Six engineers across web and mobile
Research
18 account owner interviews
Four rounds of usability testing
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon
© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon© BrowserMoon