Avest Bank
Bank of your choice
Timeline
8 week
Tools use
Figma
Fig jam
Role
ui design
Background
Avest Bank is an online banking system that tries to alleviate the challenges people confront in the Nigerian financial sector. Many online banking payment systems have the same qualities.
Their functionality largely focuses on transmitting and receiving payments.
Avest Bank would like to complete its service by offering users specialized tools to track their earnings, schedule payments, and manage their accounts.
Project goal
Create a finance management function to help young professionals deal with their financial worries.
Design process
Empathize
Define
Ideate
Prototype
Test
01 / Empathize - Exploring the User's Needs
Quantitative Research
I decided to send a survey to a wider audience to collect data on people's habits, preferences, and thoughts regarding the difficulties they encounter when using mobile banking apps. This will give me a better idea of the range of problems people experience.
This are the survey i sent out
*What is your age range?
*Are you nigeria?
*how often do you use mobile app?
*Which feature do you most frequently use in your current mobile app?
*What challenges or frustrations do you face when you use your current mobile bank app?
*How important are security features to you in a mobile banking app?
* what design aspect is the most important to you in a mobile banking app?
*would you like personalized tips or alert based on your spending
These are my responses
106 people responded to my survey, and all the participants had different financial concerns, habits, and goals. Here are the statistics I gather. So I decided to draw an empathy map about their feelings, and what they say, think, and do.
What is your age range?
would you like personalized tips or alerts based on your spending?
What design aspect is the most important to you in a mobile banking app?
How important are security features to you in a mobile banking app?
Are you nigeria?
What challenges or frustrations do you face when you use your current mobile bank app?
*Which feature do you most frequently use in your current mobile app?
02 / Define: Identifying User Needs and Issues
I firmly utilized the insights gained from the empathy phase to clearly identify and articulate the user's needs and challenges.
Pain point
-
Instant chat with customer support
-
too long to transfer money
-
Instant chat with customer support
-
Paying bills is complicated and difficult to access
-
Not able to see my notification alert on time
-
Not able to track my spending
Solution
-
Use a chatbot to handle FAQs and basic queries efficiently.
-
Send instant notifications once the transfer is complete, with details of the transaction.
-
Create a notification icon within the app for easy access to missed alerts.
-
Create a dedicated "Bill Payment" section on the app's homepage for easy access.
-
I offer visual analytics, charts, to show spending trends over time and track their earnings.
-
I integrate one-tap payment options for efficiency eg quick access.
User personal
I create detailed profiles for the tropical user based on the information I gather; these personalities help me visualize what the product or service means. Making it easier to keep their needs in mind.
03 / Ideate: Creating the Framework
Ideation
For the ideation phase, I used the Crazy 8 brainstorming exercise. This session entailed 5-minute intervals of 8 sketches with an intentional break of 20-30 minutes. I did not compose 8 sketches each time, but this exercise forced me to generate ideas, and I spent the breaks thinking about the ideas I wanted to elaborate on. This was a great exercise for getting my ideas on paper. After doing this exercise five times, I compiled my sketches and grouped them according to themes.
How might
These are the problem statements I decided to focus on before designing the wireframe:
-
How might we be able to make online banking more secure for the customer?
-
How might we be able to make online banking more secure for the customer?
-
How might we facilitate money transfers to ensure smooth and effective transactions?
-
How might we show users how they are using their money so that they can understand how they are spending their money?
-
How might we help users track their spending?
User flow
After I finished sketching, I decided to use the concepts I had come up with to develop a feature that makes transactions simple for users. Within this feature, I wanted to integrate ways users can improve their financial health and manage expenses.
Information Architecture
An information architecture was created based on user needs and research analysis to guarantee easy-to-use navigation and rapid access to important features in Avest.
Prototype
Low fidelity wireframe
The high-fidelity wireframe showcases Avest's refined design, with detailed visuals and interaction that bring the user experience to life.
High fidelity wireframe
usability testing
The usability test consisted of conducting approximately 30-minute testing sessions with 5 people who fit the AVEST target user demographic. Then we collected our notes and synthesized our findings with affinity maps.
I added a quick Access section for easy transactions for the user
I added month section so user can their last month spending and track there earning
I added popular bank which is the most use bank for user
Muck up
Learning Outcomes
Working on this project has truly opened my eyes to how important it is to enter the research phase with an open mind and no preconceived notions about solutions. I’ve come to appreciate that the insights gained from surveys and secondary research can reveal aspects we might not have considered initially. It’s all too common to latch onto a solution we like and then only look for information that reinforces our beliefs. Unfortunately, this often means we miss the opportunity to understand and address the real challenges users are facing.
I’ve also learned that experimenting early in the process, especially during the sketching phase, can be incredibly beneficial. I understand that as we dive deeper into the project, making changes becomes more challenging. By allowing ourselves the freedom to explore different app designs early on, we can ease some of that pressure and pave the way for a more thoughtful and effective outcome in the long run. It’s about giving ourselves the space to innovate and truly meet the needs of our users.
Lessons Learned
-
Trust is the foundation of financial apps.
-
Simple language, clean design, and transparency build user confidence.
-
Continuous testing and feedback loops are critical for success.