Case Study
simplifi is a budgeting app focused on a modular, educational approach to budgeting.
UX Research, Visual Design, Branding
Pen and paper, Figma, Usability Hub, Optimal Sort, paint.net, InVision, Maze
User surveys, competitive analysis, personas, user stories and flows, branding and style guide, wireframes, prototypes, user testing
Many people struggle with budgeting for a number of reasons. Either current tools don’t work for them, they’re nervous about facing the truth of their financial reality, or they simply have no idea how to start. No current budgeting app serves these markets and helps to introduce people to budgeting.
The solution was simplifi, a budgeting app prioritizing new budgeters while also providing useful tools for those with more experience. The primary goal was to provide easy access to budgeting by starting them off with three categories of expenses and the ability to set individual goals, then track their expenses by linking chosen accounts and analyzing their expenses in order to help them develop and specialize their budget, in essence teaching them how to budget.
The first step was looking at competitors to see what they offered, and where simplifi could find ways to attract its own audience. Of the current major options, we selected Mint, Wally, and You Need a Budget (YNAB), and then performed a SWOT analysis and found a couple of key opportunities:
Next we took a survey to determine how much space there was for an educational tool, and how many people even really look at budgeting apps to begin with. When we finished the surveys, we made a few key observations.
First, that of people who do budget, a surprisingly small number of our responders used any budgeting app. Many either used generic spreadsheets or did budgeting by hand.
Use generic spreadsheets or budget by hand
Would use or consider using a budget app or software
In addition to the surveys, we ran a card sort to try and determine how people viewed and sorted a variety of purchases. In most cases, the responders divided the items into some variation of three categories, with varying labels.
Using the data and some interviews, we created three user personas, each for a user at a different level of experience to encompass the different levels at which clients would engage with the app.
Next, we modeled user stories and user flows based on those profiles and survey responses. These stories and flows were primarily based on the straightforward usage of a budgeting app, but high priority stories were split between new and general/advanced users.
Role | Task | Importance |
---|---|---|
As a new user | I want to create a user account | High |
As a new user | I want to enroll a bank account | High |
As a new user | I want to create a budget through budget items | High |
As a new user | I want to see an analysis of my spending after the first month | High |
As a general user | I want to enroll additional accounts | High |
As a general user | I want to adjust my budget items | High |
As a general user | I want to edit/delete my accounts | High |
As a general user | I want to edit and change my goals | High |
As a general user | I want to add new budget line items | High |
As a new/general user | I want to receive push notification on purchases showing my remaining budget for that category | Medium |
As a new/general user | I want to see quick digestable stats per month | Medium |
As a new/general user | I want to set specific success milestones | Medium |
As a new/general user | I want to see suggestions for tweaking my budget in the event of consistent overspending | Low |
As a new/general user | I want to see 3-, 6-, 9-, and 12-month analyses | Low |
As a new/general user | I want to divide purchases into multiple categories | Low |
As a new/general user | I want to automatically sort recurring purchases | Low |
As a new/general user | I want to set up scheduled transactions | Low |
As a new/general user | I want to categorize transaction types | Low |
As a new/general user | I want to enroll retirement accounts | Low |
The first round of wireframes was designed specifically for usability, to attempt to put to paper (so to speak) the user flows above while trying to flesh out the basic design of the page.
We conducted our first round of testing here, with four tasks:
This first prototype ran afoul of users almost immediately. When conducting a Maze test and in-person testing, the Add Account page was poorly explained and resulted in a mere 33% success rate on the page.
This necessitated a revision.
The revision worked better. However, outside of the Add Account confusion, there was very little confusion. Users had no real issue, and there were some good reviews, specifically one user mentioned that he appreciated the ability to set an end date to the goal as a way to help measure concrete progress.
Once the Add Account page was fixed and flows were re-evaluated and confirmed to work as intended, we were ready to step into branding.
First we started with brainstorming on the app using a mindmap.
I started with the concept of zen, which branched off into mindfulness and calm, which are core elements of zen, as well as the Japanese word “anzen” which means safety or security. These would become watchwords for the mood I wanted to create, and they helped me to define the product, which at the time was nameless.
Next I worked on logo design, which also helped me to workshop names. I hit on a number of concepts, though the word “zen” was still at the forefront of my thought process. So most of my
early attempts had some play on that word.
Eventually, I pivoted to the concept of simplifi, here shown as being conceptually divided into three per the three categories from the card sort. However, I settled on something a bit
less convoluted and more straightforward:
The palette was tied to the concept of simplicity. The original attempts focused on earth tones and pastel colors, but did not convey the desired mood. Instead, we shifted toward a more neutral presentation with a couple of deep, rich colors designed to remind of home, comfort, and stability while still promoting the concept of growth and education. The green and brown here, in a design that merges the s and f while resembling a tree, reinforced that.
This also came with the creation of a complete style guide that included choices of typography.
After settling on a defined identity, palette, and mood, we went into high-fidelity mockups, taking our refined mockups and feedback and combining them to create a finished product.
The second round of user testing focused entirely on aesthetic and usability. While the original issues had seemingly been addressed, we wanted to ensure that there were no further issues, and also test out the analysis portion.
For the second test, our testers were asked to perform a similar set of tasks to the first, but then were also asked to go into the analysis and view a one-month analysis of their spending.
Users responded very positively to the testing, and particularly to the analysis page. There were no hiccups regarding the user flows, and users felt very much at home with the coloration of the app. The biggest suggestion was about the possible use of widgets to help guide new users, but as there were no hangups in the testing this suggestion was ultimately not considered for the MVP.
All told, I feel satisfied with the final result, if not entirely with the road it took to get there. My initial vision for the final project, using the sandy-brown color for a background,
backfired significantly, as very few people were receptive to the design. I appreciate the final product as it is, it’s a very streamlined and stylized product that encourages thoughtful
interaction, which I want to make the hallmark of my design style. My concern is how much of that was me and how much of that was the input I received. And whether that even makes a
difference.
What surprised me the most was how quick I was to bounce back and implement much of the feedback I received. I feel that even moreso than my first outing, I was able to conceptualize and
act on the key elements of design in this product.
Going forward with this product, the key things I would do would be to set a pricepoint - I’d want to avoid the ad-based revenue of Mint, and subscription services can feel predatory.
Instead I would want to make the app free to a point, with a one-time purchase to unlock the analytical capabilities of the app. This could also potentially lead to a tie-in with local CPAs
who might be able to provide extra extended analyses to clients.
Personally moving forward, I would like to develop a stronger sense of aesthetics in order to avoid missteps like the one I made in the middle of my development here with the color palette
and the application of that palette. I feel that it will require a good deal of work to fully realize exactly how these discrete elements come together and how they should be applied, and it
is something I will work on going forward.