Case Study Overview

Client

Global Bank - Fictional Bank for the Design Challenge.

Problem Statement

Create a risk analyst dashboard for foreign exchange loan risk analysts that allows them to:

conduct data analysis

flag high risk loans

escalate loans to supervisors

Deliverables

I delivered the following:

A risk analyst dashboard

Buttons for flagging and escalating high risk loans

Solution

The solution included additions to the design system provided such as loan cards, various risk analyst interaction points.

Research

Review Provided UX Research

The design challenge provided a number of materials from the user experience research team to inform the user experience design of the dashboard. These included:

Risk Analyst Persona

Design System

User Interviews

I interviewed 3 users about their specific experiences surrounding financial risk assessment and exchanging currency.

Their responses guided the initial sketches and their continued feedback was sought throughout the process.

Co-Design

A Co-Design session was conducted with one of the user's interviewed during one of the feedback sessions. This provided valuable insight on the different mental models associated with buttons shapes and presentation.

Insights

Risk Indicators

Risk indicators like potential loss and computer determined risk should be easily seen at a glance.
‍
I learned from my subject matter expert that very little information should be needed in order to know whether or not to escalate a loan. They personally would only want to see the potential loss risk amount in national currency and the computer generated risk indicator number. They felt any additional information could be considered a waste of time.

Speed

Visuals and interactions should be dark, but soothing while in the underworld and the overworld should contrast.

The persona provided by the User Research team indicated that the risk analysts value taking as little time as possible to make an accurate assessment of a loan while still being able to access any additional information they may want to make that decision.

First Iteration

Basic Structure

For the first iteration, I started with sketching out my initial ideas based off the initial interview conducted with a subject matter expert. From there, I took these rough sketches to a Product Owner to gain their feedback and concerns. This developed organically in a co-design session that resulted in the sketches to the right.

Second Iteration

Risk Interaction Points

For my second mini sprint, I worked on the needed additions to the design system to meet the design challenge deliverables. I was specifically tasked with creating a way to flag a loan and to escalate a loan review. For these two buttons I drew from my interviews and co-design session for the way they would look and interact. When I took them to the users, they gave them positive reviews for understanding their function on site.

Third Iteration

Interaction Placement

Taking the feedback I had from the previous two iterations, I created a medium fidelity prototype to present to the Design Challenge team. Before presenting it to the team, I presented it to my subject matter expert and my product owner for last minute feedback and suggestions. Both provided positive responses, so I proceeded with the presentation.

The Design Challenge Team had concerns about the risk interaction points being placed close enough to create confusion as to what is a button and what isn't a button. They also had concern about having a save interaction from the base dashboard. I would take these concerns into account as I cleaned up the final design.

Final Design

For the final design, I moved the risk indicator closer to the other loan information to help make it clear that this is another data point to be used in the decision making process. This allowed for a wider gap between the risk indicator and interaction points to escalate and flag loans. Finally I removed the save button from the quick view card to reflect the mindset that a loan being flagged or escalated would be autosaved. Instead, the save interaction is only available when commenting is enabled so the risk analyst can denote their comments are complete.

Reflections

I personally really enjoyed working through this design challenge. It gave me the opportunity to work within a strict timeline of 5 days and to work within a design system. This led me to be more creative with where I was gonna get my information and feedback as I worked. It also gave me the opportunity to look at a design system and reimagine it into a fresh modern look.

Overall, the design challenged pushed me harder into better time management of the project and into prioritizing higher impact ROIs.