Financial Dasboard

Challenge

I knew the stakeholders wanted to enhance the use of the dashboard, but we did not know what the user thought about the dashboard, so the first step was to approach the users to understand what was the problem to solve in order to move forward.

Users who interact with this section have mostly managerial roles, with high degrees of education and knowledge of technological—financial tools. The most used tools mentioned were Quickbooks, Netsuite, Zoho Books, and SAP concur.

‍

Research

Internal and external qualitative research was conducted; and was divided into two phases, the goal was to collect feedback from internal people to discover and get ideas, then with the end user to verify and refine them.

First, a focus group with team members who work directly with users to understand more about their role in the company, what their daily bases look like, common paint points for the user, and the most common needs the user requested for the dashboard. Additionally, the full story app data matched a couple of feedback findings.

‍

First clues

I found that users had almost no interaction with the dashboard because important information was missing or hidden and the information displayed was not clear.

For this stage, the product team was in the research sessions as listeners, they wanted to use the feedback as a basis to build a product definition.

‍

Next clues

For the second part, individual interviews with end users were scheduled, accompanied by an exercise.

The idea was to refine and confirm the first draft of ideas showing the actual section, which led to an open critique chat and then an exercise where the user was asked to type and rank the information and features they needed to see in the dashboard from most to least important.​​​​​​​

The last session led to defining the relevant information and user actions, which showed us that we needed to explore a proposal with that in mind. Users needed to know their spending behavior and wanted a reminder of actions to take.

‍

Solution

Before I started working on a hi-fi proposal, I drew a low-fidelity to communicate the big idea to the product, engineering and data team. Those wireframes helped collect and understand the information that we could bring in from the core in order to display to the user.

I wanted to focus on feasible, reliable, and functional features for the users. The product team also wanted to focus on adding an insights section that would provide information on financial behavior regarding their lines of credit in order to give users clues to save or improve the use of their credit. Those insights would be built with the help of the data team.

Having gone through a series of iterations, we landed on a card-based top which allowed us to identify the information

After a series of iterations and touch points with the product and engineering team, the high-fidelity proposal was ready. Based in cards and modules that allowed information to be found based on users' concerns.

‍

Result

Before the handoff, I approached again with 10 participants and run out a usability test with a prototype to find out if this new version would add value to the platform and solve the interaction problem.

The outcomes from the usability test pointed out that all the participants confirmed that the information and actions displayed were more useful with the new proposal, and they realized they have benefits with the company. Based on feedback regarding actions and content within the proposal The iterations were made and together with the product, engineering, and data team the final version was decided.

The handoff was prepared with the team and the suggestion was to conduct new research 3 months after it has been implemented and launched into production.

You can sneak-peek the prototype here.

‍

Thanks for watching! ♥︎ You can review my other projects.

‍