Platform reach
20,000+ usersFront-office advisors, client service, operations, and other wealth management teams.
Earlier case study
Connect is an enterprise desktop platform used by more than 20,000 people across front-office advisory, client service, operations, and other wealth management functions.
As a Senior UX Designer on the Connect Core Team, I worked across the design system, UX governance, and consulting engagements that shaped how applications entered the ecosystem. This case study outlines that platform role, then examines Financial Entry, a ten-month project I led as the sole designer.
Front-office advisors, client service, operations, and other wealth management teams.
Shared experience standards and direct product engagements across the ecosystem.
A scalable workflow for capturing held-away assets across 22 asset types.
Supporting the shared foundation behind every Connect application
The Connect Core Team managed the parts of the ecosystem that every user encountered. My work combined system stewardship with direct product design across multiple teams.
Documented components, their variations, and appropriate use. I also identified opportunities to improve shared patterns.
Reviewed new applications and features with teams across the firm to understand business goals and evaluate alignment with design and ADA standards.
Led several engagements at once, from complete design processes to focused support for teams without dedicated UX resources.
Designed an interface that helped teams identify and repair extraction errors in digitized documents. The application reduced manual data entry.
Designed a net-worth dashboard that included external accounts and a streamlined workflow for adding assets and liabilities.
Designed a strategy and cross-application experience that moved data between J.P. Morgan and third-party tools within the advisor workflow.
Financial Entry
Enabling advisors to capture a client’s complete financial picture
Financial Entry established a scalable way to capture held-away assets. It reduced an advisor workflow that took one to two hours to between three and fifteen minutes.
Only 5% of clients were aggregating assets online
Advisors often collected statements and tracked held-away assets through spreadsheets, PDFs, and personal workflows. The process required significant administrative effort and created inconsistent records. It also left the firm without a complete view of client wealth.
The opportunity was to make external asset entry sustainable within an advisor’s daily workflow and create a single source of truth for planning, reporting, and other wealth management experiences.
Manual entry reduced the time advisors could spend on relationships and business growth.
Disconnected records increased the chance that financial information would become incomplete or outdated.
Downstream applications lacked consistent access to a client’s complete financial picture.
Leading a foundational initiative through changing requirements
As the sole project designer, I defined the advisor workflow, conducted research, drove interaction design, facilitated usability testing, and partnered with Product and Engineering through delivery.
Understanding how advisors managed held-away assets
Advisor interviews showed that disconnected tools created repetitive work and inconsistent information. Advisors valued a dedicated view that made gaps in a client’s portfolio visible.
How might we help advisors enter external assets quickly enough to make aggregation sustainable within their daily workflow?
One reusable framework for 22 asset types
I identified the structures shared across asset categories instead of designing 22 separate workflows. Each asset type combined core account information, asset-specific information, and review or management actions.
We started with the most complex asset type to stress-test the framework before applying it to simpler categories. This reduced design complexity and created a consistent foundation for future expansion.
We prioritized a shared framework over one-off workflows for individual asset types. This reduced cognitive load and simplified implementation.
We focused the release on a reliable asset-entry foundation. Additional integrations and downstream use cases could build on that system later.
Creating a more predictable path through delivery
The product owner was new to the role, requirements changed frequently, and deadlines had been committed before the team was staffed. Engineering teams risked revisiting work as priorities evolved.
Testing efficiency before scaling
Moderated usability sessions validated the value of streamlined workflows, consistent layouts, and multiple entry methods. Bulk upload capabilities also reduced perceived effort.
The findings guided refinements to the dashboard and entry screens. They helped decrease cognitive load and time to completion before the framework expanded across asset types.
The final workflow gave advisors a faster, consistent way to capture held-away assets and created a centralized source of truth for downstream planning and reporting.
The project strengthened my ability to lead through ambiguity, align teams, and design systems that extend beyond a single release.
If I approached the work again, I would establish stronger requirement governance earlier and align teams before major design exploration began.
Explore more work