SplitSavvy

SplitSavvy

Creating a scalable budgeting app for collaborative budgeting that's inclusive to those with shared finances

Creating a scalable budgeting app for collaborative budgeting that's inclusive to those with shared finances

Product Type

Scalable Feature

Platform

Mobile

TIMELINE

1 week (2024)
BACKGROUND

A Modified Design Sprint

This was a 1-week solo project where I used a modified version of a design sprint. The focus for this case study came from a personal challenge I encountered while searching for the perfect budgeting app.

Identifying this gap in the market inspired me to commit to exploring solutions to this problem, while maintaining an open mind during the research process.

PROBLEM STATEMENT

Helping Those Who Share Expenses

How might we design an expense tracking app that helps users easily split the task of tracking income and expenses?

This would make it easier for those who share budgets with partners, roommates, or family members.

MARKET ANALYSIS

Identifying Gaps in Existing Budgeting Apps

With only one week to complete this project, I didn't have time to gather user insights directly. Instead, I reviewed existing apps to see if this feature was really missing.

With only one week to complete this project, I didn't have time to gather user insights directly. Instead, I reviewed existing apps to see if this feature was really missing.

With only one week to complete this project, I didn't have time to gather user insights directly. Instead, I reviewed existing apps to see if this feature was really missing.

Top Insights:

  • Lack of customization for specific categories.

  • Lack of splitting fields.

  • Privacy and security concerns when linking your bank.


To speak a little more on the last one about privacy, I have heard this concern with multiple people in the past about connecting their banks to budgeting apps, and how that can be the one reason they wouldn't sign up.

Top Insights:

  • Lack of customization for specific categories.

  • Lack of splitting fields.

  • Privacy and security concerns when linking your bank.


To speak a little more on the last one about privacy, I have heard this concern with multiple people in the past about connecting their banks to budgeting apps, and how that can be the one reason they wouldn't sign up.

Top Insights:

  • Lack of customization for specific categories.

  • Lack of splitting fields.

  • Privacy and security concerns when linking your bank.


To speak a little more on the last one about privacy, I have heard this concern with multiple people in the past about connecting their banks to budgeting apps, and how that can be the one reason they wouldn't sign up.

STORYBOARD

Starting with the Boring to Get Splitting Right

Creating this storyboard helped me streamline the transaction splitting process. I identified key elements the user might want to split, such as users, merchants, categories, and amounts.
Initially, the format resembled a spreadsheet, which felt too boring. To enhance user engagement and prevent fatigue, I aimed for a more enjoyable and interactive design.
REVISED STORYBOARD

From Spreadsheets to Interactive Sentences

I aimed to improve user experience and engagement by replacing the traditional tabular format with a visually appealing, interactive interface that uses a sentence format, allowing users to follow along and fill in the blanks.

USER TESTING

Navigating Negative Feedback

Even though the five users that I tested didn’t favor the splitting function during this test, I decided to keep it because I believe the splitting feature might have been misrepresented and could be very useful to others if I had tested it with more people.

Since this feature is the main focus of my project, I felt it was important to refine and continue with it, despite the initial challenges.

USER FEEDBACK

Improving Usability

"The size of the word ENTER was too small"

Users hesitated after selection, unaware the button had to turn blue.

"Change the word to match the function"

It appeared that there was a lack of clarity in interpreting the button.

"Excessive ENTER buttons"

60% of the users mentions there were too many "enter" buttons to proceed.

"Change the date to a numerical format"

80% of users preferred seeing the date instead of the word "today" or "yesterday"

Initial Loading Screen

Entering a Transaction

Entering a Transaction

Splitting a Transaction

FINAL THOUGHTS

A Successful Learning Experience

Although the users didn't find the product useful, the case study was a success because it provided crucial insights into the design process:

  • Importance of Research: Showed that starting with thorough user research is crucial to find real user needs.

  • Avoiding Assumptions: Highlighted the dangers of assuming others have the same problems as you.

  • Better Future Projects: Equipped me with the knowledge to approach future projects with a more user-centric and research-driven mindset.

Reflecting on these learnings, I realize that a design sprint was not the best approach for this project. If I had conducted more interviews initially and found consistent disinterest, I could have redirected the project much earlier, saving time.

Although the users didn't find the product useful, the case study was a success because it provided crucial insights into the design process:

  • Importance of Research: Showed that starting with thorough user research is crucial to find real user needs.

  • Avoiding Assumptions: Highlighted the dangers of assuming others have the same problems as you.

  • Better Future Projects: Equipped me with the knowledge to approach future projects with a more user-centric and research-driven mindset.

Reflecting on these learnings, I realize that a design sprint was not the best approach for this project. If I had conducted more interviews initially and found consistent disinterest, I could have redirected the project much earlier, saving time.

See More of My Work
Spotify Unite
VidSeo Pro
See More of My Work
Spotify Unite
VidSeo Pro
See More of My Work
Spotify Unite
VidSeo Pro

  • GET IN TOUCH ✧ LET'S TALK ✧

  • GET IN TOUCH ✧ LET'S TALK ✧

© 2024 Dexter Sulit

Linkedin

Instagram

sulitdexter@gmail.com