How do you deal with joint payments with a lot of people? Split bill process made easy with Patungin!
PATUNGIN is an all-in-one mobile app for a joint payment using split-bill feature.
ROLE
UX Researcher
DURATION
3 Days, 14-16June 2022
PROCESS
Empathize, define, ideate, testing
TOOLS
Figma, FigJam, Adobe Illustrator, Trello, Zoom Meeting, Maze, Google Form
PROJECT OVERVIEW
PATUNGIN is an all-in-one mobile app for a joint payment using split-bill feature. Track your expenses for electricity bill, group dinner, even travelling expenditures! Payments are made easy via bank accounts or
e-Wallet options. You can also collect your friends shortfall by setting a due date reminder. No more hard feelings, right?
BACKSTORY
This UI UX case study is done as an exercise, without any direction from the client. This redesign process was obtained from the Binar Academy Bootcamp as a Final Project. This time the redesign process
was carried out with the group as UI/UX Designer team that collaborate with Project Manager Team. We had some brainstorming and we found difficulties when doing split-bill in daily activities with group of friends.
In this Final Project I’m in charge as UX Researcher. I involved in Empathize, Define, Ideate, and Prototype Testing. Also me and one of my friend as UX Researcher do an intense communication and collaboration with PM
Team and UI Designer Team. Here is some works that I do in this project.
In our first meeting we have a long discussion as UI/UX Designer and PM team. We do brainstorming about what’s our problem these days that we can solve the problem by creating an application prototype. Until
we came up with the splitting-bill problem when we go out or living with group of friends.
We also make a conclusion about the financial cost problem’s in this case. In addition to
wasted time due to calculations that takes a lot of time, paying more that what should be due can cause personal losses. For example Tax and Delay payment. Then from a social perspective, people who collect
arrears will be able to change people’s perceptions of the collector as a label of a ‘calculating person’, even this can damage a relationship with someone.
In this case, how things should work? In splitting-bill process there is should be a way to make combined payments more fairly, quickly, and evenly. Also on time in paying bills without delay, reluctant to remind, and asked
many time. Because it can save your time, money, and there will be no harsh feeling with your group of friends, right?
“They don’t want to be counted, but also do not want to lose. Of course it can save time!”
How We Collect Data
We used quantitative methods to collect validation of problems experienced by the prospective respondents in their daily lives. To collect data, we make a practical survey by placing hypotheses and assumptions in each survey
problem. And for publications, we use the Google Form link so it will be easier to access by the participants. Based on the participants basic information that are 225 participants with 42% Male and 54% Female. And 91%
of the participants are 17-25 years old.
And these are the results of our research, that was filled by 225 participants.
Competitor Analysis
In developing a feature, we also need to know competitor data related to the advantages and disadvantages of features with the same business model. The following is a review objective on Competitor Benchmarking
document data:
This stage is carried out to map user problems more specifically
The Problem
Based on user survey, most of user felt that the administrative and payment process in car rental took a lot of time and not that flexible. So that customer problems are obtained in the form of,
Problems
Promblem Statement
Point of View
From the user survey data and problem statement, a point of view is prepared that contains information and needs from the user.
Empathy Map
After we know the problems faced by the user, we try to write what the user might say, think, do, and feel when facing these problems in the form of an empathy map. The making of this empathy map allows our team to position
ourselves as users who face these problems.
User Persona & User Journey Map
The user persona is structured to find out information from the target user of this application. Meanwhile, the User Journey Map is made to find out user thoughts when they doing the splitting-bill process, so that improvement
opportunities points can be obtained.
How Might we Question
Created as research objective summary of the user's pain points when they try to send money through DANA application and the problem statement that has been made before.
How might we help the user to be able to see the complete account information for the transfer destination?
Created as research objective summary of the user's pain points when they do splitting-bill with a group of friends and the problem statement that has been made before.
How We Generate Solution
We propose solution by provides a collective calculation-based platform with detailed column variables that can be easily adjusted by the user, and coupled with a reminder feature to the joint member concerned.
Because with the effective calculation, the audience can share calculation quickly and accurately without feeling lost. Then this can also minimize the perception of calculation bias.
Information Architecture & User Flow
This document was made to illustrates the program's operating processes through basic shapes and symbols, also it serves as a guide for ui designers in the process of making ui design. It shows the flow of PATUNGIN
application,
Low Fidelity (wireframe)
This is the digital sketch of PATUNGIN app was made in
Figma.
Two methods of testing were used to review and evaluate our prototype hence validating its efficiency, design, and functionality. First, heat map were conducted using Maze to 19 users in total, to observe its features,
click-ability, and rating our features using System Usability Score (SUS). Secondly, we do Usability Testing with 5 participants to observe how user use and interact with the prototype and got
user feedback after they try the prototype.
Heat Map and SUS Result
This is the quantitative data that we get from Heat Map usiing Maze and SUS testing using Google Form. From these data we know that this prototype get a Good-Poor score from the participants
First slide label
Some representative placeholder content for the first slide.
Second slide label
Some representative placeholder content for the second slide.
Third slide label
Some representative placeholder content for the third slide.
Usability Testing Result
We does the Usability Testing with 5 participants that have the similar background and might use our application
Here is some feedback from UT participants after they try to use PATUNGIN prototype,
The wrongs things of the this designs,
Recommendation
- Create a different page for each process in ‘Mulai Patungan’ page
- Add a progress bar in each ‘Mulai Patungan’ page
- Replace radio button with Toggle Button Switch for ‘custom’ and ‘evenly’ feature
- Make the home page look simpler & Cleaner
What's Next?
- Create a different page & Progress bar for each process in ‘Mulai Patungan’ page
- Replace Radio Button with Toggle Button Switch for ‘custom’ and ‘evenly’ feature
This is project become my longest and tearful project in this Bootcamp. Because we work on this PATUNGIN project from starch until we present it to our facilitator. I have such a good time and opportunity to work in a larger
group also have collaboration with Project Manager. Working with the PM team made me understand how to run this project by considering the business aspects and also getting directions and suggestions from the PM team's point
of view.
I also learn how to present our work as UX researcher to our team members and facilitator. I learn how to present it as clear as possible with words that are easy to understand. The important thing that I get from this project
is the feedback that I get from our facilitator, to “always remember every time you do anything always consider what does the user really need? :)”
