Tip-Top Table

Product Design Case Study



Product define

At the beginning we defined the product.

For the purposes of the project, a complete analysis of the business environment was conducted using Business Model Canvas, Value Proposition, Value Model Canvas, SWOT.

Due to the fact that I focus on the UX process, I will skip the detailed description of this stage.



Research objective

To learn about the needs and problems of users who eat in restaurants

Research questions
  • in which situations users go out to the restaurant
  • in which situations they decide to book in advance
  • how do they book?
  • what determines the choice of a particular restaurant?
  • what problems do users encounter during the reservation and stay?
  • what are the expectations during the process and visit to the restaurant
  • what is the ideal booking process


IDI test results

Customer needs
  • Minimize booking time
  • Simplify the process and facilitate meetings with a group of contractors, friends
  • Menu preview and the possibility of ordering for a specific time
  • Convenient payment methods (cash, background, account separation, electronic tip)
Restaurateurs needs
  • A secure payment system
  • Minimizing service costs
  • Access to the integrated CRM system
  • Additional space for advertising and offer


The results of the research showed that our product in its original concept did not solve the real problems of users, so we were able to make a pivot and offer a service that will solve the problems of both users and restaurateurs.


Functional benchmark​

Rest-tech apps benchamarked
With the possibility of reservation
avaible on Polish market
in premium sector


Information architecture

Card Sorting

In building the information architecture as well as in selecting the search, filtering and sorting options, the card sorting method helped us. We used this method several more times during project iteration.



On the basis of the research data, the main and side persona were developed


User Stories

During the workshop we developed User Stories, a few examples below.

Additionally, using SAP Scenes we created a storyboard for one of the user paths

  • As an assistant, I want to easily book a place for the group to have a meal together
  • As a user, I want to easily pay for a pre-booking to be able to make a reservation
  • As a user, I want to be able to easily search for a restaurant to make a reservation for a large group
  • As a user, I want to be able to pay the bill easily so that I don’t have to remember about it and be able to separate it

Customer Journey Map​

We have created a map of user experience based on user data and history.

This allowed us to better understand the needs and pains the user is experiencing during the booking process. The visualization allowed us to define critical problems and find solutions for them (quick wins).


Functional scope​

In the first stage, we have listed all functions that could be used in the application.

We then asked the people surveyed to express their opinion on each function and to allocate points which would give them the greatest value and which they would use most often.

On the basis of the survey, we created a table which shows us what we should focus on when designing application.


User Flow​

On the basis of User Stories we have created critical paths that the user has to follow in order to make a reservation in the application.

Having the paths ready, we created the whole flow of application.




Sketching solutions allowed us to generate ideas quickly. The first tests with users on paper prototypes showed which solutions can work.


Low Fidelty​

Two equivalent Lo-Fi designs were created, one made in Balsamiq and Marvel, the other in Sketch and Invision.


Graphic Design​

Between the Lo-Fi model and the graphic design we performed few iterations of usability tests.

The conclusions led us to the final prototype which was subjected to the last tests.

Last but not least


Usabilty tests

Many times during the application design stage we used tests with users.
First on paper prototypes, then on Low Fidelity and Graphic Design stage.