UX/UI: Got a Table?
Gotable: Make your waiting experience easier and smarter.
"Have you ever met this situation, that you are waiting for a table, standing outside of the restaurant for a long time, hungry and anxious about don’t know how long to go? " Before crafting this project, we have hypothesis like this, brainstorming that people who had bad waiting experience might need a product helps them tracking the waiting status. That's the intention we brought out this idea in the very beginning. We want to build a powerful waiting status tracking gadget to make users’ waiting experience easier and smarter.
However still there's something we need to dig into, it's crucial to understand the specific pain points and insights of the users before we jump into design solutions, so we dive into this situation and do research to figure out the real insights behind …
The dramatic gap between the feedback from customers and restaurant also draw our attentions. Popular restaurants don't consider queuing is a big problem. However the opportunities is those less popular restaurant, they want more customers to come to their place, it would be better to push their availability as alternatives to the customers which redirect them to their restaurants. That's the opportunity for us to make customers satisfied while advertising for those less popular restaurant, which make the app profitable.
During the ideation phase, it's essential to imitate the real waiting experience, thus we can map out the essential features which help solve the problem. We adopt Affinity Diagram to group different scenarios as our first step, including all kinds of waiting experience, from small group of people family gathering, to large group team building, we map out the context, step, anxiety cause and solution of each scenarios and regroup them into three personas. Based on the personas we formulated those 3 scenarios storyboard in order to capture the features that target users need.
Firstly users need to walk through the searching task. It's quite basic and mostly I leverage the best practice of the industry. As the app is designed for checking the wait time of the restaurant, users might have a potential target restaurant in their minds, thus searching bar is the task focus.
Check-in on site: users need to scan the QR code, input their information to check-in, then they can wait to be updated the accurate waiting status and get push notification from the restaurant.
In engagement phase, user can view the updated menu, and pre-order through the app. If user quit the line, gotable will push alternatives to redirect them to other restaurants. This will meet the needs of the less popular restaurants.