← All work

FNZ client portal

When the conditions aren’t right, design the conditions.

Client
FNZ
Sector
Wealth management
Role
Senior product designer, sole UX
Year
2025
Status
Lo-fi and mid-fi, then taken in-house
Lo-fi onboarding screens covering setup, documents and the dashboard Open full size →

TLDR

A wealth portal built once for many advice firms, while the first client wanted its own. As sole UX designer, I turned bespoke requests into configuration and cut 30+ user stories to four journeys. The whole was never agreed, but the single inbox and request-led documents landed.

01

One product for many firms, while one firm wanted its own

I answered bespoke requests with configuration: switch a feature off, never build a version.

Six product owners held six definitions, with no personas. So the dashboard became a fixed set of widgets each firm switches on or off. A firm with no goals product never shows goals.

Dashboard wireframe showing total net wealth, a wealth against debt bar, and goals at a glance.
Dashboard widgets. Goals disappear for firms that don’t offer them

02

Two inboxes became one, and the vault became a request

Existing behaviour argued against both stories, and both cuts landed.

Seventy per cent of the client’s existing users were on mobile, which held mobile-first against a web-focused room. At FNB, people testing a document vault I’d designed hesitated to store documents with their bank, so clients here upload against a request instead.

What the user stories asked for, what I proposed, and why
The stories asked forI proposedBecause
Messages and notifications, two areasOne filtered inbox, action required firstOne place to check
A personal document vaultReceive documents, upload on requestAt FNB, people hesitated to store documents with a bank
A sharing-permissions modelRemovedThe upload is the permission
Secure Messages screen with a single filtered inbox, an action required group at the top, then the inbox grouped by month.
Secure messaging wireframe with one inbox and an action queue

03

An interim dashboard while the money moves

Until onboarding ends, the dashboard tracks each transfer, and it changes as they land.

Product owners expected onboarding to take weeks, longer when a mortgage or another provider’s policy moves across. An empty dashboard in that gap reads as nothing happening.

Interim dashboard at 30 per cent: onboarding progress on holdings breakdown, next steps for a financial and risk review and plan research, and a welcome call in the calendar. No portfolio value yet.
At 30%: progress and next steps, no value
Interim dashboard at 80 per cent: a total value of 62,089 pounds, a pension transfer in progress, a tax planning report as the next step, and a Stocks and Shares ISA in accounts.
At 80%: the value and first account appear

04

What landed, and what didn’t

The inbox and request-led documents landed. Agreement on the whole stalled on what every firm must show, and what success meant.

  • 4journeys, from 30+ user stories
  • 1inbox, from two product areas
  • 15+reviews
  • 6product owners

My journey template gave six product owners one format, but a format can’t settle a strategy. The client then took design in-house. The work stays with FNZ as an internal core product, not yet reused with another client.

Blank journey template: story, criteria and edge cases before wireframes Open full size →

Next time

Both questions come first, with the alignment workshop I asked for midway. I’d measure onboarding completion and how often firms configure rather than build.

Later visualisation, not production design

Two dashboard concepts side by side in the ABC Wealth demo brand. Wealth at a glance: total net wealth with a wealth against debt bar, two goals on track, and protection products. Wealth in depth: net worth against debt over time, a time range selector, and a breakdown starting with investments. A later visualisation of her dashboard direction, not production user interface.
Dashboard direction, at a glance and in depth