Paygo is a web-based platform that makes it simple to split the bill so that everyone can pay their fair share.

A project born out of my personal passion, was inspired by the challenge I faced while splitting a bill at a restaurant. (8/2022)
Tools used
: Figma, Axure, FigJam, Google suite (Form, Docs, Sheet)

Overview

First, let me set up the scene…

In a large group It's a pain to manually split a check and calculate what each person owes. So what happens more often than not is the bill gets split evenly, and people end up paying for things they didn't order.

The goal: Simplify the experience of splitting a check at a restaurant between a group of people.

Click for the final design
Research

Gathering the data

I did a screening survey with 81 participants and then conducted user interviews with 8 interviewees.

Interview insights

  1. 1. The most common actions users take:
2. Most of the participants carry cash only for safety
3. Most of the participants  prefer credit cards so they can pay every amount, and credit is easier to carry
4. The calculation is annoying and time-consuming, especially when sharing meals
Define

Who are our users?

From the research and user interviews, I was able to define two types of users:
Anna, 37: A business consultant who’s always on the go and needs a quick, cashless checkout solution that doesn’t require third-party assistance. She values having all payment information handy to handle bills efficiently, especially in busy meetings.
Sharon, 25: A startup employee with a strict budget who prefers Apple Pay for convenience and dislikes installing extra apps. She wants a simple, seamless way to split checks with her colleagues without the hassle of managing separate payments.

What they want to do?

Design

Testing ideas with low-fidelity

Usability test

I conducted usability test with Maze platform:
I had 16 participants in total,  I assigned 3 main tasks and gathered feedback on their experience.

I found a few patterns:

  • Users struggled to choose check-splitting methods due to closely placed buttons, leading to misclicks.
  • Participants accidentally clicked multiple numbers when selecting payment amounts; spacing between numbers needs adjustment.

Refining the design

Using insights gained from usability testing

What I learned
  • Accessibility matters: With user testing, I realized that the text and buttons were too small, creating barriers for users. This taught me the importance of prioritizing accessibility in future designs.
  • Not everyone is aligned with the use of technology- some prefer to stick to traditional methods (cash).
Next steps
This design was created as a learning opportunity; therefore, I plan to conduct another usability test and improve my design based on the insights.

More?

Check out other projects

Ticketrack

Ticketing solution for
cybersecurity platform

Tangata

B2B system for managing Human Resources processes and needs.