top of page
Screenshot 2024-02-14 at 11.45.29 AM.png

Savi Finance

I was working on a dashboard page with the key stakeholders to organize it from scratch.

Team 

Project Manager
Lead UX/UI Designer

UX/UI Designer Intern (me)

Duration

3 weeks

Role

UX/UI Designer Intern

Time

Fall 2023

Problem

Lack of understanding of how the dashboard should look like, which type of layout it should have, and what kinds of widgets should be included.

Solution

By conducting thorough research and constantly going back and forth with the project manager and lead UX/UI Designer, I finished the project with a 5-widget dashboard and two additional widgets that could be found in a dropdown menu.

As my knowledge of organizing financial dashboards was equal to zero, I decided that the first step should be researching every single dashboard related to the financial institutions I could find.

The most helpful were FIQ, FIBOARD, Finb, Muzli, Super Syatem, and Monarch which I found with the help of various internet sources.

IMG_8564.PNG
Screenshot 2024-02-15 at 8.04.36 PM.png
IMG_8567.PNG
Screenshot 2024-02-15 at 8.06.14 PM.png

After making sure that I had a lot of insights to base my dashboard on, I started to work on the layout.

The main problem with the dashboard's layout was that the project manager wasn't sure which layout would be the best to go with. So, I created the three most popular options of the layouts to choose from.

Screenshot 2024-02-16 at 10.18.22 AM.png
Screenshot 2024-02-16 at 10.17.50 AM.png
Screenshot 2024-02-16 at 10.18.03 AM.png

I set up a quick meeting where the project manager, lead designer, and I decided to go for the version with eight widgets visible on the screen. So, with the chosen layout in mind, we also discussed and wrote down all the widgets from the list I created during the research phase.

The decision was to have six vitally important widgets located on the screen while two remaining which are not as important as those on the screen hidden in the dropdown menu.

The layout and the widgets we wanted to include were chosen. Therefore, I started working on a low-fidelity version of the dashboard to prepare it for usability testings.

Screenshot 2024-02-16 at 2.30.00 PM.png

Some of the insights I got from the testings:

​

  • Recurring transactions and Oct. transactions should be located within one widget;

  • Every column should have a name, otherwise, it is hard to understand everything happening in the account overview and transactions widgets;

  • The Peak Net Worth chart should have the amount a user begins with and at what year the whole amount is going to be spent;

  • There should be a legend for the used colors somewhere;

  • The Annual savings performance chart should be simplified.

After the testings, I started to craft the final version of the dashboard.

Screenshot 2024-02-16 at 2.56.44 PM.png

My takeaways and assumptions

Thorough research, communication between the project manager, and lead designer, as well as the usability testings, were essential engines of progress for the completion of the project. Without one of the components, the project wouldn't be as complete as it is now. 

​

As for the assumptions: the main reason why I didn't go for a high-fidelity for the dashboard was that I was waiting for another designer to finish with a design system for the company. So, unfortunately, I left the company before it happened, but if I were still there, I would for sure finish the project with a brand-focused UI.  

bottom of page