User journey map allowed for visibility across a vast ecosystem

Connecting your bank and importing transactions allows Wave to become the source of truth for your business. Once a business owners transactions are in Wave, they can get insights to their business such as expenses, profit & loss, and other reports.

To understand why a user would connect their bank, I took a look at the user journey of connecting a bank in Wave. I put together the user journey from 3 data points:

From here I identified key points to focus on.

Untitled

By auditing all the places in Wave where users are asked to connect their bank, I got a holistic view of the user experience surrounding bank connection. This ensured users would only be asked to connect their bank when it’s contextually relevant, helping build trust through consideration and care.

Creating access to the product through Design Systems

The Central Banking project touched every product team in the company. In order to act on these areas of the product across the ecosystem, the screens needed to be available in our design tooling. I recreated fully editable and componentized screens available for designers in our design tooling. This allowed anybody to have access to these screens for user flows, user testing, iteration, and other design tasks with full customizability.

It also provided access and visibility to areas of the app to all designers and other stakeholders, without the need to create test accounts and go through the flows manually.

This started an initiative within the design team to create a robust and complete set of fully editable, componentized, and customizable screens for our respective areas to work with. Any designer to follow would have a supportive base to start new projects from, and explore existing UI.

Untitled

Untitled

➡️ Next

Bank connect experience


🔙 Back

What is Central Banking?