← Back to work Case Study · 2025

Insights 2.0

Rebuilding the core client reporting platform for RMs serving UHNI and family office clients. Information architecture, data visualization, and workflows for the places where serious money gets decided.

Role
Lead Product Designer
Team
2 designers, 4 engineers, 1 PM
Scope
IA, UX, UI, prototyping
Year
2025

The platform RMs used every morning was the platform they trusted the least.

Insights was the core client reporting platform serving Relationship Managers across the firm. The tool they opened first thing in the morning to pull portfolio snapshots before client calls, and the tool they complained about the most.

Data lived in three different places. The legacy version was built in 2018 for UHNI and family office clients and had slowly drifted out of sync with how RMs actually worked. RMs were exporting everything to Excel and rebuilding views from scratch, every single day.

RMs were losing 90 minutes a day rebuilding views the platform should have given them.

We talked to 14 RMs, 3 portfolio managers, and 2 heads of wealth across two weeks. The same three things came up:

So the goal was to run the morning client review inside the platform instead of in Excel.

Two things we couldn't change.

A new information model, then the interface.

Instead of starting with screens, we started with the mental model. We mapped how a senior RM actually thinks about a client: family, relationship, portfolio, holdings, transactions. Then rebuilt the IA around that hierarchy.

Once the hierarchy was right, the screens fell out of it. A single client canvas replaced the six tabs. Benchmarks, allocation drift, and transaction history stayed on the canvas instead of living on separate pages. The dashboard answered the four questions every RM asked first: what moved, what's at risk, what needs action, what to talk about.

"The first week, I caught myself Cmd+Tabbing to Excel. By the second, I didn't need to."

Data visualization was the second half of the work. We moved from legacy donut-chart defaults to a restrained palette of four chart types, each tied to a specific question an RM was trying to answer. No chart existed without a reason. We drew every state (empty, loading, stale, drift) so none were left to the developer.

Selected screens from the platform.

Preview of selected surfaces · Full deck shared on request

Insights 2.0 is live inside a private wealth platform. What's below is a preview of the design work: three hero surfaces walked through in narrative, and a grid of deeper surfaces from the rest of the platform. The full process, artifacts, interaction prototypes, and the NDA-guarded context sit behind a request.

The morning dashboard

The first screen every RM opened. AUM, gain/loss, net cashflow, cash equivalents, top families, and the live asset mix. All resolved before the first call of the day.

My Dashboard, teaser view

Portfolio overview. One canvas per client.

The single client view that replaced six legacy tabs. A snapshot across every asset class with filters for family member, engagement, date range, and benchmark. Resolved in one scroll.

Portfolio Overview, Summary tab
Portfolio Overview, Analysis tab

More from the platform

Deeper surfaces I can walk you through live: families, holdings (with fund-level cards), cross-asset analytics, portfolio health & IPS tracking, and the market outlook panel.

Families list view
Families Protected
Holdings fund card
Holdings · Fund Cards Protected
Portfolio analytics equity view
Analytics · Equity Protected
Portfolio health and IPS tracking
Health & IPS Protected
Market outlook panel
Market Outlook Protected
User-defined benchmark overlay
User Benchmark Protected
Want the full walkthrough? The complete deck (process, artifacts, interaction prototypes, and unblurred screens) is shared under NDA on request.
Request full case study →

The work shipped on the design system I built in parallel.

Insights 2.0 was the first product to fully consume ONE Design System, the internal design system I built and scaled across four wealth product lines. Tokens, components, and chart primitives all came from the system, which meant the rebuild moved faster and the handoff stayed clean.

Fewer clicks, fewer charts, one canvas.

~70% Reduction in clicks to complete a daily client review
4 Chart types replacing 11 legacy visualizations
1 Unified canvas replacing six separate tabs

Data-heavy software works best when it shows less.

The old version was trying to prove it was powerful by showing everything. The rebuild earned trust by showing only what answered a question. Every screen had a job and every chart had a reason. Anything else got cut.

RMs handle real money for real families. Their tools need to be honest, fast, and quiet before they need to be beautiful. That became the bar for everything that shipped after.

Next case study Brenman Talent In-house HR platform that replaced a per-seat subscription, built solo in two weeks.