Tackling Bill Calculation Problems for Group Food Orders in GoFood

Tackling Bill Calculation Problems for Group Food Orders in GoFood

Tackling Bill Calculation Problems for Group Food Orders in GoFood

Tackling Bill Calculation Problems for Group Food Orders in GoFood

GoFood is a food delivery service in Indonesia.

GoFood is a food delivery service in Indonesia.

GoFood is a food delivery service in Indonesia.

Overview

Overview

A part feature from the Gojek app. GoFood helps you to order food from lots of restaurants and have it brought to your door by a Gojek driver.

The goal of this particular project was to help a user who ordered food with their friends that find difficulties when calculating how much each person should pay in the end.

A part feature from the Gojek app. GoFood helps you to order food from lots of restaurants and have it brought to your door by a Gojek driver.

The goal of this particular project was to help a user who ordered food with their friends that find difficulties when calculating how much each person should pay in the end.

A part feature from the Gojek app. GoFood helps you to order food from lots of restaurants and have it brought to your door by a Gojek driver.

The goal of this particular project was to help a user who ordered food with their friends that find difficulties when calculating how much each person should pay in the end.

Role

Role

UI/UX Designer - User research, visual design, prototyping & testing

UI/UX Designer - User research, visual design, prototyping & testing

UI/UX Designer - User research, visual design, prototyping & testing

Project Duration

Project Duration

4 weeks

4 weeks

4 weeks

Platform

Platform

Mobile - Android

Mobile - Android

Mobile - Android

RESEARCH

RESEARCH

Problem Validation & User Research

Problem Validation & User Research

Before I jump far into visual design, I took my time to validate the initial problem. By doing that, not only I have the assurance that my assumption is valid, but also I managed to gather further pain points from real users. Then I conduct a user research to dig deeper from users' perspective when ordering multiple foods/drinks with friends using GoFood.

Objective

  • Understand user behavior when ordering food/drinks together through GoFood

  • Understand user behavior in calculating how much each person must pay when ordering food/drinks together through 1 GoFood account

  • Understand user pain points when viewing transaction history to find out how much each person must pay when ordering food/drinks together on GoFood

  • Find the ideal way in calculating how much each person must pay and how is the ideal way to ask his/her friends to pay

  • Understand user behavior when ordering food/drinks together through GoFood

  • Understand user behavior in calculating how much each person must pay when ordering food/drinks together through 1 GoFood account

  • Understand user pain points when viewing transaction history to find out how much each person must pay when ordering food/drinks together on GoFood

  • Find the ideal way in calculating how much each person must pay and how is the ideal way to ask his/her friends to pay

  • Understand user behavior when ordering food/drinks together through GoFood

  • Understand user behavior in calculating how much each person must pay when ordering food/drinks together through 1 GoFood account

  • Understand user pain points when viewing transaction history to find out how much each person must pay when ordering food/drinks together on GoFood

  • Find the ideal way in calculating how much each person must pay and how is the ideal way to ask his/her friends to pay

Methodology

  • In-Depth Interview

    Based on the objective, what I want to look for is how the user calculates, what are the pain points, and also the expectations of the user.

  • Usability Testing

    At the end of the improvement I made, I want to know, at which step the user still struggling to see the order history, calculating bill per item person and so on.

  • In-Depth Interview

    Based on the objective, what I want to look for is how the user calculates, what are the pain points, and also the expectations of the user.

  • Usability Testing

    At the end of the improvement I made, I want to know, at which step the user still struggling to see the order history, calculating bill per item person and so on.

  • In-Depth Interview

    Based on the objective, what I want to look for is how the user calculates, what are the pain points, and also the expectations of the user.

  • Usability Testing

    At the end of the improvement I made, I want to know, at which step the user still struggling to see the order history, calculating bill per item person and so on.

Conducting Research

I managed to gain information from users’ perspectives on how they use GoFood and how they calculate how much each person must pay when ordering food/drinks together through 1 GoFood account. So, there are five participants in this research, and the research itself was conducted by phone call. You can access the research here.

define

define

Defining the Problems & Proposing Solutions

Defining the Problems & Proposing Solutions

After conducting qualitative research to 5 users, I realize that there are repetitive problems users have encountered when doing the task. From that point, I can address three key issues I can possibly tackle.

Insights

From the five respondents, obtained a user persona. User personas are very helpful to explore more, what problems that users have experienced. And also from the user persona, we can see options to help solve the problem.

From the five respondents, obtained a user persona. User personas are very helpful to explore more, what problems that users have experienced. And also from the user persona, we can see options to help solve the problem.

From the five respondents, obtained a user persona. User personas are very helpful to explore more, what problems that users have experienced. And also from the user persona, we can see options to help solve the problem.

Image: User persona as urban office workers

Image: User persona as urban office workers

Motivations:

Motivations:

Motivations:

  • Vouchers & promos that offered by GoFood

  • The merchants and menus in GoFood are complete

  • Don’t have to go to the merchant, more practical and faster to buy food

  • The price will be cheaper when order together

  • Using calculator because faster and easier to calculate

  • Vouchers & promos that offered by GoFood

  • The merchants and menus in GoFood are complete

  • Don’t have to go to the merchant, more practical and faster to buy food

  • The price will be cheaper when order together

  • Using calculator because faster and easier to calculate

  • Vouchers & promos that offered by GoFood

  • The merchants and menus in GoFood are complete

  • Don’t have to go to the merchant, more practical and faster to buy food

  • The price will be cheaper when order together

  • Using calculator because faster and easier to calculate

Pain points:

Pain points:

Pain points:

  • Can't find price per item in transaction history, causing hard to calculate the bill

  • The difference in menu prices and discounts obtained

  • Sometimes forgot how much the bill when calculating, because missed the count

  • Forgot which items have been ordered by who

  • Often times friends forgot to pay the bill or forgot his/her bill

  • Often times feel disinclined to ask for the money

  • Can’t order from more than 1 merchants at a time

  • Can't find price per item in transaction history, causing hard to calculate the bill

  • The difference in menu prices and discounts obtained

  • Sometimes forgot how much the bill when calculating, because missed the count

  • Forgot which items have been ordered by who

  • Often times friends forgot to pay the bill or forgot his/her bill

  • Often times feel disinclined to ask for the money

  • Can’t order from more than 1 merchants at a time

  • Can't find price per item in transaction history, causing hard to calculate the bill

  • The difference in menu prices and discounts obtained

  • Sometimes forgot how much the bill when calculating, because missed the count

  • Forgot which items have been ordered by who

  • Often times friends forgot to pay the bill or forgot his/her bill

  • Often times feel disinclined to ask for the money

  • Can’t order from more than 1 merchants at a time

Expectations:

Expectations:

Expectations:

  • More detail on transaction history; price per item has to be shown

  • The detailed transaction history can appear without having to download it first

  • Able to name the item according to the name of the person who ordered it

  • Integrated feature from GoFood’s transaction history to GoPay’s “Split bill” & “Request GoPay”

  • Easy to use Split bill feature

  • Simple and automated calculation

  • Simple and automated billing

  • More detail on transaction history; price per item has to be shown

  • The detailed transaction history can appear without having to download it first

  • Able to name the item according to the name of the person who ordered it

  • Integrated feature from GoFood’s transaction history to GoPay’s “Split bill” & “Request GoPay”

  • Easy to use Split bill feature

  • Simple and automated calculation

  • Simple and automated billing

  • More detail on transaction history; price per item has to be shown

  • The detailed transaction history can appear without having to download it first

  • Able to name the item according to the name of the person who ordered it

  • Integrated feature from GoFood’s transaction history to GoPay’s “Split bill” & “Request GoPay”

  • Easy to use Split bill feature

  • Simple and automated calculation

  • Simple and automated billing

Problems

  1. Can't find the price per item in the transaction history, causing it hard to calculate the bill.

Most of the users find it difficult when they want to calculate the bill. It's because when they wanted to see the price per item in the transaction history, there is none. What appears is only the subtotal price along with discount fees, platform fees, and discounts. Not to mention if there is a menu that gets its discount, then the calculation will be different.

Most of the users find it difficult when they want to calculate the bill. It's because when they wanted to see the price per item in the transaction history, there is none. What appears is only the subtotal price along with discount fees, platform fees, and discounts. Not to mention if there is a menu that gets its discount, then the calculation will be different.

Most of the users find it difficult when they want to calculate the bill. It's because when they wanted to see the price per item in the transaction history, there is none. What appears is only the subtotal price along with discount fees, platform fees, and discounts. Not to mention if there is a menu that gets its discount, then the calculation will be different.

"Di history cuma kelihatan total aja, kalo hitung harga akhirnya ya bagi rata aja, walau ga fair." — Berkat, 26 y.o.

"Ngga terbantu, harus balik lagi ke retonya buat tau harga itemnya berapa." — Elsa, 26 y.o.

"Susah kalo mau bagi harga diterakhir, apalagi ada item yan punya diskon tersendiri." — Anggi, 21 y.o.

"Di history cuma kelihatan total aja, kalo hitung harga akhirnya ya bagi rata aja, walau ga fair." — Berkat, 26 y.o.

"Ngga terbantu, harus balik lagi ke retonya buat tau harga itemnya berapa." — Elsa, 26 y.o.

"Susah kalo mau bagi harga diterakhir, apalagi ada item yan punya diskon tersendiri." — Anggi, 21 y.o.

"Di history cuma kelihatan total aja, kalo hitung harga akhirnya ya bagi rata aja, walau ga fair." — Berkat, 26 y.o.

"Ngga terbantu, harus balik lagi ke retonya buat tau harga itemnya berapa." — Elsa, 26 y.o.

"Susah kalo mau bagi harga diterakhir, apalagi ada item yan punya diskon tersendiri." — Anggi, 21 y.o.

  1. Sometimes user loses the calculation when with a large group of people and the items ordered are too many.

When calculating the orders of a large group of people, the user feels confused and sometimes forgets the count because the user has to scroll the screen back and forth, to look at what orders are ordered. In the end, the user has to re-calculate again and make it feel even more inefficient.

When calculating the orders of a large group of people, the user feels confused and sometimes forgets the count because the user has to scroll the screen back and forth, to look at what orders are ordered. In the end, the user has to re-calculate again and make it feel even more inefficient.

When calculating the orders of a large group of people, the user feels confused and sometimes forgets the count because the user has to scroll the screen back and forth, to look at what orders are ordered. In the end, the user has to re-calculate again and make it feel even more inefficient.

"Pusing mikirin angkanya, kadang suka terlewat hitungannya." — Wilma, 26 y.o.

"Tergantung dari pesanannya apa dan jumlahnya. Bisa sulit kalau banyak dan harganya beda." — Elsa, 26 y.o.

"Pusing mikirin angkanya, kadang suka terlewat hitungannya." — Wilma, 26 y.o.

"Tergantung dari pesanannya apa dan jumlahnya. Bisa sulit kalau banyak dan harganya beda." — Elsa, 26 y.o.

"Pusing mikirin angkanya, kadang suka terlewat hitungannya." — Wilma, 26 y.o.

"Tergantung dari pesanannya apa dan jumlahnya. Bisa sulit kalau banyak dan harganya beda." — Elsa, 26 y.o.

  1. Oftentimes friends forgot to pay the bill or forget how much he/she has to pay.

After the user manages to find out how much each person has to pay, the user will charge his friends. It turns out that in this particular step the user also has a problem, namely some friends forget to pay or forget how much to pay. And this is not an easy thing for users to remind again because they feel disinclined.

After the user manages to find out how much each person has to pay, the user will charge his friends. It turns out that in this particular step the user also has a problem, namely some friends forget to pay or forget how much to pay. And this is not an easy thing for users to remind again because they feel disinclined.

After the user manages to find out how much each person has to pay, the user will charge his friends. It turns out that in this particular step the user also has a problem, namely some friends forget to pay or forget how much to pay. And this is not an easy thing for users to remind again because they feel disinclined.

"Kalau lupa orangnya dan jumlahnya yang harus dibayar." — Elsa, 26 y.o.

"Kadang-kadang ada rasa ga enak kalo mau ingetin." — Axel, 24 y.o.

"Kalau lupa orangnya dan jumlahnya yang harus dibayar." — Elsa, 26 y.o.

"Kadang-kadang ada rasa ga enak kalo mau ingetin." — Axel, 24 y.o.

"Kalau lupa orangnya dan jumlahnya yang harus dibayar." — Elsa, 26 y.o.

"Kadang-kadang ada rasa ga enak kalo mau ingetin." — Axel, 24 y.o.

Project Goal & Proposed Solution

  1. How might we make the transaction history able to help users to calculate their bills easily?

  • Show price per item, just like a common receipt

  • Show the discount that certain orders get

  • Show price per item, just like a common receipt

  • Show the discount that certain orders get

  1. How might we assist users with a large group of people ordered together & the items ordered are too many by making a feature to help write down the orders & calculate complex numbers?

  • Make split bill feature in GoFood

  • Make split bill feature able to apply discount per item

  • Make split bill feature able to add sub-items

  • Make split bill feature able to add friend(s) who didn’t have GoPay account

  1. How might we help users to remind his/her friends to pay their bills?

  • Integrate GoFood’s bill with “Request GoPay” feature

  • Make split bill feature able to share the calculation to Email or WhatsApp

design

Visualizing the Solutions

Visualizing the Solutions

Starting from the 'how-might-we' questions above, I worked on designing three improvements for each problem.

Starting from the 'how-might-we' questions above, I worked on designing three improvements for each problem.

Problem 1
Can’t find the price per item in the transaction history, causing it hard to calculate the bill.

Problem 1
Can’t find the price per item in the transaction history, causing it hard to calculate the bill.

Problem 1
Can’t find the price per item in the transaction history, causing it hard to calculate the bill.

Improvement 1

Before, on the history page user can’t see the price per item. So the solution to this problem is; show the price per item, just like a common receipt, and also show the discount that certain orders get.

Image: Order receipt

Image: Order receipt

Problem 2
Sometimes user loses the calculation when with a large group of people and the items ordered are too many.

Problem 2
Sometimes user loses the calculation when with a large group of people and the items ordered are too many.

Problem 2
Sometimes user loses the calculation when with a large group of people and the items ordered are too many.

Improvement 2

In this problem, there is no feature that helps user calculate their bill, so I developed a split bill feature, where user can apply discounts per item, can add sub-items, and also can add friends who didn’t have a GoPay account. This should be directly after user sees the transaction history to the page where user can see how much each one should pay.

Image: Split bill improvement

Image: Split bill improvement

Problem 3

Oftentimes friends forgot to pay the bill or forget how much he/she has to pay.

Improvement 3

Also in this problem, there is no feature yet in GoFood that can help user to easily and simply charge his/her friends. So I came up with Share to social media and integrating GoPay’s split bill to Request feature in GoPay.

Improvement 3

Also in this problem, there is no feature yet in GoFood that can help user to easily and simply charge his/her friends. So I came up with Share to social media and integrating GoPay’s split bill to Request feature in GoPay.

Improvement 3

Also in this problem, there is no feature yet in GoFood that can help user to easily and simply charge his/her friends. So I came up with Share to social media and integrating GoPay’s split bill to Request feature in GoPay.

Image: Request GoPay feature

Image: Request GoPay feature

test

Testing the Solutions Qualitatively

Testing the Solutions Qualitatively

And now, here comes the last step of the design thinking process. After a long-long journey, I have to validate my solutions to real users by conducting Usability Test. Wondering if my solutions are solving their problem or not. By asking users to accomplish 3 tasks, I hope I covered all problems stated above.

And now, here comes the last step of the design thinking process. After a long-long journey, I have to validate my solutions to real users by conducting Usability Test. Wondering if my solutions are solving their problem or not. By asking users to accomplish 3 tasks, I hope I covered all problems stated above.

Task no. 1:
Find your last GoFood transaction history and find price per item.

Task no. 1:
Find your last GoFood transaction history and find price per item.

Task no. 1:
Find your last GoFood transaction history and find price per item.

Summary

Users felt pleased when they now can see the price per item, which before they can’t. It helped them to know how many items they have ordered and how much each item costs.

Pain Points

For some users, the size of the fonts seems too small, reducing the readability.

Iteration

Resize some text.

Before

After

Task no. 2:
Calculate the bill by using Split Bill feature.

Task no. 2:
Calculate the bill by using Split Bill feature.

Task no. 2:
Calculate the bill by using Split Bill feature.

Summary

Most users like this feature and find it very helpful when they want to calculate each person’s bill. Users find it very helpful especially because they don’t have to calculate manually using a calculator or through Ms. Excel, the user can know the bill per person automatically.

Pain Point 1

The Bill Details button on the summary page is too small.

Solution 1

Change the size of the Bill Details button to be larger.

Before

After

Pain Point 2

The Checkbox & Avatar size on the Assign Items page is also too small.

Solution 2

Change the size of the Checkbox & Avatar on the Assign Items page to be larger.

Before

After

Pain Point 3

The size of the name in the Contact Card component on the Split Bill With page is also too small.

Solution 3

Change the name font size in the Contact Card component on the Slit Bill With page to be larger.

Before

After

Pain Point 4

Users find it difficult when they want to split the bill with new people who are not in their phone contacts.

Solution 4

Allows users to add new people by entering their name only, and later on, the avatar will show their initials.

Before

After

Task no. 3:
Request your friends to pay.

Task no. 3:
Request your friends to pay.

Task no. 3:
Request your friends to pay.

Summary

Most users who feel disinclined when they want to collect or remind their friends to pay bills found out that this feature is helpful. Without the need to charge/remind again, user just has to share the bills with his friends.

Pain Point 1

Users feel confused about what the purpose of Request GoPay’s and Share are distinguished for.

Solution 1

Put Request GoPay feature into the Share button, and make 1 button only so that users will not be confused.

Before

After

Pain Point 2

When charging, some users notice that not all of their friends have GoPay accounts so that it will be difficult for the payment process later.

Solution 2

Make more flexible choices when the user wants to share the bill with his friends by creating a new page.

Before

After

prototype

Making Design 'Alive'

Making Design 'Alive'

Here comes the fun step! After making mock-up solutions, it’s time to make things feel alive and running. Using Figma to prototyping you also can try the solution. Click on the link below to direct you to the prototype!

Here comes the fun step! After making mock-up solutions, it’s time to make things feel alive and running. Using Figma to prototyping you also can try the solution. Click on the link below to direct you to the prototype!

Closing

Closing

Conclusion

Finally reaching the end of this study case, I learned a lot from all this process, this journey, where every problem has its own way out and needs to be solved. UI/UX design products are not to fulfill what designers want. But most of all, what users need is all to aim for.

Finally reaching the end of this study case, I learned a lot from all this process, this journey, where every problem has its own way out and needs to be solved. UI/UX design products are not to fulfill what designers want. But most of all, what users need is all to aim for.

Finally reaching the end of this study case, I learned a lot from all this process, this journey, where every problem has its own way out and needs to be solved. UI/UX design products are not to fulfill what designers want. But most of all, what users need is all to aim for.