Monee Bank App


The goal of this project is to design a dashboard for a banking app. To make it happen I have used the information provided for the company in their UX Research Report.

Below you will find the process detailed.
Thanks for your attention!

1. Starting. Immersion Phase.

Before starting, I just want to make clear that I understand the design process as a team process, because it is important to count with different points of view and different cultural backgrounds in order to build a better product. In this case it won't be possible, so all the conclusions will be just based on my point of view.

In order to achieve a good understanding of the context, and to assimilate the most important goals of the project, I tried to visualize all the key points exposed at the research report.

This first step is quite important, it will allow me to change my point of view and put myself in the end users' place. After that, I will have a deeper understanding of the target whom I am designing for. Furthermore, this visual thinking phase will help me to connect dots and discover user patterns.

Below an screenshot, the first big picture of the project.

One of the first conclusions that I found is that I design for millennials, people aged between 22 and 35 years old. They are digitals, they use all kind of digital devices, and they do not trust banks; they don’t understand them and they think banks does not understand them either.

As you can appreciate in the previous picture, we have two different kind of profiles here, the "Young Students" and the "Young Workers".

What do they have in common that they use a few simple products and they want to use it fast, without commissions, always having someone by their side to help them. They also want a personalized attention, and they want to feel secure, feel quiet, and find trust thru clarity.

They have some different behaviour patterns, also:

Young Students

Young Workers

After analyze all that information I have some assumptions. One of them is that the dashboard should be dynamic and contextual, should reflect the personal activity of each user, as each one is different. That will provide trust and transparency.

We can achieve it using the system itself or giving the users the tools to design their own dashboard. In an ideal scenario, we should test this in order to figure out which is the best option.

Another assumption, is that the dashboard should work as a distributor, giving the users the chance to find what they are looking for. To make that possible a sitemap based in all the possible userflows is required. I will make mine based on the UX Research, an analysis of the competence, and by asking some users.

It seems clear that young users are not feeling comfortable with the current tone of voice used by banks, so a new one will be needed if we want to get closer to our customers.

2. What others do? Market Tendencies.

The next step is to analyze what others do and identify which elements they use that would help us to give a better service.

Below the mobile solutions for millennials created by other companies.

Check the result of the analisis below.

Based on this information I conceptualized some ideas that could solve the user's concerns:

3. Conceptualize.

The next step was to collect all the information and ask some users who help me to sort it.

His perception helped me to set up an Information Arquitecture, that was the basis on which I began to build the first low-fidelity wireframes. After some quick iterations I made a more detailed wireframe, the last step before starting with the final visual design.

Check the final design below.