Equitable Bill Splitting
Overview
This project is one of my favorite projects because I had the chance to follow the ideal human centered approach. It was designed for a group project at UW program. Our group started the project by brainstorming the ideas for problem space we wanted to tackle.
We realized that there is need for finding a solution for easy bill splitting in a group dining experience. Sometimes people are invited to a birthday party with a bunch of people they don’t know and it gets awkward at the end when it comes time to pay. They want to make a good impression and don’t want to come off too cheap and it’s just a tough social situation to navigate.
We created Party Favor for an easy way to split the bill and pay what you owe without getting into any awkward social situation.
Challenge
How might we transform the unique challenge of a group restaurant meal into a positive experience and minimize bad feelings?
Strategy
We started with competitive analysis and stakeholder research. We learnt what exists, where the gaps are and how our target users feel about the existing solutions.
Our groundbreaking insight came from ethnographic research. We discovered that all the data needed to make our app successful already sits in POS systems at restaurants. We decided to design a mobile app for diners which will pull data from the POS systems. This will not only provide the complete control and transparency to the diners but will also reduce the workload of a server.
Ideation, Sketching & Paper prototyping
While doing brainstorming, we all narrowed down on few ideas we all wanted to explore. We decided to use a code to provide a bridge between diner’s app and restaurant POS system.
ROLE
UX designer
TEAM
Nikhita Goyal, Julie Sayigh, Andrew O’connor, Melina Shak
High fidelity wireframes
To avoid any distractions, we made a prototype with high fidelity wireframes for user testing. This helped users focus on functionalities instead of visual design elements.
Usability testing
Key takeaway
Considering the usability testing results and reflecting at our final product, we realized that we should not ‘feature bloat’ our app. So we decided to narrow down the scope and aim for quality over quantity.