Well Budget was created to help couples budget and track their expenses.
This app is about making budgeting as simple and flexible as possible.
I used the double diamonds method to solve the problem.
After I discovered the problem, I defined the problem by conducting research. Following this, I came up with solutions that could fulfill users' needs and started to do wireframes, prototyping, and developed a design system. Next, I did usability testing. And I modified my design along the way while I was doing the usability testing so the next tester could have a better experience and provide new feedback. After all usability testing was done, I made a final change and had the final delivery of the product.
Controlling expenses and budgeting is always the first step to achieve a financial goal. Most budget apps on the market are designed for personal use, which is very different from two people budget together. Not to mention every couple is different. From how they split to who is in charge.
My goals was: Create a budget app for couples.
Aged from 25-34, has been dating for a while, and is planning to move to the next stage of the relationship. Possibly Asian and more likely to be female. Tried to budget several times in the past, but always lost track due to some uncertainty surrounding income and/or expenses.
To understand more about how people budget, I did 1 quantitative survey (16 replies, 12 valid responses) and 1 qualitative survey (2 interviewees).
Why chose the way they budget: Fits their needs!
How often and how
How about personal budget?
After talking to my interviewees and digging into budget-related research. I've developed my persona. This could help me develop more vivid users in my mind and empathize with what they want and what they need.
After the persona, I created the user journey and the empathy map. I focus more on how Sarah is feeling because female is more likely to be the main user.
As I was developing the journey map, I noticed there are a lot of pain points during the process of setting up the account and keeping track of the expense. I kept this in mind when I was creating the user flow, tried to make the paint points less painful.
Next, I created a user flow based on the journey map. There were a lot of pain points on the journey map and everyone budget in his/her own way. Hence, my goal was to create an app that'd give users a lot of flexibility and easy to keep track.
For Sarah,
After the user flow, I had a more clear idea of what the users' needs are and how they would use the product. The problem was not just to create a budget app, was to create a easy to use app that people wouldn't quit using because it's too complicated or troublesome.
A budget app could be very complicated, in order to deliver the product within a limited timeframe. I wrote down the MVP so I wouldn't get lost while I'm developing the wireframes.
After I worked on the solution, I tried to develop different ways of showing budget and possibility of having a home page.
After the sketch, I went back and took a look at my user flow and MVP. I decided to focus on 4 main pages: Budget, Account, Transaction, Setting.
I wanted to create a trustable and friendly atmosphere for the app. Therefore, I chose blue (trust) and green (calm) as my main colors. But I wanted it to be lighter and more neutral so users wouldn't feel very "heavy" while using the app.
I adopted my mood board to my wireframes to have the mock up to see how the app would look like.
I modified my design according to the usability testing results, including added more pages, remind message...etc.
Research
1. Dive deeper into why people “don’t use app” to know what's stopping them.
2. Interview couples or do field study with couples.
Execution
1. Financial decisions could be complicated, maybe work with financial experts in the future.
2. I focused a lot on "how to keep it simple". Hence, I was missing the opportunity of some potential features .
Overall
1. I only had 3 weeks. If I had longer time, I could spend more time on the interview and maybe try dairy studies.
**Resource: