elise pace

Two Years Inside the Product.

myprosperity (now HUB24) is a B2B2C wealth platform. In-house Lead UX/UI across three portals and a native app, from research to shipped UI.

Role
Lead UX/UI Designer & Design Manager
Duration
2020 – 2022 · in-house
Sector
Fintech SaaS, wealth & advice

I ran the design function for two and a half years. For the first year I was the only designer in the business. A year in I put the case to the board for two hires, our first permanent UI designer and a chief product manager. They approved both. From there I managed the UI designer, and guided two interns over half a year, one sitting with marketing and one with product. On this project I was hands-on day to day with one UI designer and the chief product manager.

The Product

A platform where professionals and their clients meet their money.

myprosperity helps accountants and financial planners work with their clients to compile net worth: live data feeds, in-app messaging, automated reporting, documents and e-signatures. I designed and updated its three portals and white-labelled mobile app from 2020, through its life into HUB24.

Mobile app 2022 case study: myprosperity background, the desktop portal, HUB24 docs view and three white-labelled app themes
The platform and its white-labelled app themes: one design system, many brands.

Try It · One System, Three Brands

Same screen, same layout; only the accent and the lockup change. Switch the brand, keep the behaviour.

Northlight

Net worth

$1,284,900

Property$920,000
Super$248,400
Vehicles$116,500
Add an asset
Home
Rooms
Docs
More

Story One · 2022 Tax-Season Research

Six Sessions, Twenty-One Errors.

How do we encourage ongoing adoption for new and returning clients? I ran the mobile usability study end to end (recruiting on Askable, sessions on Zoom, synthesis in Dovetail), with the accountant client's tax journey as the focus.

Finding the Gaps

Map the whole tax journey first: client and partner, side by side.

Before a single session, I mapped the full e-signature-to-tax-room scenario across both actors, from a new client signing through to completing their first tax room, and marked the gaps where people fell out.

Scenario map: new client receives an e-signature request email. Client and partner swimlanes from sign-up through completing the first tax room, with gaps highlighted
Research goals and the double diamond: identify design problems, uncover opportunities, learn user behaviours; focused on the accountant client's mobile tax journey
Research goals, double diamond, and the tax user flow under test.
The research plan: Notion plan, participant schedule, session scripts; organised end to end with Askable, Dovetail, Zoom and Google Drive
The plan, the participants and the scripts, run end to end by one researcher.

Synthesis · What Users Say vs What They Do

Every quote tagged, counted and traceable to tape.

Six moderated sessions became a radar plot of pain points, a donut of likes versus frustrations, and 21 tagged usability errors, with every insight linked back to the Dovetail clip it came from.

Gathering the qualitative research: Dovetail session highlights and a radar plot of pain point note counts, navigation and usability highest
The radar plot: navigation, usability and notifications spoken about most.
Mapping the valuable insights: donut chart of features liked versus frustrations, with tagged session cards for each participant
Likes in teal, frustrations in pink, mapped card by card.
Research roundup: converting qualitative and quantitative data into actionable items. 21 usability errors, navigation and guidance themes, digital forms needing a UI uplift
The roundup: 21 usability errors converted into a build-ready backlog.
Session 2, Participant 2: on the dashboard she would love a My tax documents link, then to analyse and categorise all her data
Session 3, Participant 3: wants documents searchable by words within the docs, and likes tags tied to search

21

Usability errors found across six sessions, each tagged by theme, from missing bottom navigation to digital forms that weren't mobile-native.

Story Two · From Findings to Shipped UI

Assumptions, Validated. Fixes, Shipped.

First Shipped Response · Intercom Tours

Guidance was the gap, so guidance shipped first.

Users asked for a "getting started guide". Within a month of the findings, Intercom mobile carousel tours were live in the app, welcoming users, pointing at tasks, rooms and docs.

3,669

Tours sent via iOS in the first month (May 2022).

63%

iOS tour completion rate.

1,091

Tours sent via Android in the same month.

73%

Android tour completion rate.

Next steps, Intercom tours: carousel prompt screens across iOS and Android with completion metrics after one month live
The tours as shipped: encouragement to keep exploring after every completed task.

The Uplift · UI/UX Overhaul

Familiar behaviours, bottom navigation, mobile-first forms.

Users are already inundated with app behaviours, so the redesign borrowed the familiar: a centralised bottom nav, native digital forms, and a component library of sheets, cards and recipients so every fix landed consistently.

Next steps UI/UX uplift: centralised bottom navigation and native digital forms on the redesigned home, newsfeed and rooms screens
Bottom navigation, so users think less about "where do I go?"
UI/UX consistency: the component library of sheets, to-do cards, room cards, document and recipient cards
The card system: one vocabulary for documents, rooms, to-dos and people.
UI/UX consistency continued: menu, profile and settings screens with the new bottom navigation
Menu, profile and settings: the unglamorous screens, made consistent.

The Prototype

Try the net-worth flow yourself.

The redesigned add-an-asset flow, ending in the small moment of joy the research asked for: open the interactive Figma prototype → (opens in a new tab)

Prototype preview: adding a vehicle to net worth ends in a success state with confetti over the updated net worth screen
Taps "I'm all done", and the net worth screen celebrates with them.

Six sessions, twenty-one errors, one through-line: make the app behave like the apps people already know.