Portfolio Analysis Experience
Simplifying investment analysis for high-net-worth clients through a scalable multi-currency platform.
Role
Senior Product Designer
Industry
Private Banking
Duration
6 months

My Role
Led end-to-end UX for the investments area redesign
Restructured information architecture across asset classes
Partnered with product, engineering, and business teams
Defined financial microcopy and nomenclature standards
Contributed components to the shared design system
The Problem
Investment visibility is a core expectation in private banking. High-net-worth clients managing multi-asset portfolios need to compare positions, track performance, and make decisions with confidence. The existing platform presented investments in a card-based layout that made comparison across assets difficult — clients frequently navigated back and forth between screens to view positions they could not see side by side.
The friction was well-documented through FullStory session recordings and consistent client feedback, which helped align the team around the need for a structural redesign of the investments area.

Results
The platform evolved from v1.0 to v2.4, shipped and in production. User satisfaction on the Likert scale grew from 12% to 39% month over month. Asset table feedback shifted from negative to positive, with clients directly praising the redesign in survey responses.
Multi-currency support expanded from a single currency to four — USD, BRL, AUD, and NZD — enabling the platform to serve a broader international client base.
Results tracked monthly and presented to executive stakeholders · Itaú Private Bank · 2025
Reflection
This project reinforced that in financial products, layout is not a visual decision — it is a functional one. The shift from cards to a data table was not about aesthetics; it was about giving clients the tools they needed to make informed decisions. When the structure matches how users think, the interface gets out of the way.
Working across product, engineering, and business teams on a project with both UX and data complexity also reinforced the importance of shared language. Standardizing financial nomenclature early prevented inconsistencies that would have been costly to fix later — and contributed to a more cohesive experience across the platform.


