Enabling existing customers to open investment accounts without visiting a branch or calling.

PNC Wealth Management

Enabling existing customers to open investment accounts without visiting a branch or calling.

PNC Wealth Management

Individual Brokerage Application
Company: PNC Wealth Management | Duration: 6 months
My Role: Design Lead — Competitive research, end-to-end user experience, and managing additional designers.
Table of Contents
1. Overview
2. Creating a Starting Point (user journey & service blueprint)
3. Gathering Requirements with Story Maps
4. Competitive Research
5. Low-Fidelity Wireframes
6. High-Fidelity Screens
1. Overview
Customers who wanted an investment account had to call in or visit a branch to open one.
There was no way to open an investment account digitally with PNC. I was tasked with designing the first digital application for an Individual Brokerage account, a standard investment account that allows customers to trade stocks and ETFs.

Users

Existing PNC Customers
Scope and Constraints
• Fuelle end-to-end appilcation
• The Account Opening Platform is the environment in which all digital applications are built.
• Third-party API integration
The Problem
Weaving together the needs of multiple stakeholders and systems required transparency and cross-team collaboration to succeed. 
Designing the digital application required aligning business requirements from the Wealth Management Product, Operations, and Account Opening teams with the needs of multiple design systems and technology platforms.
2. Creating a Starting Point
Understanding the customer journey and technology systems helped the Product Team clarify the path forward and define the work needed to secure resources.
Creating a User Journey artifact helped align all the stakeholders around what we needed to build.
I partnered with the Product Manager and Design Manager to map the user journey, creating a foundation for requirements gathering and a high-level roadmap the Product Manager could share with leadership.
The Service Blueprint highlighted the complexity of a digital product application to the new product team.
Banking is subject to many regulations governing the management of personally identifiable information and financial records. This leads to data being segregated across many systems. I created a blueprint showing the paths data for an investment applicant would need to follow for the new Product Manager and Business Analyst.
3. Gathering Requirements with Story Maps
The Story Map enabled me to collaborate with a large group of stakeholders to quickly gather and iterate through requirements.
To start designing, I needed solid business requirements. Rather than waiting for them to be handed to me, I drove requirements gathering through cross-team collaboration using a Story Map. This let me quickly get feedback from multiple stakeholder groups and work with our tech leads to identify what the third-party APIs we were using required.
Choosing which user inputs we needed from 3 different resources required additional diagramming to determine which inputs to use.
I worked with our Business Analyst to cross-reference users' inputs required by the underlying service API, Wealth Management Operations, and Federal Regulations to determine which to include in our digital application.


4. Competitive Research
Competitive Research made the case for being more succinct in how we ask regulatory questions, rather than bombarding customers with too many questions. 
Our legal team initially wanted to display every regulatory question, which would have created a lengthy list. Competitive research revealed how others in the industry addressed complex regulatory requirements, giving us the insight to push back and find a middle ground. Using progressive disclosure, I distilled the list into five questions, with additional required questions appearing when relevant.
5. Low-fidelity Wireframes
Low-fidelity wireframes helped push boundaries, identify gaps in the design system, and iterate on solutions to reduce customer friction.
I had to use two different design systems to design the application: the PNC-wide design library and an account-opening library with components specific to product applications. Starting with low-fidelity wireframes helped me determine when the account-opening library took precedence over the PNC-wide library. 
I also used wireframes to identify friction points and improve the user experience. For example, I reduced the number of regulatory questions. After reviewing the competitive research, I developed a few concepts supported by what our competitors are doing.
6. Individual Brokerage Application
High-Fidelity Designs
I created the initial happy path in Figma, then guided another designer in developing the sad path and incorporating stakeholder feedback to arrive at the final product.
Starting the application and Reviewing personal information
Regulatory and Financial questions
Adding a trusted contanct
Application review
Terms & Conditions and Congratulations (application end)
↑Back to Top