A redesigned accounts dashboard for a UK retail bank, improving self-service across desktop and mobile for 75K+ customers, while laying a modular foundation for future products.
✦ Web Prototype ↗ ✦ Mobile Prototype ↗Queen Bank* is a UK-based bank with 75K+ users. As it scaled, the accounts dashboard became cluttered and inconsistent. Customers struggled to understand their accounts, navigate services, and complete basic tasks without customer support assistance.
This compounded into three quiet but expensive problems:
* Name changed due to NDA
The brief sounded simple. The reality was that "independence" only works when the interface is calm enough to be read at a glance, on a phone, between tasks. Most banking UI announces. We needed one that answers.
I redesigned the accounts dashboard by establishing a clear information hierarchy, simplifying copy, and introducing consistent, reusable UI patterns. The experience was designed to be accessible by default and responsive across devices.
A modular layout ensured the dashboard could scale with future products while supporting incremental releases, no big-bang rewrite.
A redesign disciplined by hierarchy, consistency, accessibility, and device-first thinking.
They're complex to build, but they significantly reduce long-term effort. Every component reused is a decision you don't have to defend again.
Frequent developer reviews, before final pixel polish, prevent costly rework and keep design intent intact through implementation.
Managing time within sprint constraints is a craft. Knowing what's "done enough this cycle" is as important as knowing what's "good."
Knowing when to stop is as important as knowing what to improve. Most "one more iteration" cycles cost more than they earn.
This project reinforced that strong product design isn't about perfect screens. It's about thoughtful trade-offs, designing for scale, and enabling users to help themselves within real-world constraints.